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- Mark deals which can count as lost if lost

METADATA title: ELEVATE- Mark deals which can count as lost if lost 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: 2
• Property references: Deal Stage (dealstage)
• List references: none detected
• Filter types: PROPERTY: 1
• Operators: ENUMERATION: 1, HAS_EVER_BEEN_ANY_OF: 1
• Trigger logic:
  • Enrollment criteria type: LIST_BASED
  • Enrollment branch 1:
    • OR group
      • AND group
        • Deal Stage has ever been any of Ordered, Proposal sent
  • Enrollment branch 2:
    • AND group
      • Deal Stage has ever been any of Ordered, Proposal sent
• 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.

Steps

Step 1 - Action 1

• What happens: Sets HubSpot property values; properties: n4f_if_lost_count_as_lost = 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: 4f_if lost count as lost (n4f_if_lost_count_as_lost); lists: none detected

DATA MEANING:

• 4f_if lost count as lost (n4f_if_lost_count_as_lost): Property which is mainly used for controlling. Value is set as soon as a deal enters proposal in preparation stage. Relevant for reports.

ACTION EVIDENCE:

• Action category: set_property
• Detected intent: Sets HubSpot property values
• Returned action type: SINGLE_CONNECTION
• Returned field keys: property_name, value
• property_name: n4f_if_lost_count_as_lost
• 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:

• 4f_if lost count as lost (n4f_if_lost_count_as_lost) is set or updated; value: static value Yes; confidence: high. Purpose: Property which is mainly used for controlling. Value is set as soon as a deal enters proposal in preparation stage. Relevant for reports.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

System Behavior

• Workflow actions: 1
• Branch actions: 0
• Custom code actions: 0
• Property operations: 1
• List dependencies: 0
• Action categories: 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: Deal: 1 property operation(s)
• 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: 0

How It Is Implemented

Workflows

• Workflow: ELEVATE- Mark deals which can count as lost if lost
  • Workflow ID: 2805019866
  • Revision ID: 6
  • Enabled: yes
  • Current HubSpot description: Sets a property to “Yes” for deals that have ever been in the “Ordered” or “Proposal sent” stages.
  • Purpose: Sets a property to “Yes” for deals that have ever been in the “Ordered” or “Proposal sent” stages.
  • Key logic: set_property: 1
  • Branching logic: 0 branch detail(s) returned by HubSpot No branch logic returned by HubSpot.
  • Dependencies: lists: none detected; properties: Deal Stage (dealstage), 4f_if lost count as lost (n4f_if_lost_count_as_lost); 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: trigger condition. internal name: dealstage; object: Deals; type: enumeration.
• 4f_if lost count as lost (n4f_if_lost_count_as_lost) - Property which is mainly used for controlling. Value is set as soon as a deal enters proposal in preparation stage. Relevant for reports. Roles: property updated, step data. internal name: n4f_if_lost_count_as_lost; object: Deals; 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.