HubSpot Process Documentation

Metadata

• Generated by: HubSpot Documentation Engine
• Total process candidates: 1
• Workflow assessment scope: name_contains via DOCS_WORKFLOW_PREFIXES: ELEVATE, Quality (86/500)
• List assessment scope: name_contains via DOCS_LIST_PREFIXES: ELEVATE (45/2191)
• Status: draft

NEW_ELEVATE - Events - Lead creation & lifecycle stage based on marketing touchpoints w/o company req

METADATA title: NEW_ELEVATE - Events - Lead creation & lifecycle stage based on marketing touchpoints w/o company req type: process domain: Events objects: [Touchpoint] status: draft

User Story (optional)

Logic not derivable from system.

Why

• Why this process exists: Logic not derivable from system.
• What business problem it solves: Logic not derivable from system.
• What breaks if removed: HubSpot would stop executing the system behavior listed below; business impact is not derivable from system alone.

How It Works

Trigger

• Exact trigger from workflow: HubSpot enrollment criteria type: MANUAL
• Criteria type: MANUAL
• Filter-like criteria returned: 0
• Property references: none detected
• List references: none detected
• Filter types: Logic not derivable from system.
• Operators: Logic not derivable from system.
• Trigger logic:
  • Enrollment criteria type: MANUAL
  • Returned criteria keys: shouldReEnroll, type
  • Detailed trigger logic: Logic not derivable from system.

Steps

Step 1 - Action 62

• What happens: Branches based on HubSpot list membership; 1 branches
• What triggers it: Workflow start action returned by HubSpot
• System condition: 1 branch condition(s) returned by HubSpot.
• What data is used: properties: 4f_Touchpoint type (n4f_touchpoint_type); lists: none detected

DATA MEANING:

• 4f_Touchpoint type (n4f_touchpoint_type): 4flow specific dropdown select of touchpoint types. Works in conjunction with 4f_Touchpoint name_dd and 4f_activity type.

ACTION EVIDENCE:

• Action category: list_branch
• Detected intent: Branches based on HubSpot list membership
• Returned action type: LIST_BRANCH

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• Branch: booth meeting
  • Condition summary: booth meeting
  • Default branch: no
  • Next action IDs: 65
  • Referenced properties: 4f_Touchpoint type (n4f_touchpoint_type)
  • Referenced lists: none detected
  • Filter-like criteria returned: 2
  • Returned branch logic:
    • OR group
      • AND group
        • 4f_Touchpoint type is any of Event booth meeting

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 2 - Action 65

• What happens: Branches based on HubSpot list membership; 2 branches
• What triggers it: After action 62
• System condition: 2 branch condition(s) returned by HubSpot.
• What data is used: properties: 4f_event_Quality of contact (n4f_event_quality_of_contact); lists: none detected

DATA MEANING:

• 4f_event_Quality of contact (n4f_event_quality_of_contact): This property is used as the selector for event booth staff. By selecting the right measures, we determine if a conversion (of the contact) is an MQL and create a lead.

ACTION EVIDENCE:

• Action category: list_branch
• Detected intent: Branches based on HubSpot list membership
• Returned action type: LIST_BRANCH

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• Branch: qualified
  • Condition summary: qualified
  • Default branch: no
  • Next action IDs: 94
  • Referenced properties: 4f_event_Quality of contact (n4f_event_quality_of_contact)
  • Referenced lists: none detected
  • Filter-like criteria returned: 2
  • Returned branch logic:
    • OR group
      • AND group
        • 4f_event_Quality of contact is any of Sales potential, Sales potential unclear
• Branch: not qualified
  • Condition summary: not qualified
  • Default branch: yes
  • Next action IDs: workflow exit or not returned
  • Referenced properties: none detected
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch name: not qualified

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 3 - Action 94

• What happens: Runs a connected HubSpot workflow action
• What triggers it: After action 65
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: connected_action
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Runs a connected HubSpot workflow action
• Returned action type: SINGLE_CONNECTION
• Returned field keys: marketableType, targetContact

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 4 - Action 113

• What happens: Branches by A/B test split
• What triggers it: After action 94
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: ab_test_branch
• Detected intent: Branches by A/B test split
• Returned action type: AB_TEST_BRANCH

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 5 - Action 114

• What happens: Runs a connected HubSpot workflow action
• What triggers it: After action 113
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: connected_action
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Runs a connected HubSpot workflow action
• Returned action type: SINGLE_CONNECTION
• Returned field keys: delta, time_unit

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 6 - Action 2

• What happens: Branches based on HubSpot list membership; 5 branches; 6 list dependencies
• What triggers it: After action 114
• System condition: 5 branch condition(s) returned by HubSpot.
• What data is used: properties: Disqualification Reason (hs_lead_disqualification_reason); lists: ELEVATE - Stop criteria existing active lead, ELEVATE - Stop criteria - Lead creation, ELEVATE - Lead supression - diqualification criteria permanent, ELEVATE - Lead supression - disqualification criteria temporary, ELEVATE - Contacts with lost deals, ELEVATE - Contacts with ghosting leads

DATA MEANING:

• Disqualification Reason (hs_lead_disqualification_reason): Dropdown list of reasons for disqualification

ACTION EVIDENCE:

• Action category: list_branch
• Detected intent: Branches based on HubSpot list membership
• Returned action type: LIST_BRANCH

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• Branch: already active - Lead
  • Condition summary: already active - Lead
  • Default branch: no
  • Next action IDs: 66
  • Referenced properties: none detected
  • Referenced lists: 11378
  • Filter-like criteria returned: 2
  • Returned branch logic:
    • OR group
      • AND group
        • AND group
          • ELEVATE - Stop criteria existing active lead is in list 11378
• Branch: reopen - Lead
  • Condition summary: reopen - Lead
  • Default branch: no
  • Next action IDs: 10
  • Referenced properties: none detected
  • Referenced lists: 17863
  • Filter-like criteria returned: 2
  • Returned branch logic:
    • OR group
      • AND group
        • AND group
          • ELEVATE - Contacts with ghosting leads is in list 17863
• Branch: reattempting lead
  • Condition summary: reattempting lead
  • Default branch: no
  • Next action IDs: 10
  • Referenced properties: Disqualification Reason (hs_lead_disqualification_reason)
  • Referenced lists: 11391, 11421, 11428, 11434
  • Filter-like criteria returned: 10
  • Returned branch logic:
    • OR group
      • AND group
        • AND group
          • ELEVATE - Lead supression - disqualification criteria temporary is not in list 11428
        • AND group
          • Disqualification Reason is any of Budget Constraints, Bad Timing, No Interest
      • AND group
        • AND group
          • ELEVATE - Contacts with lost deals is in list 11434
          • ELEVATE - Lead supression - diqualification criteria permanent is not in list 11421
          • ELEVATE - Lead supression - disqualification criteria temporary is not in list 11428
          • ELEVATE - Stop criteria - Lead creation is not in list 11391
• Branch: new business lead
  • Condition summary: new business lead
  • Default branch: no
  • Next action IDs: 8
  • Referenced properties: none detected
  • Referenced lists: 11391, 11434
  • Filter-like criteria returned: 3
  • Returned branch logic:
    • OR group
      • AND group
        • AND group
          • ELEVATE - Stop criteria - Lead creation is not in list 11391
          • ELEVATE - Contacts with lost deals is not in list 11434
• Branch: could not decide
  • Condition summary: could not decide
  • Default branch: yes
  • Next action IDs: 101
  • Referenced properties: none detected
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch name: could not decide
      • Next action: 101

LIST LOGIC:

• ELEVATE - Stop criteria existing active lead (11378)
  • Business meaning: System-derived role: data quality. Used to identify records for data hygiene or completeness review based on returned filters.
  • Filters: 6
  • Referenced properties: hs_last_activity_date, hs_pipeline_stage, n4f_initial_lead_creation_time
  • Filter logic:
    • OR group
      • AND group
        • AND group
          • Last Activity Date is between object with keys: indexReference, offset, timeType, timezoneSource, zoneId
        • AND group
          • Lead stage is any of Qualification, Assignment, Outreach
      • AND group
        • AND group
          • Last Activity Date is unknown
        • AND group
          • Lead stage is any of Qualification, Assignment, Outreach
      • AND group
        • AND group
          • Last Activity Date is before
        • AND group
          • Lead stage is any of Qualification, Assignment, Outreach
• ELEVATE - Stop criteria - Lead creation (11391)
  • Business meaning: Used for segmentation. A more specific business purpose is not derivable from returned system evidence.
  • Filters: 3
  • Referenced properties: none detected
  • Filter logic:
    • OR group
      • AND group
        • ELEVATE - Stop criteria existing active deal is in list 11381
      • AND group
        • ELEVATE - Stop criteria existing active lead is in list 11378
      • AND group
        • ELEVATE - Stop criteria strategic contact is in list 11383
• ELEVATE - Lead supression - diqualification criteria permanent (11421)
  • Business meaning: System-derived role: qualification. Used to identify records that meet qualification criteria returned by HubSpot filters.
  • Filters: 2
  • Referenced properties: hs_lead_disqualification_reason, hs_pipeline_stage
  • Filter logic:
    • OR group
      • AND group
        • AND group
          • Lead stage is any of Disqualified
          • Disqualification Reason is any of No Sales Lead, No Decision-making Power, Technical Limitations, Competitor Preference, Prior Negative Experience
• ELEVATE - Lead supression - disqualification criteria temporary (11428)
  • Business meaning: System-derived role: qualification. Used to identify records that meet qualification criteria returned by HubSpot filters.
  • Filters: 4
  • Referenced properties: hs_lead_disqualification_reason, hs_v2_date_entered_unqualified_stage_id_1675714327
  • Filter logic:
    • OR group
      • AND group
        • AND group
          • Date entered “Disqualified (Lead-Pipeline)” is between object with keys: indexReference, offset, timeType, timezoneSource, zoneId
          • Disqualification Reason is any of Budget Constraints, No Decision-making Power, Bad Timing, No Interest
      • AND group
        • AND group
          • Date entered “Disqualified (Lead-Pipeline)” is between object with keys: indexReference, offset, timeType, timezoneSource, zoneId
          • Disqualification Reason is any of No response / ghosted
• ELEVATE - Contacts with lost deals (11434)
  • Business meaning: Used for segmentation. A more specific business purpose is not derivable from returned system evidence.
  • Filters: 1
  • Referenced properties: hs_is_closed_lost
  • Filter logic:
    • OR group
      • AND group
        • AND group
          • Is closed lost equals True
• ELEVATE - Contacts with ghosting leads (17863)
  • Business meaning: System-derived role: qualification. Used to identify records that meet qualification criteria returned by HubSpot filters.
  • Filters: 2
  • Referenced properties: hs_lead_disqualification_reason, hs_v2_date_entered_unqualified_stage_id_1675714327
  • Filter logic:
    • OR group
      • AND group
        • AND group
          • Disqualification Reason is any of No response / ghosted
          • Date entered “Disqualified (Lead-Pipeline)” is between object with keys: indexReference, offset, timeType, timezoneSource, zoneId

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 7 - Action 10

• What happens: Branches based on HubSpot list membership; 2 branches
• What triggers it: After action 2
• System condition: 2 branch condition(s) returned by HubSpot.
• What data is used: properties: Lifecycle Stage (lifecyclestage); lists: none detected

DATA MEANING:

• Lifecycle Stage (lifecyclestage): The qualification of companies to sales readiness throughout the buying journey

ACTION EVIDENCE:

• Action category: list_branch
• Detected intent: Branches based on HubSpot list membership
• Returned action type: LIST_BRANCH

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• Branch: lifecycle stage low
  • Condition summary: lifecycle stage low
  • Default branch: no
  • Next action IDs: 11
  • Referenced properties: Lifecycle Stage (lifecyclestage)
  • Referenced lists: none detected
  • Filter-like criteria returned: 3
  • Returned branch logic:
    • OR group
      • AND group
        • AND group
          • Lifecycle Stage is none of Evangelist, Sales Accepted Lead, Opportunity, Sales Qualified Lead, Customer
• Branch: lifecycle stage high
  • Condition summary: lifecycle stage high
  • Default branch: yes
  • Next action IDs: 12
  • Referenced properties: none detected
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch name: lifecycle stage high
      • Next action: 12

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 8 - Action 11

• What happens: Sets HubSpot property values; properties: lifecyclestage = static value Marketing Qualified Lead
• What triggers it: After action 10
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: Lifecycle Stage (lifecyclestage); lists: none detected

DATA MEANING:

• Lifecycle Stage (lifecyclestage): The qualification of companies to sales readiness throughout the buying journey

ACTION EVIDENCE:

• Action category: set_property
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Sets HubSpot property values
• Returned action type: SINGLE_CONNECTION
• Returned field keys: association, property_name, value
• property_name: lifecyclestage
• value: static value Marketing Qualified Lead

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• Lifecycle Stage (lifecyclestage) is set or updated; value: static value Marketing Qualified Lead; confidence: high. Purpose: The qualification of companies to sales readiness throughout the buying journey

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 9 - Action 12

• What happens: Runs custom code; 21 inputs; 0 outputs
• What triggers it: After action 11
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: coreApi, join; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: custom_code
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Runs custom code
• Returned action type: CUSTOM_CODE

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• Inputs used by code: company, coreApi, download_name, hs_lead_name, hs_lead_type, hs_pipeline, hs_pipeline_stage, join, n4f_assigned_owner_touchpoint, n4f_booth_protocoll, n4f_business_line, n4f_campaign_owner, n4f_date_of_conversion, n4f_last_marketing_touchpoint_date, n4f_lead_message, n4f_lead_region_country, n4f_lead_source_level_1, n4f_lead_source_level_2, n4f_priority_label, n4f_region_country, n4f_touchpoint_name_dd, n4f_touchpoint_type, name

• Conditions detected in code: Code condition: if (obj !== null) console.log([${ts()}] INFO Lead-from-Touchpoint ${msg} ${safeJSON(obj)}); Code condition: if (obj !== null) console.warn([${ts()}] WARN Lead-from-Touchpoint ${msg} ${safeJSON(obj)}); Code condition: if (obj !== null) console.error([${ts()}] ERROR Lead-from-Touchpoint ${msg} ${safeJSON(obj)}); Code condition: if (s == null) return String(s); Code condition: if (!ra) return defMs; Code condition: if (!Number.isNaN(sec)) return Math.max(defMs, sec * 1000); Code condition: if (!retryable

  attempt >= maxRetries) throw e; Code condition: if (DEBUG) log((DEBUG) Read ${objectType} ${objectId} properties:, obj?.properties

  {}); Code condition: if (!leadPropCache[propName]) { Code condition: if (inputValue == null

  String(inputValue).trim() === “”) return null; Code condition: if (!DEBUG) return raw; Code condition: if (found) return found.value;

• CRM/API operations detected: creates records or resources, creates, removes, or checks associations
• Concrete CRM operations: associate: associations, objects, properties; create: associations, objects, properties; read by ID: associations, objects, properties
• Search/filter evidence: none detected
• Data transformations: calculates or formats dates, combines multiple values, converts values to numbers, filters collections, maps collections into derived values, normalizes text to lowercase, removes surrounding whitespace, replaces or cleans text patterns, serializes data as JSON, splits a value into parts
• Outputs returned to workflow: none detected
• HubSpot CRM objects affected or referenced: associations, objects, properties
• Associations handled: association logic referenced in custom code
• Workflow control: can exit without producing outputs, can fail the action explicitly, contains asynchronous execution
• Safeguards/error handling: error or warning logging, explicit error throwing, guard clauses or missing-value checks, structured response handling, try/catch error handling, checks missing values, has catch block, logs errors, mentions retry or rate-limit handling, throws errors
• Imports: @hubspot/api-client
• External systems/hosts: none detected
• External call evidence: none detected
• HTTP methods in code: none detected
• Secrets configured: 2
• Code evidence: 397 lines returned; code body analyzed but omitted from docs

Step 10 - Action 14

• What happens: Runs a connected HubSpot workflow action
• What triggers it: After action 12
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: connected_action
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Runs a connected HubSpot workflow action
• Returned action type: SINGLE_CONNECTION
• Returned field keys: delta, time_unit

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 11 - Action 13

• What happens: Branches based on HubSpot list membership; 2 branches
• What triggers it: After action 14
• System condition: 2 branch condition(s) returned by HubSpot.
• What data is used: properties: Lead Name (hs_lead_name); lists: none detected

DATA MEANING:

• Lead Name (hs_lead_name): The full name of the lead.

ACTION EVIDENCE:

• Action category: list_branch
• Detected intent: Branches based on HubSpot list membership
• Returned action type: LIST_BRANCH

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• Branch: Lead known
  • Condition summary: Lead known
  • Default branch: no
  • Next action IDs: 51
  • Referenced properties: Lead Name (hs_lead_name)
  • Referenced lists: none detected
  • Filter-like criteria returned: 3
  • Returned branch logic:
    • OR group
      • AND group
        • AND group
          • Lead Name is known
• Branch: Lead unknown
  • Condition summary: Lead unknown
  • Default branch: yes
  • Next action IDs: 19
  • Referenced properties: none detected
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch name: Lead unknown
      • Next action: 19

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 12 - Action 19

• What happens: Runs a connected HubSpot workflow action
• What triggers it: After action 13
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: connected_action
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Runs a connected HubSpot workflow action
• Returned action type: SINGLE_CONNECTION
• Returned field keys: delta, time_unit

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 13 - Action 96

• What happens: Runs custom code; 21 inputs; 0 outputs
• What triggers it: After action 19
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: coreApi, join; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: custom_code
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Runs custom code
• Returned action type: CUSTOM_CODE

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• Inputs used by code: company, coreApi, download_name, hs_lead_name, hs_lead_type, hs_pipeline, hs_pipeline_stage, join, n4f_assigned_owner_touchpoint, n4f_booth_protocoll, n4f_business_line, n4f_campaign_owner, n4f_date_of_conversion, n4f_last_marketing_touchpoint_date, n4f_lead_message, n4f_lead_region_country, n4f_lead_source_level_1, n4f_lead_source_level_2, n4f_priority_label, n4f_region_country, n4f_touchpoint_name_dd, n4f_touchpoint_type, name

• Conditions detected in code: Code condition: if (obj !== null) console.log([${ts()}] INFO Lead-from-Touchpoint ${msg} ${safeJSON(obj)}); Code condition: if (obj !== null) console.warn([${ts()}] WARN Lead-from-Touchpoint ${msg} ${safeJSON(obj)}); Code condition: if (obj !== null) console.error([${ts()}] ERROR Lead-from-Touchpoint ${msg} ${safeJSON(obj)}); Code condition: if (s == null) return String(s); Code condition: if (!ra) return defMs; Code condition: if (!Number.isNaN(sec)) return Math.max(defMs, sec * 1000); Code condition: if (!retryable

  attempt >= maxRetries) throw e; Code condition: if (DEBUG) log((DEBUG) Read ${objectType} ${objectId} properties:, obj?.properties

  {}); Code condition: if (!leadPropCache[propName]) { Code condition: if (inputValue == null

  String(inputValue).trim() === “”) return null; Code condition: if (!DEBUG) return raw; Code condition: if (found) return found.value;

• CRM/API operations detected: creates records or resources, creates, removes, or checks associations
• Concrete CRM operations: associate: associations, objects, properties; create: associations, objects, properties; read by ID: associations, objects, properties
• Search/filter evidence: none detected
• Data transformations: calculates or formats dates, combines multiple values, converts values to numbers, filters collections, maps collections into derived values, normalizes text to lowercase, removes surrounding whitespace, replaces or cleans text patterns, serializes data as JSON, splits a value into parts
• Outputs returned to workflow: none detected
• HubSpot CRM objects affected or referenced: associations, objects, properties
• Associations handled: association logic referenced in custom code
• Workflow control: can exit without producing outputs, can fail the action explicitly, contains asynchronous execution
• Safeguards/error handling: error or warning logging, explicit error throwing, guard clauses or missing-value checks, structured response handling, try/catch error handling, checks missing values, has catch block, logs errors, mentions retry or rate-limit handling, throws errors
• Imports: @hubspot/api-client
• External systems/hosts: none detected
• External call evidence: none detected
• HTTP methods in code: none detected
• Secrets configured: 2
• Code evidence: 397 lines returned; code body analyzed but omitted from docs

Step 14 - Action 16

• What happens: Runs a connected HubSpot workflow action
• What triggers it: After action 96
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: connected_action
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Runs a connected HubSpot workflow action
• Returned action type: SINGLE_CONNECTION
• Returned field keys: delta, time_unit

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 15 - Action 17

• What happens: Branches based on HubSpot list membership; 2 branches
• What triggers it: After action 16
• System condition: 2 branch condition(s) returned by HubSpot.
• What data is used: properties: Lead Name (hs_lead_name); lists: none detected

DATA MEANING:

• Lead Name (hs_lead_name): The full name of the lead.

ACTION EVIDENCE:

• Action category: list_branch
• Detected intent: Branches based on HubSpot list membership
• Returned action type: LIST_BRANCH

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• Branch: Lead known
  • Condition summary: Lead known
  • Default branch: no
  • Next action IDs: 50
  • Referenced properties: Lead Name (hs_lead_name)
  • Referenced lists: none detected
  • Filter-like criteria returned: 3
  • Returned branch logic:
    • OR group
      • AND group
        • AND group
          • Lead Name is known
• Branch: Lead unknown
  • Condition summary: Lead unknown
  • Default branch: yes
  • Next action IDs: 18
  • Referenced properties: none detected
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch name: Lead unknown
      • Next action: 18

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 16 - Action 18

• What happens: Sends an internal notification
• What triggers it: After action 17
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: internal_notification
• Detected intent: Sends an internal notification
• Returned action type: SINGLE_CONNECTION
• Returned field keys: body, subject, team_ids
• subject: ALARM- Lead creation failed - Re-attempting branch
• team_ids: Demand-Gen & CRM

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 17 - Action 50

• What happens: Sends an internal notification
• What triggers it: After action 17
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: internal_notification
• Detected intent: Sends an internal notification
• Returned action type: SINGLE_CONNECTION
• Returned field keys: body, subject, team_ids
• subject: Re-attempting lead created
• team_ids: Demand-Gen & CRM

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 18 - Action 51

• What happens: Sends an internal notification
• What triggers it: After action 13
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: internal_notification
• Detected intent: Sends an internal notification
• Returned action type: SINGLE_CONNECTION
• Returned field keys: body, subject, team_ids
• subject: Re-attempting lead created
• team_ids: Demand-Gen & CRM

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 19 - Action 101

• What happens: Branches based on HubSpot list membership; 2 branches
• What triggers it: After action 2
• System condition: 2 branch condition(s) returned by HubSpot.
• What data is used: properties: Lifecycle Stage (lifecyclestage); lists: none detected

DATA MEANING:

• Lifecycle Stage (lifecyclestage): The qualification of companies to sales readiness throughout the buying journey

ACTION EVIDENCE:

• Action category: list_branch
• Detected intent: Branches based on HubSpot list membership
• Returned action type: LIST_BRANCH

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• Branch: lifecycle stage low
  • Condition summary: lifecycle stage low
  • Default branch: no
  • Next action IDs: 102
  • Referenced properties: Lifecycle Stage (lifecyclestage)
  • Referenced lists: none detected
  • Filter-like criteria returned: 3
  • Returned branch logic:
    • OR group
      • AND group
        • AND group
          • Lifecycle Stage is none of Evangelist, Sales Accepted Lead, Opportunity, Sales Qualified Lead, Customer
• Branch: lifecycle stage high
  • Condition summary: lifecycle stage high
  • Default branch: yes
  • Next action IDs: 100
  • Referenced properties: none detected
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch name: lifecycle stage high
      • Next action: 100

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 20 - Action 100

• What happens: Runs custom code; 22 inputs; 0 outputs
• What triggers it: After action 101
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: custom_code
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Runs custom code
• Returned action type: CUSTOM_CODE

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• Inputs used by code: company, download_name, hs_lead_name, hs_lead_type, hs_pipeline, hs_pipeline_stage, n4f_assigned_owner_touchpoint, n4f_booth_protocoll, n4f_business_line, n4f_campaign_owner, n4f_date_of_conversion, n4f_event_quality_of_contact, n4f_last_marketing_touchpoint_date, n4f_lead_message, n4f_lead_region_country, n4f_lead_source_level_1, n4f_lead_source_level_2, n4f_priority_label, n4f_region_country, n4f_touchpoint_name_dd, n4f_touchpoint_type, name

• Conditions detected in code: Code condition: if (!retryable

  attempt >= retries) throw e; Code condition: if (!tpId) return callback({ ok: true }); Code condition: if (existingLeadId) { Code condition: if (!contactId) throw new Error(“No Contact associated.”); Code condition: if (companyId) { Code condition: if (tpAssignedOwner && /^\d+$/.test(tpAssignedOwner)) { Code condition: if (tpType) { Code condition: if (tpNameDD) { Code condition: if (tpBoothMsg) { Code condition: if (tpCampOwner) { Code condition: if (String(tpEventQuality).toLowerCase().trim() === “sales potential”) { Code condition: if (tpConversionDate) {

• CRM/API operations detected: creates records or resources, creates, removes, or checks associations
• Concrete CRM operations: associate: associations, objects; create: associations, objects; read by ID: associations, objects
• Search/filter evidence: none detected
• Data transformations: calculates or formats dates, combines multiple values, filters collections, maps collections into derived values, normalizes text to lowercase, removes surrounding whitespace, splits a value into parts
• Outputs returned to workflow: none detected
• HubSpot CRM objects affected or referenced: associations, objects
• Associations handled: association logic referenced in custom code
• Workflow control: can fail the action explicitly, contains asynchronous execution
• Safeguards/error handling: error or warning logging, explicit error throwing, guard clauses or missing-value checks, structured response handling, try/catch error handling, checks missing values, has catch block, logs errors, mentions retry or rate-limit handling, throws errors
• Imports: @hubspot/api-client
• External systems/hosts: none detected
• External call evidence: none detected
• HTTP methods in code: none detected
• Secrets configured: 2
• Code evidence: 279 lines returned; code body analyzed but omitted from docs

Step 21 - Action 105

• What happens: Runs a connected HubSpot workflow action
• What triggers it: After action 100
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: connected_action
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Runs a connected HubSpot workflow action
• Returned action type: SINGLE_CONNECTION
• Returned field keys: delta, time_unit

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 22 - Action 106

• What happens: Branches based on HubSpot list membership; 2 branches
• What triggers it: After action 105
• System condition: 2 branch condition(s) returned by HubSpot.
• What data is used: properties: Lead Name (hs_lead_name); lists: none detected

DATA MEANING:

• Lead Name (hs_lead_name): The full name of the lead.

ACTION EVIDENCE:

• Action category: list_branch
• Detected intent: Branches based on HubSpot list membership
• Returned action type: LIST_BRANCH

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• Branch: Lead known
  • Condition summary: Lead known
  • Default branch: no
  • Next action IDs: 103
  • Referenced properties: Lead Name (hs_lead_name)
  • Referenced lists: none detected
  • Filter-like criteria returned: 3
  • Returned branch logic:
    • OR group
      • AND group
        • AND group
          • Lead Name is known
• Branch: Lead unknown
  • Condition summary: Lead unknown
  • Default branch: yes
  • Next action IDs: 107
  • Referenced properties: none detected
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch name: Lead unknown
      • Next action: 107

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 23 - Action 103

• What happens: Sends an internal notification
• What triggers it: After action 106
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: internal_notification
• Detected intent: Sends an internal notification
• Returned action type: SINGLE_CONNECTION
• Returned field keys: body, subject, team_ids
• subject: unrated lead created
• team_ids: Demand-Gen & CRM

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 24 - Action 107

• What happens: Runs a connected HubSpot workflow action
• What triggers it: After action 106
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: connected_action
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Runs a connected HubSpot workflow action
• Returned action type: SINGLE_CONNECTION
• Returned field keys: delta, time_unit

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 25 - Action 112

• What happens: Runs custom code; 22 inputs; 0 outputs
• What triggers it: After action 107
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: custom_code
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Runs custom code
• Returned action type: CUSTOM_CODE

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• Inputs used by code: company, download_name, hs_lead_name, hs_lead_type, hs_pipeline, hs_pipeline_stage, n4f_assigned_owner_touchpoint, n4f_booth_protocoll, n4f_business_line, n4f_campaign_owner, n4f_date_of_conversion, n4f_event_quality_of_contact, n4f_last_marketing_touchpoint_date, n4f_lead_message, n4f_lead_region_country, n4f_lead_source_level_1, n4f_lead_source_level_2, n4f_priority_label, n4f_region_country, n4f_touchpoint_name_dd, n4f_touchpoint_type, name

• Conditions detected in code: Code condition: if (!retryable

  attempt >= retries) throw e; Code condition: if (!tpId) return callback({ ok: true }); Code condition: if (existingLeadId) { Code condition: if (!contactId) throw new Error(“No Contact associated.”); Code condition: if (companyId) { Code condition: if (tpAssignedOwner && /^\d+$/.test(tpAssignedOwner)) { Code condition: if (tpType) { Code condition: if (tpNameDD) { Code condition: if (tpBoothMsg) { Code condition: if (tpCampOwner) { Code condition: if (String(tpEventQuality).toLowerCase().trim() === “sales potential”) { Code condition: if (tpConversionDate) {

• CRM/API operations detected: creates records or resources, creates, removes, or checks associations
• Concrete CRM operations: associate: associations, objects; create: associations, objects; read by ID: associations, objects
• Search/filter evidence: none detected
• Data transformations: calculates or formats dates, combines multiple values, filters collections, maps collections into derived values, normalizes text to lowercase, removes surrounding whitespace, splits a value into parts
• Outputs returned to workflow: none detected
• HubSpot CRM objects affected or referenced: associations, objects
• Associations handled: association logic referenced in custom code
• Workflow control: can fail the action explicitly, contains asynchronous execution
• Safeguards/error handling: error or warning logging, explicit error throwing, guard clauses or missing-value checks, structured response handling, try/catch error handling, checks missing values, has catch block, logs errors, mentions retry or rate-limit handling, throws errors
• Imports: @hubspot/api-client
• External systems/hosts: none detected
• External call evidence: none detected
• HTTP methods in code: none detected
• Secrets configured: 2
• Code evidence: 279 lines returned; code body analyzed but omitted from docs

Step 26 - Action 108

• What happens: Runs a connected HubSpot workflow action
• What triggers it: After action 112
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: connected_action
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Runs a connected HubSpot workflow action
• Returned action type: SINGLE_CONNECTION
• Returned field keys: delta, time_unit

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 27 - Action 109

• What happens: Branches based on HubSpot list membership; 2 branches
• What triggers it: After action 108
• System condition: 2 branch condition(s) returned by HubSpot.
• What data is used: properties: Lead Name (hs_lead_name); lists: none detected

DATA MEANING:

• Lead Name (hs_lead_name): The full name of the lead.

ACTION EVIDENCE:

• Action category: list_branch
• Detected intent: Branches based on HubSpot list membership
• Returned action type: LIST_BRANCH

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• Branch: Lead known
  • Condition summary: Lead known
  • Default branch: no
  • Next action IDs: 104
  • Referenced properties: Lead Name (hs_lead_name)
  • Referenced lists: none detected
  • Filter-like criteria returned: 3
  • Returned branch logic:
    • OR group
      • AND group
        • AND group
          • Lead Name is known
• Branch: Lead unknown
  • Condition summary: Lead unknown
  • Default branch: yes
  • Next action IDs: 110
  • Referenced properties: none detected
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch name: Lead unknown
      • Next action: 110

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 28 - Action 104

• What happens: Sends an internal notification
• What triggers it: After action 109
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: internal_notification
• Detected intent: Sends an internal notification
• Returned action type: SINGLE_CONNECTION
• Returned field keys: body, subject, team_ids
• subject: unrated lead created
• team_ids: Demand-Gen & CRM

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 29 - Action 110

• What happens: Sends an internal notification
• What triggers it: After action 109
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: internal_notification
• Detected intent: Sends an internal notification
• Returned action type: SINGLE_CONNECTION
• Returned field keys: body, subject, team_ids
• subject: ALARM- Lead creation failed - could not decide branch
• team_ids: Demand-Gen & CRM

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 30 - Action 102

• What happens: Sets HubSpot property values; properties: lifecyclestage = static value Marketing Qualified Lead
• What triggers it: After action 101
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: Lifecycle Stage (lifecyclestage); lists: none detected

DATA MEANING:

• Lifecycle Stage (lifecyclestage): The qualification of companies to sales readiness throughout the buying journey

ACTION EVIDENCE:

• Action category: set_property
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Sets HubSpot property values
• Returned action type: SINGLE_CONNECTION
• Returned field keys: association, property_name, value
• property_name: lifecyclestage
• value: static value Marketing Qualified Lead

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• Lifecycle Stage (lifecyclestage) is set or updated; value: static value Marketing Qualified Lead; confidence: high. Purpose: The qualification of companies to sales readiness throughout the buying journey

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 31 - Action 66

• What happens: Branches based on HubSpot list membership; 3 branches; 2 list dependencies
• What triggers it: After action 2
• System condition: 3 branch condition(s) returned by HubSpot.
• What data is used: properties: none detected; lists: ELEVATE-Contacts with open outbound leads, ELEVATE-Contacts with open pre-scheduled meeting leads

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: list_branch
• Detected intent: Branches based on HubSpot list membership
• Returned action type: LIST_BRANCH

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• Branch: outbound
  • Condition summary: outbound
  • Default branch: no
  • Next action IDs: 67
  • Referenced properties: none detected
  • Referenced lists: 16614
  • Filter-like criteria returned: 2
  • Returned branch logic:
    • OR group
      • AND group
        • AND group
          • ELEVATE-Contacts with open outbound leads is in list 16614
• Branch: pre-scheduled
  • Condition summary: pre-scheduled
  • Default branch: no
  • Next action IDs: 81
  • Referenced properties: none detected
  • Referenced lists: 16616
  • Filter-like criteria returned: 2
  • Returned branch logic:
    • OR group
      • AND group
        • AND group
          • ELEVATE-Contacts with open pre-scheduled meeting leads is in list 16616
• Branch: default branch
  • Condition summary: default branch
  • Default branch: yes
  • Next action IDs: 37
  • Referenced properties: none detected
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch name: default branch
      • Next action: 37

LIST LOGIC:

• ELEVATE-Contacts with open outbound leads (16614)
  • Business meaning: System-derived role: attribution. Used to segment records by source, campaign, channel, or touchpoint evidence returned by HubSpot filters.
  • Filters: 2
  • Referenced properties: hs_pipeline_stage, n4f_lead_source_level_1
  • Filter logic:
    • OR group
      • AND group
        • AND group
          • Lead stage is none of Qualified, Disqualified
          • 4f_Lead Source Level 1 is any of Outbound
• ELEVATE-Contacts with open pre-scheduled meeting leads (16616)
  • Business meaning: System-derived role: attribution. Used to segment records by source, campaign, channel, or touchpoint evidence returned by HubSpot filters.
  • Filters: 2
  • Referenced properties: hs_pipeline_stage, n4f_lead_source_level_1
  • Filter logic:
    • OR group
      • AND group
        • AND group
          • Lead stage is none of Qualified, Disqualified
          • 4f_Lead Source Level 1 is any of Pre-scheduled event meeting

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 32 - Action 37

• What happens: Runs custom code; 18 inputs; 0 outputs
• What triggers it: After action 66
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: join; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: custom_code
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Runs custom code
• Returned action type: CUSTOM_CODE

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• Inputs used by code: download_name, hs_lead_name, hs_lead_type, hs_pipeline, hs_pipeline_stage, join, n4f_assigned_owner_touchpoint, n4f_booth_protocoll, n4f_campaign_owner, n4f_lead_document, n4f_lead_message, n4f_lead_region_country, n4f_lead_source_level_1, n4f_lead_source_level_2, n4f_region_country, n4f_touchpoint_document, n4f_touchpoint_name_dd, n4f_touchpoint_type, name
• Conditions detected in code: Code condition: if (obj !== null) { Code condition: if (obj !== null) { Code condition: if (!tpId) { Code condition: if (!contactId) { Code condition: if (companyId) { Code condition: if (tpAssignedOwner && /^\d+$/.test(String(tpAssignedOwner))) { Code condition: if (tpType) { Code condition: if (tpNameDD) { Code condition: if (tpBoothProtocol) { Code condition: if (tpCampaignOwner) { Code condition: if (String(tpEventQuality).toLowerCase().trim() === “sales potential”) { Code condition: if (tpConversionDate) {
• CRM/API operations detected: creates records or resources, creates, removes, or checks associations
• Concrete CRM operations: associate: associations, objects; create: associations, objects; read by ID: associations, objects
• Search/filter evidence: none detected
• Data transformations: calculates or formats dates, combines multiple values, filters collections, maps collections into derived values, normalizes text to lowercase, removes surrounding whitespace, splits a value into parts
• Outputs returned to workflow: none detected
• HubSpot CRM objects affected or referenced: associations, objects
• Associations handled: association logic referenced in custom code
• Workflow control: can fail the action explicitly, contains asynchronous execution
• Safeguards/error handling: error or warning logging, explicit error throwing, guard clauses or missing-value checks, structured response handling, try/catch error handling, checks missing values, has catch block, logs errors, throws errors
• Imports: @hubspot/api-client
• External systems/hosts: none detected
• External call evidence: none detected
• HTTP methods in code: none detected
• Secrets configured: 2
• Code evidence: 357 lines returned; code body analyzed but omitted from docs

Step 33 - Action 38

• What happens: Runs a connected HubSpot workflow action
• What triggers it: After action 37
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: connected_action
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Runs a connected HubSpot workflow action
• Returned action type: SINGLE_CONNECTION
• Returned field keys: delta, time_unit

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 34 - Action 39

• What happens: Branches based on HubSpot list membership; 2 branches
• What triggers it: After action 38
• System condition: 2 branch condition(s) returned by HubSpot.
• What data is used: properties: Lead Name (hs_lead_name); lists: none detected

DATA MEANING:

• Lead Name (hs_lead_name): The full name of the lead.

ACTION EVIDENCE:

• Action category: list_branch
• Detected intent: Branches based on HubSpot list membership
• Returned action type: LIST_BRANCH

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• Branch: Lead known
  • Condition summary: Lead known
  • Default branch: no
  • Next action IDs: 44
  • Referenced properties: Lead Name (hs_lead_name)
  • Referenced lists: none detected
  • Filter-like criteria returned: 3
  • Returned branch logic:
    • OR group
      • AND group
        • AND group
          • Lead Name is known
• Branch: Lead unknown
  • Condition summary: Lead unknown
  • Default branch: yes
  • Next action IDs: 41
  • Referenced properties: none detected
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch name: Lead unknown
      • Next action: 41

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 35 - Action 41

• What happens: Runs a connected HubSpot workflow action
• What triggers it: After action 39
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: connected_action
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Runs a connected HubSpot workflow action
• Returned action type: SINGLE_CONNECTION
• Returned field keys: delta, time_unit

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 36 - Action 42

• What happens: Branches based on HubSpot list membership; 2 branches
• What triggers it: After action 41
• System condition: 2 branch condition(s) returned by HubSpot.
• What data is used: properties: Lead Name (hs_lead_name); lists: none detected

DATA MEANING:

• Lead Name (hs_lead_name): The full name of the lead.

ACTION EVIDENCE:

• Action category: list_branch
• Detected intent: Branches based on HubSpot list membership
• Returned action type: LIST_BRANCH

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• Branch: Lead known
  • Condition summary: Lead known
  • Default branch: no
  • Next action IDs: 45
  • Referenced properties: Lead Name (hs_lead_name)
  • Referenced lists: none detected
  • Filter-like criteria returned: 3
  • Returned branch logic:
    • OR group
      • AND group
        • AND group
          • Lead Name is known
• Branch: Lead unknown
  • Condition summary: Lead unknown
  • Default branch: yes
  • Next action IDs: 40
  • Referenced properties: none detected
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch name: Lead unknown
      • Next action: 40

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 37 - Action 40

• What happens: Sends an internal notification
• What triggers it: After action 42
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: internal_notification
• Detected intent: Sends an internal notification
• Returned action type: SINGLE_CONNECTION
• Returned field keys: body, subject, team_ids
• subject: ALARM- Lead association failed for existing lead
• team_ids: Demand-Gen & CRM

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 38 - Action 45

• What happens: Sends an internal notification
• What triggers it: After action 42
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: internal_notification
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Sends an internal notification
• Returned action type: SINGLE_CONNECTION
• Returned field keys: body, subject, team_ids
• subject: No lead created but lead was updated
• team_ids: Demand-Gen & CRM

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 39 - Action 53

• What happens: Branches based on HubSpot list membership; 2 branches
• What triggers it: After action 45
• System condition: 2 branch condition(s) returned by HubSpot.
• What data is used: properties: 4f_Lead Source Level 1 (n4f_lead_source_level_1); lists: none detected

DATA MEANING:

• 4f_Lead Source Level 1 (n4f_lead_source_level_1): used for attribution of marketing leads, synchronized with touchpoint types (and deal sources)

ACTION EVIDENCE:

• Action category: list_branch
• Detected intent: Branches based on HubSpot list membership
• Returned action type: LIST_BRANCH

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• Branch: outbound
  • Condition summary: outbound
  • Default branch: no
  • Next action IDs: 54
  • Referenced properties: 4f_Lead Source Level 1 (n4f_lead_source_level_1)
  • Referenced lists: none detected
  • Filter-like criteria returned: 3
  • Returned branch logic:
    • OR group
      • AND group
        • AND group
          • 4f_Lead Source Level 1 is any of Outbound
• Branch: not outbound
  • Condition summary: not outbound
  • Default branch: yes
  • Next action IDs: 55
  • Referenced properties: none detected
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch name: not outbound
      • Next action: 55

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 40 - Action 54

• What happens: Sets HubSpot property values; properties: n4f_conversion_source = static value Yes
• What triggers it: After action 53
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: 4f_Conversion source (n4f_conversion_source); lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: set_property
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Sets HubSpot property values
• Returned action type: SINGLE_CONNECTION
• Returned field keys: property_name, value
• property_name: n4f_conversion_source
• value: static value Yes

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• 4f_Conversion source (n4f_conversion_source) is set or updated; value: static value Yes; confidence: high.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 41 - Action 55

• What happens: Branches based on HubSpot list membership; 1 branches
• What triggers it: After action 54
• System condition: 1 branch condition(s) returned by HubSpot.
• What data is used: properties: Lifecycle Stage (lifecyclestage); lists: none detected

DATA MEANING:

• Lifecycle Stage (lifecyclestage): The qualification of companies to sales readiness throughout the buying journey

ACTION EVIDENCE:

• Action category: list_branch
• Detected intent: Branches based on HubSpot list membership
• Returned action type: LIST_BRANCH

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• Branch: lifecycle below MQL
  • Condition summary: lifecycle below MQL
  • Default branch: no
  • Next action IDs: 56
  • Referenced properties: Lifecycle Stage (lifecyclestage)
  • Referenced lists: none detected
  • Filter-like criteria returned: 3
  • Returned branch logic:
    • OR group
      • AND group
        • AND group
          • Lifecycle Stage is any of Subscriber, New, Lead

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 42 - Action 56

• What happens: Sets HubSpot property values; properties: lifecyclestage = static value Marketing Qualified Lead
• What triggers it: After action 55
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: Lifecycle Stage (lifecyclestage); lists: none detected

DATA MEANING:

• Lifecycle Stage (lifecyclestage): The qualification of companies to sales readiness throughout the buying journey

ACTION EVIDENCE:

• Action category: set_property
• Detected intent: Sets HubSpot property values
• Returned action type: SINGLE_CONNECTION
• Returned field keys: association, property_name, value
• property_name: lifecyclestage
• value: static value Marketing Qualified Lead

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• Lifecycle Stage (lifecyclestage) is set or updated; value: static value Marketing Qualified Lead; confidence: high. Purpose: The qualification of companies to sales readiness throughout the buying journey

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 43 - Action 44

• What happens: Sends an internal notification
• What triggers it: After action 39
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: internal_notification
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Sends an internal notification
• Returned action type: SINGLE_CONNECTION
• Returned field keys: body, subject, team_ids
• subject: No lead created but lead was updated
• team_ids: Demand-Gen & CRM

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 44 - Action 67

• What happens: Runs custom code; 21 inputs; 0 outputs
• What triggers it: After action 66
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: coreApi, Object create date/time (hs_createdate), Lead stage (hs_pipeline_stage), Owner (hubspot_owner_id), join, 4f_Business line (n4f_business_line), 4f_campaign owner (n4f_campaign_owner), 4f_Lead interest (n4f_lead__interest); lists: none detected

DATA MEANING:

• Object create date/time (hs_createdate): The date and time at which this object was created. This value is automatically set by HubSpot and may not be modified.
• Lead stage (hs_pipeline_stage): shows the pipeline stages of the lead pipeline. indicates which stage the lead is in
• Owner (hubspot_owner_id): The owner of the object.
• 4f_Business line (n4f_business_line): This property reflects the 4flow business lines and is used whenever a clear association with one of our business lines/services is possible. Also used at events in booth protocols, etc.
• 4f_campaign owner (n4f_campaign_owner): Depreciated property was used to identify internal campaign stakeholders (business line representatives who requested/are responsible for a campaign).
• 4f_Lead interest (n4f_lead__interest): collects all 4Flowers who e.g. were former owners or assigned other owners - for tracking purposes

ACTION EVIDENCE:

• Action category: custom_code
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Runs custom code
• Returned action type: CUSTOM_CODE

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• Inputs used by code: coreApi, download_name, hs_createdate, hs_lead_name, hs_lead_type, hs_pipeline, hs_pipeline_stage, hubspot_owner_id, join, n4f_assigned_owner_touchpoint, n4f_booth_protocoll, n4f_business_line, n4f_campaign_owner, n4f_last_marketing_touchpoint_date, n4f_lead__interest, n4f_lead_document, n4f_lead_message, n4f_lead_region_country, n4f_lead_source_level_1, n4f_lead_source_level_2, n4f_priority_label, n4f_region_country, n4f_touchpoint_document, n4f_touchpoint_name_dd, n4f_touchpoint_type, name

• Conditions detected in code: Code condition: if (obj !== null) console.log([${ts()}] ${msg} ${safeJSON(obj)}); Code condition: if (obj !== null) console.warn([${ts()}] WARN: ${msg} ${safeJSON(obj)}); Code condition: if (obj !== null) console.error([${ts()}] ERROR: ${msg} ${safeJSON(obj)}); Code condition: if (!list.includes(id)) list.push(id); Code condition: if (!leadPropCache[propName]) { Code condition: if (inputValue == null

  String(inputValue).trim() === “”) return null; Code condition: if (found) return found.value; Code condition: if (found) return found.value; Code condition: if (found) return found.value; Code condition: if (manualCandidate) { Code condition: if (validatedManual) return validatedManual; Code condition: if (current && current === String(prevOwnerId)) {

• CRM/API operations detected: creates records or resources, creates, removes, or checks associations, updates records or resources
• Concrete CRM operations: associate: associations, objects, properties; create: associations, objects, properties; read by ID: associations, objects, properties; update: associations, objects, properties
• Search/filter evidence: none detected
• Data transformations: calculates or formats dates, combines multiple values, converts values to numbers, filters collections, maps collections into derived values, normalizes text to lowercase, removes surrounding whitespace, replaces or cleans text patterns, serializes data as JSON, splits a value into parts
• Outputs returned to workflow: none detected
• HubSpot CRM objects affected or referenced: associations, objects, properties
• Associations handled: association logic referenced in custom code
• Workflow control: can exit without producing outputs, can fail the action explicitly, contains asynchronous execution
• Safeguards/error handling: error or warning logging, explicit error throwing, guard clauses or missing-value checks, structured response handling, try/catch error handling, checks missing values, has catch block, logs errors, throws errors
• Imports: @hubspot/api-client
• External systems/hosts: none detected
• External call evidence: none detected
• HTTP methods in code: none detected
• Secrets configured: 2
• Code evidence: 455 lines returned; code body analyzed but omitted from docs

Step 45 - Action 68

• What happens: Runs a connected HubSpot workflow action
• What triggers it: After action 67
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: connected_action
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Runs a connected HubSpot workflow action
• Returned action type: SINGLE_CONNECTION
• Returned field keys: delta, time_unit

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 46 - Action 69

• What happens: Branches based on HubSpot list membership; 2 branches
• What triggers it: After action 68
• System condition: 2 branch condition(s) returned by HubSpot.
• What data is used: properties: Lead Name (hs_lead_name), 4f_Lead Source Level 1 (n4f_lead_source_level_1); lists: none detected

DATA MEANING:

• Lead Name (hs_lead_name): The full name of the lead.
• 4f_Lead Source Level 1 (n4f_lead_source_level_1): used for attribution of marketing leads, synchronized with touchpoint types (and deal sources)

ACTION EVIDENCE:

• Action category: list_branch
• Detected intent: Branches based on HubSpot list membership
• Returned action type: LIST_BRANCH

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• Branch: Lead known
  • Condition summary: Lead known
  • Default branch: no
  • Next action IDs: 74
  • Referenced properties: Lead Name (hs_lead_name), 4f_Lead Source Level 1 (n4f_lead_source_level_1)
  • Referenced lists: none detected
  • Filter-like criteria returned: 6
  • Returned branch logic:
    • OR group
      • AND group
        • AND group
          • 4f_Lead Source Level 1 is any of Event booth meeting
        • AND group
          • Lead Name is known
• Branch: Lead unknown
  • Condition summary: Lead unknown
  • Default branch: yes
  • Next action IDs: 71
  • Referenced properties: none detected
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch name: Lead unknown
      • Next action: 71

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 47 - Action 71

• What happens: Runs a connected HubSpot workflow action
• What triggers it: After action 69
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: connected_action
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Runs a connected HubSpot workflow action
• Returned action type: SINGLE_CONNECTION
• Returned field keys: delta, time_unit

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 48 - Action 97

• What happens: Runs custom code; 21 inputs; 0 outputs
• What triggers it: After action 71
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: coreApi, Object create date/time (hs_createdate), Lead stage (hs_pipeline_stage), Owner (hubspot_owner_id), join, 4f_Business line (n4f_business_line), 4f_campaign owner (n4f_campaign_owner), 4f_Lead interest (n4f_lead__interest); lists: none detected

DATA MEANING:

• Object create date/time (hs_createdate): The date and time at which this object was created. This value is automatically set by HubSpot and may not be modified.
• Lead stage (hs_pipeline_stage): shows the pipeline stages of the lead pipeline. indicates which stage the lead is in
• Owner (hubspot_owner_id): The owner of the object.
• 4f_Business line (n4f_business_line): This property reflects the 4flow business lines and is used whenever a clear association with one of our business lines/services is possible. Also used at events in booth protocols, etc.
• 4f_campaign owner (n4f_campaign_owner): Depreciated property was used to identify internal campaign stakeholders (business line representatives who requested/are responsible for a campaign).
• 4f_Lead interest (n4f_lead__interest): collects all 4Flowers who e.g. were former owners or assigned other owners - for tracking purposes

ACTION EVIDENCE:

• Action category: custom_code
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Runs custom code
• Returned action type: CUSTOM_CODE

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• Inputs used by code: coreApi, download_name, hs_createdate, hs_lead_name, hs_lead_type, hs_pipeline, hs_pipeline_stage, hubspot_owner_id, join, n4f_assigned_owner_touchpoint, n4f_booth_protocoll, n4f_business_line, n4f_campaign_owner, n4f_last_marketing_touchpoint_date, n4f_lead__interest, n4f_lead_document, n4f_lead_message, n4f_lead_region_country, n4f_lead_source_level_1, n4f_lead_source_level_2, n4f_priority_label, n4f_region_country, n4f_touchpoint_document, n4f_touchpoint_name_dd, n4f_touchpoint_type, name

• Conditions detected in code: Code condition: if (obj !== null) console.log([${ts()}] ${msg} ${safeJSON(obj)}); Code condition: if (obj !== null) console.warn([${ts()}] WARN: ${msg} ${safeJSON(obj)}); Code condition: if (obj !== null) console.error([${ts()}] ERROR: ${msg} ${safeJSON(obj)}); Code condition: if (!list.includes(id)) list.push(id); Code condition: if (!leadPropCache[propName]) { Code condition: if (inputValue == null

  String(inputValue).trim() === “”) return null; Code condition: if (found) return found.value; Code condition: if (found) return found.value; Code condition: if (found) return found.value; Code condition: if (manualCandidate) { Code condition: if (validatedManual) return validatedManual; Code condition: if (current && current === String(prevOwnerId)) {

• CRM/API operations detected: creates records or resources, creates, removes, or checks associations, updates records or resources
• Concrete CRM operations: associate: associations, objects, properties; create: associations, objects, properties; read by ID: associations, objects, properties; update: associations, objects, properties
• Search/filter evidence: none detected
• Data transformations: calculates or formats dates, combines multiple values, converts values to numbers, filters collections, maps collections into derived values, normalizes text to lowercase, removes surrounding whitespace, replaces or cleans text patterns, serializes data as JSON, splits a value into parts
• Outputs returned to workflow: none detected
• HubSpot CRM objects affected or referenced: associations, objects, properties
• Associations handled: association logic referenced in custom code
• Workflow control: can exit without producing outputs, can fail the action explicitly, contains asynchronous execution
• Safeguards/error handling: error or warning logging, explicit error throwing, guard clauses or missing-value checks, structured response handling, try/catch error handling, checks missing values, has catch block, logs errors, throws errors
• Imports: @hubspot/api-client
• External systems/hosts: none detected
• External call evidence: none detected
• HTTP methods in code: none detected
• Secrets configured: 2
• Code evidence: 455 lines returned; code body analyzed but omitted from docs

Step 49 - Action 72

• What happens: Branches based on HubSpot list membership; 2 branches
• What triggers it: After action 97
• System condition: 2 branch condition(s) returned by HubSpot.
• What data is used: properties: Lead Name (hs_lead_name); lists: none detected

DATA MEANING:

• Lead Name (hs_lead_name): The full name of the lead.

ACTION EVIDENCE:

• Action category: list_branch
• Detected intent: Branches based on HubSpot list membership
• Returned action type: LIST_BRANCH

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• Branch: Lead known
  • Condition summary: Lead known
  • Default branch: no
  • Next action IDs: 80
  • Referenced properties: Lead Name (hs_lead_name)
  • Referenced lists: none detected
  • Filter-like criteria returned: 3
  • Returned branch logic:
    • OR group
      • AND group
        • AND group
          • Lead Name is known
• Branch: Lead unknown
  • Condition summary: Lead unknown
  • Default branch: yes
  • Next action IDs: 70
  • Referenced properties: none detected
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch name: Lead unknown
      • Next action: 70

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 50 - Action 70

• What happens: Sends an internal notification
• What triggers it: After action 72
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: internal_notification
• Detected intent: Sends an internal notification
• Returned action type: SINGLE_CONNECTION
• Returned field keys: body, subject, team_ids
• subject: ALARM- Lead association & relabeling failed for existing Outreach lead
• team_ids: Demand-Gen & CRM

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 51 - Action 80

• What happens: Sends an internal notification
• What triggers it: After action 72
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: internal_notification
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Sends an internal notification
• Returned action type: SINGLE_CONNECTION
• Returned field keys: body, subject, team_ids
• subject: Outreach lead updated to Event booth
• team_ids: Demand-Gen & CRM

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 52 - Action 77

• What happens: Sets HubSpot property values; properties: n4f_conversion_source = static value Yes
• What triggers it: After action 80
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: 4f_Conversion source (n4f_conversion_source); lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: set_property
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Sets HubSpot property values
• Returned action type: SINGLE_CONNECTION
• Returned field keys: property_name, value
• property_name: n4f_conversion_source
• value: static value Yes

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• 4f_Conversion source (n4f_conversion_source) is set or updated; value: static value Yes; confidence: high.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 53 - Action 78

• What happens: Branches based on HubSpot list membership; 1 branches
• What triggers it: After action 77
• System condition: 1 branch condition(s) returned by HubSpot.
• What data is used: properties: Lifecycle Stage (lifecyclestage); lists: none detected

DATA MEANING:

• Lifecycle Stage (lifecyclestage): The qualification of companies to sales readiness throughout the buying journey

ACTION EVIDENCE:

• Action category: list_branch
• Detected intent: Branches based on HubSpot list membership
• Returned action type: LIST_BRANCH

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• Branch: lifecycle below MQL
  • Condition summary: lifecycle below MQL
  • Default branch: no
  • Next action IDs: 79
  • Referenced properties: Lifecycle Stage (lifecyclestage)
  • Referenced lists: none detected
  • Filter-like criteria returned: 3
  • Returned branch logic:
    • OR group
      • AND group
        • AND group
          • Lifecycle Stage is any of Subscriber, New, Lead

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 54 - Action 79

• What happens: Sets HubSpot property values; properties: lifecyclestage = static value Marketing Qualified Lead
• What triggers it: After action 78
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: Lifecycle Stage (lifecyclestage); lists: none detected

DATA MEANING:

• Lifecycle Stage (lifecyclestage): The qualification of companies to sales readiness throughout the buying journey

ACTION EVIDENCE:

• Action category: set_property
• Detected intent: Sets HubSpot property values
• Returned action type: SINGLE_CONNECTION
• Returned field keys: association, property_name, value
• property_name: lifecyclestage
• value: static value Marketing Qualified Lead

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• Lifecycle Stage (lifecyclestage) is set or updated; value: static value Marketing Qualified Lead; confidence: high. Purpose: The qualification of companies to sales readiness throughout the buying journey

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 55 - Action 74

• What happens: Sends an internal notification
• What triggers it: After action 69
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: internal_notification
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Sends an internal notification
• Returned action type: SINGLE_CONNECTION
• Returned field keys: body, subject, team_ids
• subject: Outreach lead updated to Event booth
• team_ids: Demand-Gen & CRM

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 56 - Action 81

• What happens: Runs custom code; 19 inputs; 0 outputs
• What triggers it: After action 66
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: coreApi, Object create date/time (hs_createdate), join; lists: none detected

DATA MEANING:

• Object create date/time (hs_createdate): The date and time at which this object was created. This value is automatically set by HubSpot and may not be modified.

ACTION EVIDENCE:

• Action category: custom_code
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Runs custom code
• Returned action type: CUSTOM_CODE

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• Inputs used by code: coreApi, download_name, hs_createdate, hs_lead_name, hs_lead_type, hs_pipeline, hs_pipeline_stage, join, n4f_assigned_owner_touchpoint, n4f_booth_protocoll, n4f_business_line, n4f_campaign_owner, n4f_lead_document, n4f_lead_message, n4f_lead_region_country, n4f_lead_source_level_1, n4f_lead_source_level_2, n4f_region_country, n4f_touchpoint_document, n4f_touchpoint_name_dd, n4f_touchpoint_type, name
• Conditions detected in code: Code condition: if (obj !== null) console.log([${ts()}] ${msg} ${safeJSON(obj)}); Code condition: if (!list.includes(id)) list.push(id); Code condition: if (!leadPropCache[propName]) { Code condition: if (!inputValue) return null; Code condition: if (found) return found.value; Code condition: if (found) return found.value; Code condition: if (found) return found.value; Code condition: if (resolved) return resolved; Code condition: if (fallback) return await resolveDropdownValue(client, propName, fallback); Code condition: if (!tpId) return callback({ ok: true }); Code condition: if (!contactId) throw new Error(“No associated Contact found for TP.”); Code condition: if (!leadIds.length) return callback({ ok: true });
• CRM/API operations detected: creates records or resources, creates, removes, or checks associations, updates records or resources
• Concrete CRM operations: associate: associations, objects, properties; create: associations, objects, properties; read by ID: associations, objects, properties; update: associations, objects, properties
• Search/filter evidence: none detected
• Data transformations: calculates or formats dates, combines multiple values, converts values to numbers, filters collections, maps collections into derived values, normalizes text to lowercase, removes surrounding whitespace, replaces or cleans text patterns, serializes data as JSON, splits a value into parts
• Outputs returned to workflow: none detected
• HubSpot CRM objects affected or referenced: associations, objects, properties
• Associations handled: association logic referenced in custom code
• Workflow control: can exit without producing outputs, can fail the action explicitly, contains asynchronous execution
• Safeguards/error handling: explicit error throwing, guard clauses or missing-value checks, structured response handling, try/catch error handling, checks missing values, has catch block, throws errors
• Imports: @hubspot/api-client
• External systems/hosts: none detected
• External call evidence: none detected
• HTTP methods in code: none detected
• Secrets configured: 2
• Code evidence: 384 lines returned; code body analyzed but omitted from docs

Step 57 - Action 82

• What happens: Runs a connected HubSpot workflow action
• What triggers it: After action 81
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: connected_action
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Runs a connected HubSpot workflow action
• Returned action type: SINGLE_CONNECTION
• Returned field keys: delta, time_unit

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 58 - Action 83

• What happens: Branches based on HubSpot list membership; 2 branches
• What triggers it: After action 82
• System condition: 2 branch condition(s) returned by HubSpot.
• What data is used: properties: Lead Name (hs_lead_name), 4f_Lead Source Level 1 (n4f_lead_source_level_1); lists: none detected

DATA MEANING:

• Lead Name (hs_lead_name): The full name of the lead.
• 4f_Lead Source Level 1 (n4f_lead_source_level_1): used for attribution of marketing leads, synchronized with touchpoint types (and deal sources)

ACTION EVIDENCE:

• Action category: list_branch
• Detected intent: Branches based on HubSpot list membership
• Returned action type: LIST_BRANCH

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• Branch: Lead known
  • Condition summary: Lead known
  • Default branch: no
  • Next action IDs: 88
  • Referenced properties: Lead Name (hs_lead_name), 4f_Lead Source Level 1 (n4f_lead_source_level_1)
  • Referenced lists: none detected
  • Filter-like criteria returned: 6
  • Returned branch logic:
    • OR group
      • AND group
        • AND group
          • Lead Name is known
        • AND group
          • 4f_Lead Source Level 1 is any of Event booth meeting
• Branch: Lead unknown
  • Condition summary: Lead unknown
  • Default branch: yes
  • Next action IDs: 85
  • Referenced properties: none detected
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch name: Lead unknown
      • Next action: 85

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 59 - Action 85

• What happens: Runs a connected HubSpot workflow action
• What triggers it: After action 83
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: connected_action
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Runs a connected HubSpot workflow action
• Returned action type: SINGLE_CONNECTION
• Returned field keys: delta, time_unit

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 60 - Action 98

• What happens: Runs custom code; 19 inputs; 0 outputs
• What triggers it: After action 85
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: coreApi, Object create date/time (hs_createdate), join; lists: none detected

DATA MEANING:

• Object create date/time (hs_createdate): The date and time at which this object was created. This value is automatically set by HubSpot and may not be modified.

ACTION EVIDENCE:

• Action category: custom_code
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Runs custom code
• Returned action type: CUSTOM_CODE

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• Inputs used by code: coreApi, download_name, hs_createdate, hs_lead_name, hs_lead_type, hs_pipeline, hs_pipeline_stage, join, n4f_assigned_owner_touchpoint, n4f_booth_protocoll, n4f_business_line, n4f_campaign_owner, n4f_lead_document, n4f_lead_message, n4f_lead_region_country, n4f_lead_source_level_1, n4f_lead_source_level_2, n4f_region_country, n4f_touchpoint_document, n4f_touchpoint_name_dd, n4f_touchpoint_type, name
• Conditions detected in code: Code condition: if (obj !== null) console.log([${ts()}] ${msg} ${safeJSON(obj)}); Code condition: if (!list.includes(id)) list.push(id); Code condition: if (!leadPropCache[propName]) { Code condition: if (!inputValue) return null; Code condition: if (found) return found.value; Code condition: if (found) return found.value; Code condition: if (found) return found.value; Code condition: if (resolved) return resolved; Code condition: if (fallback) return await resolveDropdownValue(client, propName, fallback); Code condition: if (!tpId) return callback({ ok: true }); Code condition: if (!contactId) throw new Error(“No associated Contact found for TP.”); Code condition: if (!leadIds.length) return callback({ ok: true });
• CRM/API operations detected: creates records or resources, creates, removes, or checks associations, updates records or resources
• Concrete CRM operations: associate: associations, objects, properties; create: associations, objects, properties; read by ID: associations, objects, properties; update: associations, objects, properties
• Search/filter evidence: none detected
• Data transformations: calculates or formats dates, combines multiple values, converts values to numbers, filters collections, maps collections into derived values, normalizes text to lowercase, removes surrounding whitespace, replaces or cleans text patterns, serializes data as JSON, splits a value into parts
• Outputs returned to workflow: none detected
• HubSpot CRM objects affected or referenced: associations, objects, properties
• Associations handled: association logic referenced in custom code
• Workflow control: can exit without producing outputs, can fail the action explicitly, contains asynchronous execution
• Safeguards/error handling: explicit error throwing, guard clauses or missing-value checks, structured response handling, try/catch error handling, checks missing values, has catch block, throws errors
• Imports: @hubspot/api-client
• External systems/hosts: none detected
• External call evidence: none detected
• HTTP methods in code: none detected
• Secrets configured: 2
• Code evidence: 384 lines returned; code body analyzed but omitted from docs

Step 61 - Action 86

• What happens: Branches based on HubSpot list membership; 2 branches
• What triggers it: After action 98
• System condition: 2 branch condition(s) returned by HubSpot.
• What data is used: properties: Lead Name (hs_lead_name); lists: none detected

DATA MEANING:

• Lead Name (hs_lead_name): The full name of the lead.

ACTION EVIDENCE:

• Action category: list_branch
• Detected intent: Branches based on HubSpot list membership
• Returned action type: LIST_BRANCH

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• Branch: Lead known
  • Condition summary: Lead known
  • Default branch: no
  • Next action IDs: 93
  • Referenced properties: Lead Name (hs_lead_name)
  • Referenced lists: none detected
  • Filter-like criteria returned: 3
  • Returned branch logic:
    • OR group
      • AND group
        • AND group
          • Lead Name is known
• Branch: Lead unknown
  • Condition summary: Lead unknown
  • Default branch: yes
  • Next action IDs: 84
  • Referenced properties: none detected
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch name: Lead unknown
      • Next action: 84

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 62 - Action 84

• What happens: Sends an internal notification
• What triggers it: After action 86
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: internal_notification
• Detected intent: Sends an internal notification
• Returned action type: SINGLE_CONNECTION
• Returned field keys: body, subject, team_ids
• subject: ALARM- Lead association & relabeling failed for existing pre-scheduled meeting lead
• team_ids: Demand-Gen & CRM

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 63 - Action 93

• What happens: Sends an internal notification
• What triggers it: After action 86
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: internal_notification
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Sends an internal notification
• Returned action type: SINGLE_CONNECTION
• Returned field keys: body, subject, team_ids
• subject: Pre-scheduled meeting lead updated to Event booth
• team_ids: Demand-Gen & CRM

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 64 - Action 89

• What happens: Sets HubSpot property values; properties: n4f_conversion_source = static value Yes
• What triggers it: After action 93
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: 4f_Conversion source (n4f_conversion_source); lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: set_property
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Sets HubSpot property values
• Returned action type: SINGLE_CONNECTION
• Returned field keys: property_name, value
• property_name: n4f_conversion_source
• value: static value Yes

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• 4f_Conversion source (n4f_conversion_source) is set or updated; value: static value Yes; confidence: high.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 65 - Action 90

• What happens: Branches based on HubSpot list membership; 1 branches
• What triggers it: After action 89
• System condition: 1 branch condition(s) returned by HubSpot.
• What data is used: properties: Lifecycle Stage (lifecyclestage); lists: none detected

DATA MEANING:

• Lifecycle Stage (lifecyclestage): The qualification of companies to sales readiness throughout the buying journey

ACTION EVIDENCE:

• Action category: list_branch
• Detected intent: Branches based on HubSpot list membership
• Returned action type: LIST_BRANCH

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• Branch: lifecycle below MQL
  • Condition summary: lifecycle below MQL
  • Default branch: no
  • Next action IDs: 91
  • Referenced properties: Lifecycle Stage (lifecyclestage)
  • Referenced lists: none detected
  • Filter-like criteria returned: 3
  • Returned branch logic:
    • OR group
      • AND group
        • AND group
          • Lifecycle Stage is any of Subscriber, New, Lead

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 66 - Action 91

• What happens: Sets HubSpot property values; properties: lifecyclestage = static value Marketing Qualified Lead
• What triggers it: After action 90
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: Lifecycle Stage (lifecyclestage); lists: none detected

DATA MEANING:

• Lifecycle Stage (lifecyclestage): The qualification of companies to sales readiness throughout the buying journey

ACTION EVIDENCE:

• Action category: set_property
• Detected intent: Sets HubSpot property values
• Returned action type: SINGLE_CONNECTION
• Returned field keys: association, property_name, value
• property_name: lifecyclestage
• value: static value Marketing Qualified Lead

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• Lifecycle Stage (lifecyclestage) is set or updated; value: static value Marketing Qualified Lead; confidence: high. Purpose: The qualification of companies to sales readiness throughout the buying journey

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 67 - Action 88

• What happens: Sends an internal notification
• What triggers it: After action 83
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: internal_notification
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Sends an internal notification
• Returned action type: SINGLE_CONNECTION
• Returned field keys: body, subject, team_ids
• subject: Pre-scheduled meeting lead updated to Event booth
• team_ids: Demand-Gen & CRM

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 68 - Action 8

• What happens: Branches based on HubSpot list membership; 2 branches
• What triggers it: After action 2
• System condition: 2 branch condition(s) returned by HubSpot.
• What data is used: properties: Lifecycle Stage (lifecyclestage); lists: none detected

DATA MEANING:

• Lifecycle Stage (lifecyclestage): The qualification of companies to sales readiness throughout the buying journey

ACTION EVIDENCE:

• Action category: list_branch
• Detected intent: Branches based on HubSpot list membership
• Returned action type: LIST_BRANCH

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• Branch: lifecycle stage low
  • Condition summary: lifecycle stage low
  • Default branch: no
  • Next action IDs: 9
  • Referenced properties: Lifecycle Stage (lifecyclestage)
  • Referenced lists: none detected
  • Filter-like criteria returned: 3
  • Returned branch logic:
    • OR group
      • AND group
        • AND group
          • Lifecycle Stage is none of Evangelist, Sales Accepted Lead, Opportunity, Sales Qualified Lead, Customer
• Branch: lifecycle stage high
  • Condition summary: lifecycle stage high
  • Default branch: yes
  • Next action IDs: 7
  • Referenced properties: none detected
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch name: lifecycle stage high
      • Next action: 7

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 69 - Action 7

• What happens: Runs custom code; 22 inputs; 0 outputs
• What triggers it: After action 8
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: custom_code
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Runs custom code
• Returned action type: CUSTOM_CODE

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• Inputs used by code: company, download_name, hs_lead_name, hs_lead_type, hs_pipeline, hs_pipeline_stage, n4f_assigned_owner_touchpoint, n4f_booth_protocoll, n4f_business_line, n4f_campaign_owner, n4f_date_of_conversion, n4f_event_quality_of_contact, n4f_last_marketing_touchpoint_date, n4f_lead_message, n4f_lead_region_country, n4f_lead_source_level_1, n4f_lead_source_level_2, n4f_priority_label, n4f_region_country, n4f_touchpoint_name_dd, n4f_touchpoint_type, name
• Conditions detected in code: Code condition: if (!tpId) return callback({ ok: true }); Code condition: if (existingLeadId) { Code condition: if (!contactId) throw new Error(“No Contact associated.”); Code condition: if (companyId) { Code condition: if (tpAssignedOwner && /^\d+$/.test(tpAssignedOwner)) { Code condition: if (tpType) { Code condition: if (tpNameDD) { Code condition: if (tpBoothMsg) { Code condition: if (tpCampOwner) { Code condition: if (String(tpEventQuality).toLowerCase().trim() === “sales potential”) { Code condition: if (tpConversionDate) { Code condition: if (tpBusinessLine) {
• CRM/API operations detected: creates records or resources, creates, removes, or checks associations
• Concrete CRM operations: associate: associations, objects; create: associations, objects; read by ID: associations, objects
• Search/filter evidence: none detected
• Data transformations: calculates or formats dates, combines multiple values, filters collections, maps collections into derived values, normalizes text to lowercase, removes surrounding whitespace, splits a value into parts
• Outputs returned to workflow: none detected
• HubSpot CRM objects affected or referenced: associations, objects
• Associations handled: association logic referenced in custom code
• Workflow control: can fail the action explicitly, contains asynchronous execution
• Safeguards/error handling: error or warning logging, explicit error throwing, guard clauses or missing-value checks, structured response handling, try/catch error handling, checks missing values, has catch block, logs errors, mentions retry or rate-limit handling, throws errors
• Imports: @hubspot/api-client
• External systems/hosts: none detected
• External call evidence: none detected
• HTTP methods in code: none detected
• Secrets configured: 2
• Code evidence: 296 lines returned; code body analyzed but omitted from docs

Step 70 - Action 20

• What happens: Runs a connected HubSpot workflow action
• What triggers it: After action 7
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: connected_action
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Runs a connected HubSpot workflow action
• Returned action type: SINGLE_CONNECTION
• Returned field keys: delta, time_unit

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 71 - Action 21

• What happens: Branches based on HubSpot list membership; 2 branches
• What triggers it: After action 20
• System condition: 2 branch condition(s) returned by HubSpot.
• What data is used: properties: Lead Name (hs_lead_name); lists: none detected

DATA MEANING:

• Lead Name (hs_lead_name): The full name of the lead.

ACTION EVIDENCE:

• Action category: list_branch
• Detected intent: Branches based on HubSpot list membership
• Returned action type: LIST_BRANCH

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• Branch: Lead known
  • Condition summary: Lead known
  • Default branch: no
  • Next action IDs: 48
  • Referenced properties: Lead Name (hs_lead_name)
  • Referenced lists: none detected
  • Filter-like criteria returned: 3
  • Returned branch logic:
    • OR group
      • AND group
        • AND group
          • Lead Name is known
• Branch: Lead unknown
  • Condition summary: Lead unknown
  • Default branch: yes
  • Next action IDs: 22
  • Referenced properties: none detected
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch name: Lead unknown
      • Next action: 22

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 72 - Action 22

• What happens: Runs a connected HubSpot workflow action
• What triggers it: After action 21
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: connected_action
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Runs a connected HubSpot workflow action
• Returned action type: SINGLE_CONNECTION
• Returned field keys: delta, time_unit

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 73 - Action 95

• What happens: Runs custom code; 22 inputs; 0 outputs
• What triggers it: After action 22
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: custom_code
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Runs custom code
• Returned action type: CUSTOM_CODE

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• Inputs used by code: company, download_name, hs_lead_name, hs_lead_type, hs_pipeline, hs_pipeline_stage, n4f_assigned_owner_touchpoint, n4f_booth_protocoll, n4f_business_line, n4f_campaign_owner, n4f_date_of_conversion, n4f_event_quality_of_contact, n4f_last_marketing_touchpoint_date, n4f_lead_message, n4f_lead_region_country, n4f_lead_source_level_1, n4f_lead_source_level_2, n4f_priority_label, n4f_region_country, n4f_touchpoint_name_dd, n4f_touchpoint_type, name
• Conditions detected in code: Code condition: if (!tpId) return callback({ ok: true }); Code condition: if (existingLeadId) { Code condition: if (!contactId) throw new Error(“No Contact associated.”); Code condition: if (companyId) { Code condition: if (tpAssignedOwner && /^\d+$/.test(tpAssignedOwner)) { Code condition: if (tpType) { Code condition: if (tpNameDD) { Code condition: if (tpBoothMsg) { Code condition: if (tpCampOwner) { Code condition: if (String(tpEventQuality).toLowerCase().trim() === “sales potential”) { Code condition: if (tpConversionDate) { Code condition: if (tpBusinessLine) {
• CRM/API operations detected: creates records or resources, creates, removes, or checks associations
• Concrete CRM operations: associate: associations, objects; create: associations, objects; read by ID: associations, objects
• Search/filter evidence: none detected
• Data transformations: calculates or formats dates, combines multiple values, filters collections, maps collections into derived values, normalizes text to lowercase, removes surrounding whitespace, splits a value into parts
• Outputs returned to workflow: none detected
• HubSpot CRM objects affected or referenced: associations, objects
• Associations handled: association logic referenced in custom code
• Workflow control: can fail the action explicitly, contains asynchronous execution
• Safeguards/error handling: error or warning logging, explicit error throwing, guard clauses or missing-value checks, structured response handling, try/catch error handling, checks missing values, has catch block, logs errors, mentions retry or rate-limit handling, throws errors
• Imports: @hubspot/api-client
• External systems/hosts: none detected
• External call evidence: none detected
• HTTP methods in code: none detected
• Secrets configured: 2
• Code evidence: 296 lines returned; code body analyzed but omitted from docs

Step 74 - Action 24

• What happens: Runs a connected HubSpot workflow action
• What triggers it: After action 95
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: connected_action
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Runs a connected HubSpot workflow action
• Returned action type: SINGLE_CONNECTION
• Returned field keys: delta, time_unit

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 75 - Action 25

• What happens: Branches based on HubSpot list membership; 2 branches
• What triggers it: After action 24
• System condition: 2 branch condition(s) returned by HubSpot.
• What data is used: properties: Lead Name (hs_lead_name); lists: none detected

DATA MEANING:

• Lead Name (hs_lead_name): The full name of the lead.

ACTION EVIDENCE:

• Action category: list_branch
• Detected intent: Branches based on HubSpot list membership
• Returned action type: LIST_BRANCH

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• Branch: Lead known
  • Condition summary: Lead known
  • Default branch: no
  • Next action IDs: 49
  • Referenced properties: Lead Name (hs_lead_name)
  • Referenced lists: none detected
  • Filter-like criteria returned: 3
  • Returned branch logic:
    • OR group
      • AND group
        • AND group
          • Lead Name is known
• Branch: Lead unknown
  • Condition summary: Lead unknown
  • Default branch: yes
  • Next action IDs: 26
  • Referenced properties: none detected
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch name: Lead unknown
      • Next action: 26

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 76 - Action 26

• What happens: Sends an internal notification
• What triggers it: After action 25
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: internal_notification
• Detected intent: Sends an internal notification
• Returned action type: SINGLE_CONNECTION
• Returned field keys: body, subject, team_ids
• subject: ALARM- Lead creation failed - New business branch
• team_ids: Demand-Gen & CRM

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 77 - Action 49

• What happens: Sends an internal notification
• What triggers it: After action 25
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: internal_notification
• Detected intent: Sends an internal notification
• Returned action type: SINGLE_CONNECTION
• Returned field keys: body, subject, team_ids
• subject: New business lead created
• team_ids: Demand-Gen & CRM

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 78 - Action 48

• What happens: Sends an internal notification
• What triggers it: After action 21
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: none detected

DATA MEANING:

• No property descriptions returned for the properties in this step.

ACTION EVIDENCE:

• Action category: internal_notification
• Detected intent: Sends an internal notification
• Returned action type: SINGLE_CONNECTION
• Returned field keys: body, subject, team_ids
• subject: New business lead created
• team_ids: Demand-Gen & CRM

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 79 - Action 9

• What happens: Sets HubSpot property values; properties: lifecyclestage = static value Marketing Qualified Lead
• What triggers it: After action 8
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: Lifecycle Stage (lifecyclestage); lists: none detected

DATA MEANING:

• Lifecycle Stage (lifecyclestage): The qualification of companies to sales readiness throughout the buying journey

ACTION EVIDENCE:

• Action category: set_property
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Sets HubSpot property values
• Returned action type: SINGLE_CONNECTION
• Returned field keys: association, property_name, value
• property_name: lifecyclestage
• value: static value Marketing Qualified Lead

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• No list logic detected in this step.

PROPERTY MAPPINGS:

• Lifecycle Stage (lifecyclestage) is set or updated; value: static value Marketing Qualified Lead; confidence: high. Purpose: The qualification of companies to sales readiness throughout the buying journey

CUSTOM CODE LOGIC:

• No custom code detected in this step.

System Behavior

• Workflow actions: 79
• Branch actions: 24
• Custom code actions: 11
• Property operations: 9
• List dependencies: 8
• Action categories: ab_test_branch: 1, connected_action: 17, custom_code: 11, internal_notification: 18, list_branch: 23, set_property: 9
• Property operation types: set_property: 9
• Associations created: listed under Outcomes when custom code exposes association evidence.

Outcomes

• Objects created: associations (custom code contains create call), objects (custom code contains create call), properties (custom code contains create call)
• Objects updated: Touchpoint: 9 property operation(s), associations (custom code contains update call), objects (custom code contains update call), properties (custom code contains update call)
• Associations created: association logic referenced in custom code, association logic referenced in custom code, association logic referenced in custom code, association logic referenced in custom code, association logic referenced in custom code, association logic referenced in custom code, association logic referenced in custom code, association logic referenced in custom code, association logic referenced in custom code, association logic referenced in custom code, association logic referenced in custom code
• Marketing emails sent: 0
• Internal notifications: 18
• Sequence enrollments: 0
• Subscription updates: 0
• Webhooks: 0
• Custom code actions: 11

How It Is Implemented

Workflows

• Workflow: NEW_ELEVATE - Events - Lead creation & lifecycle stage based on marketing touchpoints w/o company req
  • Workflow ID: 3166912739
  • Revision ID: 120
  • Enabled: yes
  • Current HubSpot description: Updates or creates leads based on touchpoint marketing events by associating contacts and companies, syncing campaign owners, and adjusting lead lifecycle stages accordingly.
  • Purpose: Updates or creates leads based on touchpoint marketing events by associating contacts and companies, syncing campaign owners, and adjusting lead lifecycle stages accordingly.
  • Key logic: ab_test_branch: 1, connected_action: 17, custom_code: 11, internal_notification: 18, list_branch: 23, set_property: 9
  • Branching logic: 46 branch detail(s) returned by HubSpot
  • already active - Lead: already active - Lead; next actions: 66; properties: none detected; lists: 11378
  • reopen - Lead: reopen - Lead; next actions: 10; properties: none detected; lists: 17863
  • reattempting lead: reattempting lead; next actions: 10; properties: hs_lead_disqualification_reason; lists: 11391, 11421, 11428, 11434
  • new business lead: new business lead; next actions: 8; properties: none detected; lists: 11391, 11434
  • could not decide: could not decide; next actions: 101; properties: none detected; lists: none detected
  • lifecycle stage low: lifecycle stage low; next actions: 9; properties: lifecyclestage; lists: none detected
  • lifecycle stage high: lifecycle stage high; next actions: 7; properties: none detected; lists: none detected
  • lifecycle stage low: lifecycle stage low; next actions: 11; properties: lifecyclestage; lists: none detected
  • lifecycle stage high: lifecycle stage high; next actions: 12; properties: none detected; lists: none detected
  • Lead known : Lead known ; next actions: 51; properties: hs_lead_name; lists: none detected
  • Lead unknown : Lead unknown ; next actions: 19; properties: none detected; lists: none detected
  • Lead known : Lead known ; next actions: 50; properties: hs_lead_name; lists: none detected
  • Dependencies: lists: ELEVATE - Stop criteria existing active lead (11378), ELEVATE - Stop criteria - Lead creation (11391), ELEVATE - Lead supression - diqualification criteria permanent (11421), ELEVATE - Lead supression - disqualification criteria temporary (11428), ELEVATE - Contacts with lost deals (11434), ELEVATE-Contacts with open outbound leads (16614), ELEVATE-Contacts with open pre-scheduled meeting leads (16616), ELEVATE - Contacts with ghosting leads (17863); properties: 4f_Touchpoint-name (download_name), Disqualification Reason (hs_lead_disqualification_reason), Lead Name (hs_lead_name), Lifecycle Stage (lifecyclestage), 4f_assigned owner_touchpoint (n4f_assigned_owner_touchpoint), 4f_Message (n4f_booth_protocoll), 4f_Business line (n4f_business_line), 4f_Conversion source (n4f_conversion_source), 4f_Date of conversion (n4f_date_of_conversion), 4f_event_Quality of contact (n4f_event_quality_of_contact), 4f_Lead Source Level 1 (n4f_lead_source_level_1), 4f_touchpoint_document (n4f_touchpoint_document), 4f_Touchpoint name_dd (n4f_touchpoint_name_dd), 4f_Touchpoint type (n4f_touchpoint_type); custom code: 11 custom code action(s)

Property Context

• coreApi - No HubSpot property description returned. Roles: step data. internal name: coreApi; object: object not returned; type: not returned.
• 4f_Touchpoint-name (download_name) - Standard single-line text field with name of touchpoint. Is always overwritten by _dd variant. Roles: reference. internal name: download_name; object: Touchpoints; type: string.
• Object create date/time (hs_createdate) - The date and time at which this object was created. This value is automatically set by HubSpot and may not be modified. Roles: step data. internal name: hs_createdate; object: Line Items; type: datetime.
• Disqualification Reason (hs_lead_disqualification_reason) - Dropdown list of reasons for disqualification Roles: branch condition, step data. internal name: hs_lead_disqualification_reason; object: Leads; type: enumeration.
• Lead Name (hs_lead_name) - The full name of the lead. Roles: branch condition, step data. internal name: hs_lead_name; object: Leads; type: string.
• Lead stage (hs_pipeline_stage) - shows the pipeline stages of the lead pipeline. indicates which stage the lead is in Roles: step data. internal name: hs_pipeline_stage; object: Leads; type: enumeration.
• Owner (hubspot_owner_id) - The owner of the object. Roles: step data. internal name: hubspot_owner_id; object: Line Items; type: enumeration.
• join - No HubSpot property description returned. Roles: step data. internal name: join; object: object not returned; type: not returned.
• Lifecycle Stage (lifecyclestage) - The qualification of companies to sales readiness throughout the buying journey Roles: branch condition, property updated, step data. internal name: lifecyclestage; object: Companies; type: enumeration.
• 4f_assigned owner_touchpoint (n4f_assigned_owner_touchpoint) - No HubSpot property description returned. Roles: reference. internal name: n4f_assigned_owner_touchpoint; object: Touchpoints; type: enumeration.
• 4f_Message (n4f_booth_protocoll) - No HubSpot property description returned. Roles: reference. internal name: n4f_booth_protocoll; object: Touchpoints; type: string.
• 4f_Business line (n4f_business_line) - This property reflects the 4flow business lines and is used whenever a clear association with one of our business lines/services is possible. Also used at events in booth protocols, etc. Roles: step data. internal name: n4f_business_line; object: Touchpoints; type: enumeration.
• 4f_campaign owner (n4f_campaign_owner) - Depreciated property was used to identify internal campaign stakeholders (business line representatives who requested/are responsible for a campaign). Roles: step data. internal name: n4f_campaign_owner; object: Touchpoints; type: enumeration.
• 4f_Conversion source (n4f_conversion_source) - No HubSpot property description returned. Roles: property updated, step data. internal name: n4f_conversion_source; object: Touchpoints; type: enumeration.
• 4f_Date of conversion (n4f_date_of_conversion) - This property is used instead of the create date. It is especially relevant when we are adding older conversions to the system, e.g., from an Excel sheet. It represents the actual date of conversion, not the create date of the touchpoint. Roles: reference. internal name: n4f_date_of_conversion; object: Touchpoints; type: date.
• 4f_event_Quality of contact (n4f_event_quality_of_contact) - This property is used as the selector for event booth staff. By selecting the right measures, we determine if a conversion (of the contact) is an MQL and create a lead. Roles: branch condition, step data. internal name: n4f_event_quality_of_contact; object: Touchpoints; type: enumeration.
• 4f_Lead interest (n4f_lead__interest) - collects all 4Flowers who e.g. were former owners or assigned other owners - for tracking purposes Roles: step data. internal name: n4f_lead__interest; object: Leads; type: enumeration.
• 4f_Lead Source Level 1 (n4f_lead_source_level_1) - used for attribution of marketing leads, synchronized with touchpoint types (and deal sources) Roles: branch condition, step data. internal name: n4f_lead_source_level_1; object: Leads; type: enumeration.
• 4f_touchpoint_document (n4f_touchpoint_document) - document field, used if an attachment is stored - e.g. in inbound message. advantage: document is tied to the touchpoint (unique) and not overwritten like the document field on contact level Roles: reference. internal name: n4f_touchpoint_document; object: Touchpoints; type: string.
• 4f_Touchpoint name_dd (n4f_touchpoint_name_dd) - 4flow specific dropdown select of touchpoint names such as webinar names, content pieces, event names, etc. It replaces the free text field and makes sure touchpoints can be selected easily and naming is consistent. Used in filters, in reports, etc. It also overwrites the standard touchpoint name field to make sure … Roles: reference. internal name: n4f_touchpoint_name_dd; object: Touchpoints; type: enumeration.
• 4f_Touchpoint type (n4f_touchpoint_type) - 4flow specific dropdown select of touchpoint types. Works in conjunction with 4f_Touchpoint name_dd and 4f_activity type. Roles: branch condition, step data. internal name: n4f_touchpoint_type; object: Touchpoints; type: enumeration.

Evidence And Gaps

• Domain evidence: Derived from workflow name term: event
• Quality flags: complex_workflow: Workflow contains many actions and should be reviewed as a process map. custom_code_present: Workflow appears to contain one or more custom code actions. branching_logic_present: Workflow contains branching logic. property_operations_detected: Workflow appears to write or copy one or more properties.
• Narrative context: not used as source of truth.