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

ELEVATE - Categorize new business vs. existing business

METADATA title: ELEVATE - Categorize new business vs. existing business type: process domain: ELEVATE objects: [Deal] 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: EVENT_BASED
• Criteria type: EVENT_BASED
• Filter-like criteria returned: 12
• Property references: hs_name, hs_value, Pipeline (pipeline)
• List references: none detected
• Filter types: PROPERTY: 5
• Operators: BOOL: 2, ENUMERATION: 1, HAS_COMPLETED: 2, IS_ANY_OF: 1, IS_EQUAL_TO: 4, STRING: 2
• Trigger logic:
  • Enrollment criteria type: EVENT_BASED
  • Enrollment branch 1:
    • AND group
      • hs_name equals hs_is_closed_won
      • hs_value equals true
  • Enrollment branch 2:
    • AND group
      • hs_name equals hs_is_closed_lost
      • hs_value equals true
  • Enrollment branch 3:
    • OR group
      • AND group
        • Pipeline is any of Sales Pipeline New
  • Enrollment branch 4:
    • AND group
      • Pipeline is any of Sales Pipeline New
• Trigger property meaning:
  • Pipeline (pipeline): The pipeline the deal is in. This determines which stages are options for the deal.

Steps

Step 1 - Action 3

• What happens: Runs custom code; 2 inputs; 1 outputs
• What triggers it: Workflow start action returned by HubSpot
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: Close Date (closedate), 4f_deal_cutoff_date_new (n4f_deal_cutoff_date_new); lists: none detected

DATA MEANING:

• Close Date (closedate): Date the deal was closed. This property is set automatically by HubSpot.
• 4f_deal_cutoff_date_new (n4f_deal_cutoff_date_new): used to define new business vs existing business. Cutoff date is calculated based on start date, duration, end date + define cadence

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: closedate, n4f_deal_cutoff_date_new

• Conditions detected in code: Code condition: if (!Private_App_token) { Code condition: if (!closeDateMillis

  !dealId) {

• CRM/API operations detected: updates records or resources, writes properties: n4f_deal_cutoff_date_new
• Concrete CRM operations: none detected
• Search/filter evidence: none detected
• Data transformations: calculates or formats dates, converts values to numbers, serializes data as JSON, splits a value into parts
• Outputs returned to workflow: deal_cutoff_date, n4f_deal_cutoff_date_new, outputFields
• HubSpot CRM objects affected or referenced: deals
• Associations handled: none detected
• Workflow control: none detected
• Safeguards/error handling: error or warning logging, guard clauses or missing-value checks, structured response handling, checks missing values, logs errors
• Imports: https
• External systems/hosts: none detected
• External call evidence: HTTP client usage detected
• HTTP methods in code: PATCH
• Secrets configured: 3
• Code evidence: 70 lines returned; code body analyzed but omitted from docs

Step 2 - Action 6

• What happens: Runs a connected HubSpot workflow action
• What triggers it: After action 3
• 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 3 - Action 14

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

DATA MEANING:

• 4f_deal_cutoff_date_new (n4f_deal_cutoff_date_new): used to define new business vs existing business. Cutoff date is calculated based on start date, duration, end date + define cadence

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: cutoff date known
  • Condition summary: cutoff date known
  • Default branch: no
  • Next action IDs: 5
  • Referenced properties: 4f_deal_cutoff_date_new (n4f_deal_cutoff_date_new)
  • Referenced lists: none detected
  • Filter-like criteria returned: 2
  • Returned branch logic:
    • OR group
      • AND group
        • 4f_deal_cutoff_date_new is known
• Branch: unknown
  • Condition summary: unknown
  • Default branch: yes
  • Next action IDs: 15
  • Referenced properties: none detected
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch name: unknown
      • Next action: 15

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 15

• What happens: Runs custom code; 2 inputs; 1 outputs
• What triggers it: After action 14
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: Close Date (closedate), 4f_deal_cutoff_date_new (n4f_deal_cutoff_date_new); lists: none detected

DATA MEANING:

• Close Date (closedate): Date the deal was closed. This property is set automatically by HubSpot.
• 4f_deal_cutoff_date_new (n4f_deal_cutoff_date_new): used to define new business vs existing business. Cutoff date is calculated based on start date, duration, end date + define cadence

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: closedate, n4f_deal_cutoff_date_new

• Conditions detected in code: Code condition: if (!Private_App_token) { Code condition: if (!closeDateMillis

  !dealId) {

• CRM/API operations detected: updates records or resources, writes properties: n4f_deal_cutoff_date_new
• Concrete CRM operations: none detected
• Search/filter evidence: none detected
• Data transformations: calculates or formats dates, converts values to numbers, serializes data as JSON, splits a value into parts
• Outputs returned to workflow: deal_cutoff_date, n4f_deal_cutoff_date_new, outputFields
• HubSpot CRM objects affected or referenced: deals
• Associations handled: none detected
• Workflow control: none detected
• Safeguards/error handling: error or warning logging, guard clauses or missing-value checks, structured response handling, checks missing values, logs errors
• Imports: https
• External systems/hosts: none detected
• External call evidence: HTTP client usage detected
• HTTP methods in code: PATCH
• Secrets configured: 3
• Code evidence: 70 lines returned; code body analyzed but omitted from docs

Step 5 - Action 16

• What happens: Runs a connected HubSpot workflow action
• What triggers it: After action 15
• 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 18

• 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: 4f_deal_cutoff_date_new (n4f_deal_cutoff_date_new); lists: none detected

DATA MEANING:

• 4f_deal_cutoff_date_new (n4f_deal_cutoff_date_new): used to define new business vs existing business. Cutoff date is calculated based on start date, duration, end date + define cadence

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: cutoff date known
  • Condition summary: cutoff date known
  • Default branch: no
  • Next action IDs: 5
  • Referenced properties: 4f_deal_cutoff_date_new (n4f_deal_cutoff_date_new)
  • Referenced lists: none detected
  • Filter-like criteria returned: 2
  • Returned branch logic:
    • OR group
      • AND group
        • 4f_deal_cutoff_date_new is known
• Branch: unknown
  • Condition summary: 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: 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 7 - Action 19

• What happens: Sends an internal notification
• What triggers it: After action 18
• 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: Alaaarm, cutoff date for “New business or existing business” not set
• 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 8 - Action 5

• What happens: Runs custom code; 6 inputs; 1 outputs
• What triggers it: After action 18
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: Business Line (business_line), Close Date (closedate), Deal Type (dealtype), Is Closed Won (hs_is_closed_won), 4f_associated company ID (n4f_associated_company_id), 4f_Expected project end date (n4f_expected_project_end_date); lists: none detected

DATA MEANING:

• Business Line (business_line): 4flow definition of business line
• Close Date (closedate): Date the deal was closed. This property is set automatically by HubSpot.
• Deal Type (dealtype): The type of deal. By default, categorize your deal as either a New Business or Existing Business.
• Is Closed Won (hs_is_closed_won): True if the deal is in the closed won state, false otherwise
• 4f_associated company ID (n4f_associated_company_id): stores the ID of the associated Company
• 4f_Expected project end date (n4f_expected_project_end_date): calculated property based on Start Date and Duration in Months

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: business_line, closedate, dealtype, hs_is_closed_won, n4f_associated_company_id, n4f_deal_cutoff_date_new, n4f_expected_project_end_date

• Conditions detected in code: Code condition: if (!token) { Code condition: if (!dealId

  !closeDateMillis

  !companyId

  !businessLine) { Code condition: if (!value) return null; Code condition: if (!isNaN(value)) { Code condition: if (typeof value === ‘string’ && value.includes(‘.’)) { Code condition: if (parts.length === 3) { Code condition: if (!isValidDate(closeDate)) { Code condition: if (!isValidDate(cutoffDate)) { Code condition: if (deal.id === dealId) { Code condition: if (!isWon

  dealBL !== businessLine) continue; Code condition: if (closeMatch

  endMatch) { Code condition: if (data) req.write(data);

• CRM/API operations detected: creates records or resources, creates, removes, or checks associations, searches records, updates records or resources, writes properties: dealtype
• Concrete CRM operations: associate: deals; search: deals
• Search/filter evidence: search/filter operator: EQ; search/filter property: associations.company
• Data transformations: calculates or formats dates, converts values to numbers, parses JSON input, serializes data as JSON, splits a value into parts
• Outputs returned to workflow: ID, Line, deal_cutoff_date, dealtype, filterGroups, filters, limit, operator, outputFields, propertyName, value
• HubSpot CRM objects affected or referenced: deals
• Associations handled: association logic referenced in custom code
• Workflow control: can exit without producing outputs, contains asynchronous execution
• Safeguards/error handling: error or warning logging, guard clauses or missing-value checks, structured response handling, checks missing values, logs errors
• Imports: https
• External systems/hosts: none detected
• External call evidence: HTTP client usage detected
• HTTP methods in code: PATCH, POST
• Secrets configured: 3
• Code evidence: 232 lines returned; code body analyzed but omitted from docs

Step 9 - Action 22

• What happens: Runs a connected HubSpot workflow action
• What triggers it: After action 5
• 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 10 - Action 7

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

DATA MEANING:

• Deal Type (dealtype): The type of deal. By default, categorize your deal as either a New Business or Existing Business.

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: known
  • Condition summary: known
  • Default branch: no
  • Next action IDs: 11
  • Referenced properties: Deal Type (dealtype)
  • Referenced lists: none detected
  • Filter-like criteria returned: 2
  • Returned branch logic:
    • OR group
      • AND group
        • Deal Type is known
• Branch: not existing
  • Condition summary: not existing
  • Default branch: yes
  • Next action IDs: 21
  • Referenced properties: none detected
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch name: not existing
      • Next action: 21

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 11

• What happens: Branches based on HubSpot list membership; 3 branches
• What triggers it: After action 7
• System condition: 3 branch condition(s) returned by HubSpot.
• What data is used: properties: Deal Type (dealtype); lists: none detected

DATA MEANING:

• Deal Type (dealtype): The type of deal. By default, categorize your deal as either a New Business or Existing Business.

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: existing
  • Condition summary: existing
  • Default branch: no
  • Next action IDs: 10
  • Referenced properties: Deal Type (dealtype)
  • Referenced lists: none detected
  • Filter-like criteria returned: 2
  • Returned branch logic:
    • OR group
      • AND group
        • Deal Type is any of Existing Business
• Branch: new
  • Condition summary: new
  • Default branch: no
  • Next action IDs: 12
  • Referenced properties: Deal Type (dealtype)
  • Referenced lists: none detected
  • Filter-like criteria returned: 2
  • Returned branch logic:
    • OR group
      • AND group
        • Deal Type is any of New Business
• Branch: empty
  • Condition summary: empty
  • Default branch: yes
  • Next action IDs: 13
  • Referenced properties: none detected
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch name: empty
      • Next action: 13

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 10

• What happens: Sends an internal notification
• What triggers it: After action 11
• 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: Deal was set to “Existing business” based on project end date
• 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 13 - Action 12

• What happens: Sends an internal notification
• What triggers it: After action 11
• 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: Deal was set to “New business”
• 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 14 - Action 13

• What happens: Sends an internal notification
• What triggers it: After action 11
• 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: Alaaarm, deal is still not categorized as “New business or existing business”
• 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 15 - Action 21

• 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 16 - Action 9

• What happens: Runs custom code; 7 inputs; 1 outputs
• What triggers it: After action 21
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: Business Line (business_line), Close Date (closedate), Deal Type (dealtype), Is Closed Won (hs_is_closed_won), 4f_associated company ID (n4f_associated_company_id), 4f_Expected project end date (n4f_expected_project_end_date); lists: none detected

DATA MEANING:

• Business Line (business_line): 4flow definition of business line
• Close Date (closedate): Date the deal was closed. This property is set automatically by HubSpot.
• Deal Type (dealtype): The type of deal. By default, categorize your deal as either a New Business or Existing Business.
• Is Closed Won (hs_is_closed_won): True if the deal is in the closed won state, false otherwise
• 4f_associated company ID (n4f_associated_company_id): stores the ID of the associated Company
• 4f_Expected project end date (n4f_expected_project_end_date): calculated property based on Start Date and Duration in Months

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: business_line, closedate, dealtype, hs_is_closed_won, n4f_associated_company_id, n4f_deal_cutoff_date_new, n4f_expected_project_end_date

• Conditions detected in code: Code condition: if (!token) { Code condition: if (!dealId

  !closeDateMillis

  !companyId

  !businessLine) { Code condition: if (!value) return null; Code condition: if (!isNaN(value)) { Code condition: if (typeof value === ‘string’ && value.includes(‘.’)) { Code condition: if (parts.length === 3) { Code condition: if (!isValidDate(closeDate)) { Code condition: if (!isValidDate(cutoffDate)) { Code condition: if (deal.id === dealId) { Code condition: if (!isWon

  dealBL !== businessLine) continue; Code condition: if (closeMatch

  endMatch) { Code condition: if (data) req.write(data);

• CRM/API operations detected: creates records or resources, creates, removes, or checks associations, searches records, updates records or resources, writes properties: dealtype
• Concrete CRM operations: associate: deals; search: deals
• Search/filter evidence: search/filter operator: EQ; search/filter property: associations.company
• Data transformations: calculates or formats dates, converts values to numbers, parses JSON input, serializes data as JSON, splits a value into parts
• Outputs returned to workflow: ID, Line, deal_cutoff_date, dealtype, filterGroups, filters, limit, operator, outputFields, propertyName, value
• HubSpot CRM objects affected or referenced: deals
• Associations handled: association logic referenced in custom code
• Workflow control: can exit without producing outputs, contains asynchronous execution
• Safeguards/error handling: error or warning logging, guard clauses or missing-value checks, structured response handling, checks missing values, logs errors
• Imports: https
• External systems/hosts: none detected
• External call evidence: HTTP client usage detected
• HTTP methods in code: PATCH, POST
• Secrets configured: 3
• Code evidence: 232 lines returned; code body analyzed but omitted from docs

Step 17 - Action 23

• What happens: Runs a connected HubSpot workflow action
• What triggers it: After action 9
• 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 18 - Action 20

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

DATA MEANING:

• Deal Type (dealtype): The type of deal. By default, categorize your deal as either a New Business or Existing Business.

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: known
  • Condition summary: known
  • Default branch: no
  • Next action IDs: 11
  • Referenced properties: Deal Type (dealtype)
  • Referenced lists: none detected
  • Filter-like criteria returned: 2
  • Returned branch logic:
    • OR group
      • AND group
        • Deal Type is known
• Branch: not existing
  • Condition summary: not existing
  • Default branch: yes
  • Next action IDs: 13
  • Referenced properties: none detected
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch name: not existing
      • Next action: 13

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.

System Behavior

• Workflow actions: 18
• Branch actions: 5
• Custom code actions: 4
• Property operations: 0
• List dependencies: 0
• Action categories: connected_action: 5, custom_code: 4, internal_notification: 4, list_branch: 5
• Property operation types: Logic not derivable from system.
• Associations created: listed under Outcomes when custom code exposes association evidence.

Outcomes

• Objects created: deals (custom code contains create call)
• Objects updated: deals (custom code contains update call)
• Associations created: association logic referenced in custom code, association logic referenced in custom code
• Marketing emails sent: 0
• Internal notifications: 4
• Sequence enrollments: 0
• Subscription updates: 0
• Webhooks: 0
• Custom code actions: 4

How It Is Implemented

Workflows

• Workflow: ELEVATE - Categorize new business vs. existing business
  • Workflow ID: 2422672605
  • Revision ID: 95
  • Enabled: yes
  • Current HubSpot description: No workflow description returned.
  • Purpose: Logic not derivable from system.
  • Key logic: connected_action: 5, custom_code: 4, internal_notification: 4, list_branch: 5
  • Branching logic: 11 branch detail(s) returned by HubSpot
  • known: known; next actions: 11; properties: dealtype; lists: none detected
  • not existing: not existing; next actions: 21; properties: none detected; lists: none detected
  • existing: existing; next actions: 10; properties: dealtype; lists: none detected
  • new: new; next actions: 12; properties: dealtype; lists: none detected
  • empty: empty; next actions: 13; properties: none detected; lists: none detected
  • cutoff date known: cutoff date known; next actions: 5; properties: n4f_deal_cutoff_date_new; lists: none detected
  • unknown: unknown; next actions: 15; properties: none detected; lists: none detected
  • cutoff date known: cutoff date known; next actions: 5; properties: n4f_deal_cutoff_date_new; lists: none detected
  • unknown: unknown; next actions: 19; properties: none detected; lists: none detected
  • known: known; next actions: 11; properties: dealtype; lists: none detected
  • not existing: not existing; next actions: 13; properties: none detected; lists: none detected
  • Dependencies: lists: none detected; properties: Business Line (business_line), Close Date (closedate), Deal Type (dealtype), Is Closed Won (hs_is_closed_won), hs_name, hs_value, 4f_associated company ID (n4f_associated_company_id), 4f_deal_cutoff_date_new (n4f_deal_cutoff_date_new), 4f_Expected project end date (n4f_expected_project_end_date), Pipeline (pipeline); custom code: 4 custom code action(s)

Property Context

• Business Line (business_line) - 4flow definition of business line Roles: step data. internal name: business_line; object: Line Items; type: enumeration.
• Close Date (closedate) - Date the deal was closed. This property is set automatically by HubSpot. Roles: step data. internal name: closedate; object: Deals; type: datetime.
• Deal Type (dealtype) - The type of deal. By default, categorize your deal as either a New Business or Existing Business. Roles: branch condition, step data. internal name: dealtype; object: Deals; type: enumeration.
• Is Closed Won (hs_is_closed_won) - True if the deal is in the closed won state, false otherwise Roles: step data. internal name: hs_is_closed_won; object: Deals; type: bool.
• hs_name - No HubSpot property description returned. Roles: trigger condition. internal name: hs_name; object: object not returned; type: not returned.
• hs_value - No HubSpot property description returned. Roles: trigger condition. internal name: hs_value; object: object not returned; type: not returned.
• 4f_associated company ID (n4f_associated_company_id) - stores the ID of the associated Company Roles: step data. internal name: n4f_associated_company_id; object: Touchpoints; type: number.
• 4f_deal_cutoff_date_new (n4f_deal_cutoff_date_new) - used to define new business vs existing business. Cutoff date is calculated based on start date, duration, end date + define cadence Roles: branch condition, step data. internal name: n4f_deal_cutoff_date_new; object: Deals; type: date.
• 4f_Expected project end date (n4f_expected_project_end_date) - calculated property based on Start Date and Duration in Months Roles: step data. internal name: n4f_expected_project_end_date; object: Deals; type: date.
• Pipeline (pipeline) - The pipeline the deal is in. This determines which stages are options for the deal. Roles: trigger condition. internal name: pipeline; object: Deals; type: enumeration.

Evidence And Gaps

• Domain evidence: Derived from configured workflow scope prefix: ELEVATE
• Quality flags: custom_code_present: Workflow appears to contain one or more custom code actions. branching_logic_present: Workflow contains branching logic.
• Narrative context: not used as source of truth.