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

TEST ELEVATE - re-assign Leads and Deals from deactivated Users

METADATA title: TEST ELEVATE - re-assign Leads and Deals from deactivated Users type: process domain: Unclassified objects: [Contact] 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: LIST_BASED
• Criteria type: LIST_BASED
• Filter-like criteria returned: 3
• Property references: Owner’s main team (hubspot_team_id)
• List references: none detected
• Filter types: PROPERTY: 1
• Operators: ENUMERATION: 1, IN_LIST: 1, IS_ANY_OF: 1
• Trigger logic:
  • Enrollment criteria type: LIST_BASED
  • Enrollment branch 1:
    • OR group
      • AND group
        • AND group
          • Owner’s main team is any of 167069001
  • Enrollment branch 2:
    • AND group
      • AND group
        • Owner’s main team is any of 167069001
  • Enrollment branch 3:
    • AND group
      • Owner’s main team is any of 167069001
• Trigger property meaning:
  • Owner’s main team (hubspot_team_id): The main team of the record owner. This value is set automatically by HubSpot.

Steps

Step 1 - Action 1

• What happens: Branches based on HubSpot list membership; 2 branches
• What triggers it: Workflow start action returned by HubSpot
• System condition: 2 branch condition(s) returned by HubSpot.
• What data is used: properties: Deal Stage (dealstage), Lead stage (hs_pipeline_stage), Owner (hubspot_owner_id); lists: none detected

DATA MEANING:

• Deal Stage (dealstage): The stage of the deal. Deal stages allow you to categorize and track the progress of the deals that you are working on.
• 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.

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: Open Deal
  • Condition summary: Open Deal
  • Default branch: no
  • Next action IDs: 3
  • Referenced properties: Deal Stage (dealstage), Owner (hubspot_owner_id)
  • Referenced lists: none detected
  • Filter-like criteria returned: 6
  • Returned branch logic:
    • OR group
      • AND group
        • AND group
          • Deal Stage is any of Discovery, Validation, Proposal sent, Proposal in preparation
        • AND group
          • Owner is known
• Branch: Open Lead
  • Condition summary: Open Lead
  • Default branch: no
  • Next action IDs: 2
  • Referenced properties: Lead stage (hs_pipeline_stage), Owner (hubspot_owner_id)
  • Referenced lists: none detected
  • Filter-like criteria returned: 5
  • Returned branch logic:
    • OR group
      • AND group
        • AND group
          • Owner is known
          • Lead stage is any of Qualification, Assignment, Outreach

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 2

• What happens: Sets HubSpot property values; properties: hubspot_owner_id = static value not returned
• What triggers it: After action 1
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: Owner (hubspot_owner_id); lists: none detected

DATA MEANING:

• Owner (hubspot_owner_id): The owner of the object.

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: hubspot_owner_id
• value: [object Object]

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:

• Owner (hubspot_owner_id) is set or updated; value: static value not returned; confidence: high. Purpose: The owner of the object.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 3 - Action 5

• What happens: Sends an internal notification
• What triggers it: After action 2
• 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, user_ids
• subject: Re-assign lead
• team_ids: Demand-Gen & CRM
• user_ids: Soeren Hagen

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 3

• What happens: Sets HubSpot property values; properties: hubspot_owner_id = static value not returned
• What triggers it: After action 1
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: Owner (hubspot_owner_id); lists: none detected

DATA MEANING:

• Owner (hubspot_owner_id): The owner of the object.

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: hubspot_owner_id
• value: [object Object]

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:

• Owner (hubspot_owner_id) is set or updated; value: static value not returned; confidence: high. Purpose: The owner of the object.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 5 - Action 4

• What happens: Sends an internal notification
• 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: internal_notification
• Detected intent: Sends an internal notification
• Returned action type: SINGLE_CONNECTION
• Returned field keys: body, subject, team_ids, user_ids
• subject: Re-assign deal
• team_ids: Demand-Gen & CRM
• user_ids: Soeren Hagen

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: 5
• Branch actions: 1
• Custom code actions: 0
• Property operations: 2
• List dependencies: 0
• Action categories: internal_notification: 2, list_branch: 1, set_property: 2
• Property operation types: set_property: 2
• Associations created: listed under Outcomes when custom code exposes association evidence.

Outcomes

• Objects created: Logic not derivable from system.
• Objects updated: Contact: 2 property operation(s)
• 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: TEST ELEVATE - re-assign Leads and Deals from deactivated Users
  • Workflow ID: 3572920508
  • Revision ID: 15
  • Enabled: no
  • Current HubSpot description: No workflow description returned.
  • Purpose: Logic not derivable from system.
  • Key logic: internal_notification: 2, list_branch: 1, set_property: 2
  • Branching logic: 2 branch detail(s) returned by HubSpot
  • Open Deal: Open Deal; next actions: 3; properties: dealstage, hubspot_owner_id; lists: none detected
  • Open Lead: Open Lead; next actions: 2; properties: hs_pipeline_stage, hubspot_owner_id; lists: none detected
  • Dependencies: lists: none detected; properties: Deal Stage (dealstage), Lead stage (hs_pipeline_stage), Owner (hubspot_owner_id), Owner’s main team (hubspot_team_id); custom code: none detected

Property Context

• Deal Stage (dealstage) - The stage of the deal. Deal stages allow you to categorize and track the progress of the deals that you are working on. Roles: branch condition, step data. internal name: dealstage; object: Deals; type: enumeration.
• 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.
• Owner (hubspot_owner_id) - The owner of the object. Roles: branch condition, property updated, step data. internal name: hubspot_owner_id; object: Line Items; type: enumeration.
• Owner’s main team (hubspot_team_id) - The main team of the record owner. This value is set automatically by HubSpot. Roles: trigger condition. internal name: hubspot_team_id; object: Line Items; type: enumeration.

Evidence And Gaps

• Domain evidence: Domain not derivable from system metadata.
• Quality flags: 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.