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_Lead owner notification

METADATA title: ELEVATE_Lead owner notification 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_Lead Source Level 1 (n4f_lead_source_level_1)
• List references: none detected
• Filter types: PROPERTY: 3
• Operators: ALL_PROPERTY: 1, ENUMERATION: 1, HAS_COMPLETED: 1, IS_ANY_OF: 1, IS_EQUAL_TO: 1, IS_KNOWN: 1, STRING: 1
• Trigger logic:
  • Enrollment criteria type: EVENT_BASED
  • Enrollment branch 1:
    • AND group
      • hs_name equals hubspot_owner_id
      • hs_value is known
  • Enrollment branch 2:
    • OR group
      • AND group
        • 4f_Lead Source Level 1 is any of Event booth meeting, 4flow event, Event session, Webinar, Content download, Externally hosted Webinar, Marketing assessment
  • Enrollment branch 3:
    • AND group
      • 4f_Lead Source Level 1 is any of Event booth meeting, 4flow event, Event session, Webinar, Content download, Externally hosted Webinar, Marketing assessment
• Trigger property meaning:
  • 4f_Lead Source Level 1 (n4f_lead_source_level_1): used for attribution of marketing leads, synchronized with touchpoint types (and deal sources)

Steps

Step 1 - Action 3

• What happens: Sets HubSpot property values; properties: n4f_no_activity_after_assignment = static value Yes
• 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: n4f_no_activity_after_assignment; lists: none detected

DATA MEANING:

• n4f_no_activity_after_assignment: Used to detect if after assignment of a lead, the lead owner did an activity. Used in negative reports to identify stalling leads.

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_no_activity_after_assignment
• 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:

• n4f_no_activity_after_assignment is set or updated; value: static value Yes; confidence: high. Purpose: Used to detect if after assignment of a lead, the lead owner did an activity. Used in negative reports to identify stalling leads.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 2 - Action 1

• 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 2

• What happens: Sends an internal notification
• What triggers it: After action 1
• 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
• subject: assigned you as responsible for the 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:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

System Behavior

• Workflow actions: 3
• Branch actions: 0
• Custom code actions: 0
• Property operations: 1
• List dependencies: 0
• Action categories: connected_action: 1, internal_notification: 1, set_property: 1
• Property operation types: set_property: 1
• Associations created: listed under Outcomes when custom code exposes association evidence.

Outcomes

• Objects created: Logic not derivable from system.
• Objects updated: Lead: 1 property operation(s)
• Associations created: Logic not derivable from system.
• Marketing emails sent: 0
• Internal notifications: 1
• Sequence enrollments: 0
• Subscription updates: 0
• Webhooks: 0
• Custom code actions: 0

How It Is Implemented

Workflows

• Workflow: ELEVATE_Lead owner notification
  • Workflow ID: 3036304601
  • Revision ID: 21
  • Enabled: yes
  • Current HubSpot description: No workflow description returned.
  • Purpose: Logic not derivable from system.
  • Key logic: connected_action: 1, internal_notification: 1, set_property: 1
  • Branching logic: 0 branch detail(s) returned by HubSpot No branch logic returned by HubSpot.
  • Dependencies: lists: none detected; properties: hs_name, hs_value, 4f_Lead Source Level 1 (n4f_lead_source_level_1), n4f_no_activity_after_assignment; custom code: none detected

Property Context

• 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_Lead Source Level 1 (n4f_lead_source_level_1) - used for attribution of marketing leads, synchronized with touchpoint types (and deal sources) Roles: trigger condition. internal name: n4f_lead_source_level_1; object: Leads; type: enumeration.
• n4f_no_activity_after_assignment - Used to detect if after assignment of a lead, the lead owner did an activity. Used in negative reports to identify stalling leads. Roles: property updated, step data. internal name: n4f_no_activity_after_assignment; object: Leads; type: enumeration.

Evidence And Gaps

• Domain evidence: Derived from configured workflow scope prefix: ELEVATE
• Quality flags: property_operations_detected: Workflow appears to write or copy one or more properties.
• Narrative context: not used as source of truth.