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_Deal_shift start date forward reminder

METADATA title: ELEVATE_Deal_shift start date forward reminder 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: LIST_BASED
• Criteria type: LIST_BASED
• Filter-like criteria returned: 4
• Property references: Deal Stage (dealstage), Planned start date (planned_start_date)
• List references: none detected
• Filter types: PROPERTY: 2
• Operators: ENUMERATION: 1, IS_BEFORE: 1, IS_NONE_OF: 1, TIME_POINT: 1
• Trigger logic:
  • Enrollment criteria type: LIST_BASED
  • Enrollment branch 1:
    • OR group
      • AND group
        • Planned start date is before
        • Deal Stage is none of Closed Won, Ordered, Closed Lost, Discovery
  • Enrollment branch 2:
    • AND group
      • Planned start date is before
      • Deal Stage is none of Closed Won, Ordered, Closed Lost, Discovery
• Trigger property 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.
  • Planned start date (planned_start_date): planned start date as defined by deal owner. Used to calculate end date and cutoff date in combination with duration (month) property

Steps

Step 1 - Action 1

• What happens: Branches based on HubSpot list membership; 3 branches
• What triggers it: Workflow start action returned by HubSpot
• System condition: 3 branch condition(s) returned by HubSpot.
• What data is used: properties: Deal Stage (dealstage); 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.

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: Validation
  • Condition summary: Validation
  • Default branch: no
  • Next action IDs: 4
  • Referenced properties: Deal Stage (dealstage)
  • Referenced lists: none detected
  • Filter-like criteria returned: 2
  • Returned branch logic:
    • OR group
      • AND group
        • Deal Stage is any of Validation
• Branch: Proposal in preparation
  • Condition summary: Proposal in preparation
  • Default branch: no
  • Next action IDs: 5
  • Referenced properties: Deal Stage (dealstage)
  • Referenced lists: none detected
  • Filter-like criteria returned: 2
  • Returned branch logic:
    • OR group
      • AND group
        • Deal Stage is any of Proposal in preparation
• Branch: Proposal sent
  • Condition summary: Proposal sent
  • Default branch: no
  • Next action IDs: 6
  • Referenced properties: Deal Stage (dealstage)
  • Referenced lists: none detected
  • Filter-like criteria returned: 2
  • Returned branch logic:
    • OR group
      • AND group
        • Deal Stage is any of Proposal sent

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 4

• What happens: Runs custom code; 1 inputs; 0 outputs
• 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: 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: planned_start_date

• Conditions detected in code: Code condition: if (raw === undefined

  raw === null) return null; Code condition: if (/^\d{13}$/.test(s)) { Code condition: if (!token) { Code condition: if (!dealId) { Code condition: if (!current) { Code condition: if (current.getTime() < todayUTC.getTime()) {

• CRM/API operations detected: updates records or resources
• Concrete CRM operations: read by ID: deals; update: deals
• Search/filter evidence: none detected
• Data transformations: calculates or formats dates, converts values to numbers, removes surrounding whitespace, serializes data as JSON
• Outputs returned to workflow: accessToken, outputFields
• HubSpot CRM objects affected or referenced: deals
• Associations handled: none detected
• 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, 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: 102 lines returned; code body analyzed but omitted from docs

Step 3 - Action 7

• What happens: Sends an internal notification
• What triggers it: After action 4
• 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: Reminder: Deal start date adjusted

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 5

• What happens: Runs custom code; 1 inputs; 0 outputs
• 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: 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: planned_start_date

• Conditions detected in code: Code condition: if (raw === undefined

  raw === null) return null; Code condition: if (/^\d{13}$/.test(s)) { Code condition: if (!token) { Code condition: if (!dealId) { Code condition: if (!current) { Code condition: if (current.getTime() < todayUTC.getTime()) {

• CRM/API operations detected: updates records or resources
• Concrete CRM operations: read by ID: deals; update: deals
• Search/filter evidence: none detected
• Data transformations: calculates or formats dates, converts values to numbers, removes surrounding whitespace, serializes data as JSON
• Outputs returned to workflow: accessToken, outputFields
• HubSpot CRM objects affected or referenced: deals
• Associations handled: none detected
• 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, 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: 102 lines returned; code body analyzed but omitted from docs

Step 5 - Action 8

• What happens: Sends an internal notification
• 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: internal_notification
• Detected intent: Sends an internal notification
• Returned action type: SINGLE_CONNECTION
• Returned field keys: body, owner_properties, subject
• subject: Reminder: Deal start date adjusted

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 6

• What happens: Runs custom code; 1 inputs; 0 outputs
• 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: 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: planned_start_date

• Conditions detected in code: Code condition: if (raw === undefined

  raw === null) return null; Code condition: if (/^\d{13}$/.test(s)) { Code condition: if (!token) { Code condition: if (!dealId) { Code condition: if (!current) { Code condition: if (current.getTime() < todayUTC.getTime()) {

• CRM/API operations detected: updates records or resources
• Concrete CRM operations: read by ID: deals; update: deals
• Search/filter evidence: none detected
• Data transformations: calculates or formats dates, converts values to numbers, removes surrounding whitespace, serializes data as JSON
• Outputs returned to workflow: accessToken, outputFields
• HubSpot CRM objects affected or referenced: deals
• Associations handled: none detected
• 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, 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: 102 lines returned; code body analyzed but omitted from docs

Step 7 - Action 10

• What happens: Sends an internal notification
• What triggers it: After action 6
• 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: Reminder: Deal start date adjusted

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

How It Is Implemented

Workflows

• Workflow: ELEVATE_Deal_shift start date forward reminder
  • Workflow ID: 2777356527
  • Revision ID: 45
  • Enabled: yes
  • Current HubSpot description: No workflow description returned.
  • Purpose: Logic not derivable from system.
  • Key logic: custom_code: 3, internal_notification: 3, list_branch: 1
  • Branching logic: 3 branch detail(s) returned by HubSpot
  • Validation: Validation; next actions: 4; properties: dealstage; lists: none detected
  • Proposal in preparation: Proposal in preparation; next actions: 5; properties: dealstage; lists: none detected
  • Proposal sent: Proposal sent; next actions: 6; properties: dealstage; lists: none detected
  • Dependencies: lists: none detected; properties: Deal Stage (dealstage), Planned start date (planned_start_date); custom code: 3 custom code action(s)

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, trigger condition. internal name: dealstage; object: Deals; type: enumeration.
• Planned start date (planned_start_date) - planned start date as defined by deal owner. Used to calculate end date and cutoff date in combination with duration (month) property Roles: trigger condition. internal name: planned_start_date; object: Deals; type: date.

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.