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 - Fill 4f_lead interest for tracking of activities

METADATA title: ELEVATE - Fill 4f_lead interest for tracking of activities 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: 5
• Property references: hs_name, hs_value
• List references: none detected
• Filter types: PROPERTY: 2
• Operators: ALL_PROPERTY: 1, HAS_COMPLETED: 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

Steps

Step 1 - Action 1

• What happens: Runs custom code; 2 inputs; 0 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: none detected; lists: none detected

DATA MEANING:

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

ACTION EVIDENCE:

• Action category: custom_code
• 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: hs_updated_by_user_id, n4f_lead__interest
• Conditions detected in code: Code condition: if (!Private_App_Token) { Code condition: if (!updatedByUserId) { Code condition: if (updatedByUserId === “49698977”) {
• CRM/API operations detected: updates records or resources
• Concrete CRM operations: read by ID: objects; update: objects
• Search/filter evidence: none detected
• Data transformations: serializes data as JSON
• Outputs returned to workflow: outputFields, skipped_due_to_exclusion, updated_by_user_id
• HubSpot CRM objects affected or referenced: objects
• Associations handled: none detected
• Workflow control: contains asynchronous execution, returns output fields to later workflow actions
• Safeguards/error handling: error or warning logging, guard clauses or missing-value checks, structured response handling, try/catch error handling, checks missing values, has catch block, logs 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: 74 lines returned; code body analyzed but omitted from docs

System Behavior

• Workflow actions: 1
• Branch actions: 0
• Custom code actions: 1
• Property operations: 0
• List dependencies: 0
• Action categories: custom_code: 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: objects (custom code contains update call)
• Associations created: Logic not derivable from system.
• Marketing emails sent: 0
• Internal notifications: 0
• Sequence enrollments: 0
• Subscription updates: 0
• Webhooks: 0
• Custom code actions: 1

How It Is Implemented

Workflows

• Workflow: ELEVATE - Fill 4f_lead interest for tracking of activities
  • Workflow ID: 2570213600
  • Revision ID: 9
  • Enabled: yes
  • Current HubSpot description: Updates a custom lead property with the user ID of the person who last updated the lead when the “Lead Owner” property value changes.
  • Purpose: Updates a custom lead property with the user ID of the person who last updated the lead when the “Lead Owner” property value changes.
  • Key logic: custom_code: 1
  • Branching logic: 0 branch detail(s) returned by HubSpot No branch logic returned by HubSpot.
  • Dependencies: lists: none detected; properties: hs_name, Updated by user ID (hs_updated_by_user_id), hs_value, 4f_Lead interest (n4f_lead__interest); custom code: 1 custom code action(s)

Property Context

• hs_name - No HubSpot property description returned. Roles: trigger condition. internal name: hs_name; object: object not returned; type: not returned.
• Updated by user ID (hs_updated_by_user_id) - The user who last updated this record. This value is set automatically by HubSpot. Roles: reference. internal name: hs_updated_by_user_id; object: Line Items; type: number.
• hs_value - No HubSpot property description returned. Roles: trigger condition. internal name: hs_value; object: object not returned; type: not returned.
• 4f_Lead interest (n4f_lead__interest) - collects all 4Flowers who e.g. were former owners or assigned other owners - for tracking purposes Roles: reference. internal name: n4f_lead__interest; object: Leads; 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.
• Narrative context: not used as source of truth.