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 - Notification on updated leads

METADATA title: ELEVATE - Notification on updated leads type: process domain: ELEVATE objects: [Lead] 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: 7
• Property references: hs_name, hs_value, 4f_Marketing Touchpoint count (n4f_marketing_touchpoint_count)
• List references: none detected
• Filter types: PROPERTY: 3
• Operators: ALL_PROPERTY: 1, HAS_COMPLETED: 1, IS_EQUAL_TO: 1, IS_GREATER_THAN: 1, IS_KNOWN: 1, NUMBER: 1, STRING: 1
• Trigger logic:
  • Enrollment criteria type: EVENT_BASED
  • Enrollment branch 1:
    • AND group
      • hs_name equals n4f_marketing_touchpoint_count
      • hs_value is known
  • Enrollment branch 2:
    • OR group
      • AND group
        • 4f_Marketing Touchpoint count is greater than 1
  • Enrollment branch 3:
    • AND group
      • 4f_Marketing Touchpoint count is greater than 1
• Trigger property meaning:
  • 4f_Marketing Touchpoint count (n4f_marketing_touchpoint_count): counts number of associated marketing touchpoints to give insights into multi-touch leads

Steps

Step 1 - Action 1

• What happens: Runs a connected HubSpot workflow action
• 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: 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 2 - Action 19

• What happens: Branches based on HubSpot list membership; 3 branches
• What triggers it: After action 1
• System condition: 3 branch condition(s) returned by HubSpot.
• What data is used: properties: Lead Type (hs_lead_type), Lead stage (hs_pipeline_stage); lists: none detected

DATA MEANING:

• Lead Type (hs_lead_type): The type of lead. By default, categorize your lead as either a New Business, Existing Business, or Re-attempting.
• Lead stage (hs_pipeline_stage): shows the pipeline stages of the lead pipeline. indicates which stage the lead is in

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: closed
  • Condition summary: closed
  • Default branch: no
  • Next action IDs: workflow exit or not returned
  • Referenced properties: Lead stage (hs_pipeline_stage)
  • Referenced lists: none detected
  • Filter-like criteria returned: 2
  • Returned branch logic:
    • OR group
      • AND group
        • Lead stage is any of Qualified, Disqualified
• Branch: re-opened
  • Condition summary: re-opened
  • Default branch: no
  • Next action IDs: 20
  • Referenced properties: Lead Type (hs_lead_type)
  • Referenced lists: none detected
  • Filter-like criteria returned: 4
  • Returned branch logic:
    • OR group
      • AND group
        • Lead Type is any of Re-opened
        • Lead Type is between object with keys: indexReference, offset, timeType, timezoneSource, zoneId
• Branch: default branch
  • Condition summary: default branch
  • Default branch: yes
  • Next action IDs: 9
  • Referenced properties: none detected
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch name: default branch
      • Next action: 9

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 20

• What happens: Sends an internal notification
• What triggers it: After action 19
• 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, owner_properties, subject, team_ids
• subject: A lead was re-opened based on a recent marketing touchpoint
• 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 4 - Action 9

• What happens: Sends an internal notification
• What triggers it: After action 19
• 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, owner_properties, subject, team_ids
• subject: A lead was updated based on a recent marketing touchpoint
• 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.

System Behavior

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

Outcomes

• Objects created: Logic not derivable from system.
• Objects updated: None detected.
• Associations created: Logic not derivable from system.
• Marketing emails sent: 0
• Internal notifications: 2
• Sequence enrollments: 0
• Subscription updates: 0
• Webhooks: 0
• Custom code actions: 0

How It Is Implemented

Workflows

• Workflow: ELEVATE - Notification on updated leads
  • Workflow ID: 2402439406
  • Revision ID: 69
  • Enabled: yes
  • Current HubSpot description: No workflow description returned.
  • Purpose: Logic not derivable from system.
  • Key logic: connected_action: 1, internal_notification: 2, list_branch: 1
  • Branching logic: 3 branch detail(s) returned by HubSpot
  • closed : closed ; next actions: not returned; properties: hs_pipeline_stage; lists: none detected
  • re-opened: re-opened; next actions: 20; properties: hs_lead_type; lists: none detected
  • default branch: default branch; next actions: 9; properties: none detected; lists: none detected
  • Dependencies: lists: none detected; properties: Lead Type (hs_lead_type), hs_name, Lead stage (hs_pipeline_stage), hs_value, 4f_Marketing Touchpoint count (n4f_marketing_touchpoint_count); custom code: none detected

Property Context

• Lead Type (hs_lead_type) - The type of lead. By default, categorize your lead as either a New Business, Existing Business, or Re-attempting. Roles: branch condition, step data. internal name: hs_lead_type; object: Leads; type: enumeration.
• hs_name - No HubSpot property description returned. Roles: trigger condition. internal name: hs_name; object: object not returned; type: not returned.
• Lead stage (hs_pipeline_stage) - shows the pipeline stages of the lead pipeline. indicates which stage the lead is in Roles: branch condition, step data. internal name: hs_pipeline_stage; object: Leads; type: enumeration.
• hs_value - No HubSpot property description returned. Roles: trigger condition. internal name: hs_value; object: object not returned; type: not returned.
• 4f_Marketing Touchpoint count (n4f_marketing_touchpoint_count) - counts number of associated marketing touchpoints to give insights into multi-touch leads Roles: trigger condition. internal name: n4f_marketing_touchpoint_count; object: Leads; type: number.

Evidence And Gaps

• Domain evidence: Derived from configured workflow scope prefix: ELEVATE
• Quality flags: branching_logic_present: Workflow contains branching logic.
• Narrative context: not used as source of truth.