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 - Admin notifications for created deals and won deals | logo use approved in company

METADATA title: ELEVATE - Admin notifications for created deals and won deals | logo use approved in company 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: 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: ENUMERATION: 1, HAS_COMPLETED: 1, IS_ANY_OF: 1, IS_EQUAL_TO: 1, STRING: 1
• Trigger logic:
  • Enrollment criteria type: EVENT_BASED
  • Enrollment branch 1:
    • AND group
      • hs_name equals dealstage
      • hs_value is any of 2528007373, 2528007372, 2528007368

Steps

Step 1 - Action 17

• What happens: Runs a connected HubSpot workflow action
• 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: 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 2 - Action 1

• What happens: Branches based on HubSpot list membership; 3 branches
• What triggers it: After action 17
• System condition: 3 branch condition(s) returned by HubSpot.
• What data is used: properties: Deal Stage (dealstage), Is Closed Won (hs_is_closed_won), Lead Name (hs_lead_name), 4f_Lead Source Level 1 (n4f_lead_source_level_1); 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.
• Is Closed Won (hs_is_closed_won): True if the deal is in the closed won state, false otherwise
• Lead Name (hs_lead_name): The full name of the lead.
• 4f_Lead Source Level 1 (n4f_lead_source_level_1): used for attribution of marketing leads, synchronized with touchpoint types (and deal sources)

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: created
  • Condition summary: created
  • Default branch: no
  • Next action IDs: 12
  • Referenced properties: Deal Stage (dealstage), Lead Name (hs_lead_name), 4f_Lead Source Level 1 (n4f_lead_source_level_1)
  • Referenced lists: none detected
  • Filter-like criteria returned: 7
  • Returned branch logic:
    • OR group
      • AND group
        • Deal Stage is any of Discovery
        • AND group
          • Lead Name is known
          • 4f_Lead Source Level 1 is any of Event booth meeting, 4flow event, Event session, Webinar, Content download, Listing platform, Inbound request, Externally hosted Webinar, Marketing assessment
• Branch: ordered
  • Condition summary: ordered
  • Default branch: no
  • Next action IDs: 2
  • 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 Ordered
• Branch: won
  • Condition summary: won
  • Default branch: no
  • Next action IDs: 8
  • Referenced properties: Deal Stage (dealstage), Is Closed Won (hs_is_closed_won)
  • Referenced lists: none detected
  • Filter-like criteria returned: 4
  • Returned branch logic:
    • OR group
      • AND group
        • Deal Stage is any of Closed Won
      • AND group
        • Is Closed Won equals True

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 12

• 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
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Sends an internal notification
• Returned action type: SINGLE_CONNECTION
• Returned field keys: body, subject, user_ids
• subject: A new marketing generated deal was created
• user_ids: Kathrin Witt, Patrick Gälweiler

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 13

• What happens: Uses HubSpot list membership; 1 list dependencies
• What triggers it: After action 12
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: 12658

DATA MEANING:

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

ACTION EVIDENCE:

• Action category: connected_action
• Detected intent: Uses HubSpot list membership
• Returned action type: SINGLE_CONNECTION
• Returned field keys: listId, targetObject

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• List 12658 (12658)
  • Business meaning: Logic not derivable from system.
  • Filters: Logic not derivable from system.
  • Referenced properties: none detected
  • Filter logic: Logic not derivable from system because no list filter branch was returned.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 5 - Action 2

• What happens: Branches based on a returned value or property; 3 branches
• What triggers it: After action 1
• System condition: 3 branch condition(s) returned by HubSpot.
• What data is used: properties: Logo use approved (marketing_approval); lists: none detected

DATA MEANING:

• Logo use approved (marketing_approval): Did the customer sign our contract including approval of logo use?

ACTION EVIDENCE:

• Action category: static_branch
• Detected intent: Branches based on a returned value or property
• Input value: value from property marketing_approval
• Returned action type: STATIC_BRANCH

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• Branch: true
  • Condition summary: marketing_approval = true
  • Default branch: no
  • Next action IDs: 5
  • Referenced properties: Logo use approved (marketing_approval)
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch value: true
• Branch: false
  • Condition summary: marketing_approval = false
  • Default branch: no
  • Next action IDs: 7
  • Referenced properties: Logo use approved (marketing_approval)
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch value: false
• Branch: default branch
  • Condition summary: default branch
  • Default branch: yes
  • Next action IDs: 7
  • Referenced properties: Logo use approved (marketing_approval)
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch name: default branch
      • Next action: 7

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 5

• What happens: Sets HubSpot property values; properties: n4f_logo_use_approved = static value Yes
• What triggers it: After action 2
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: 4f_Logo use approved (n4f_logo_use_approved); lists: none detected

DATA MEANING:

• 4f_Logo use approved (n4f_logo_use_approved): Set after deal is won by Account Manager. Gives Marketing overview over logo use approval e.g. on website etc.

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: n4f_logo_use_approved
• 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_Logo use approved (n4f_logo_use_approved) is set or updated; value: static value Yes; confidence: high. Purpose: Set after deal is won by Account Manager. Gives Marketing overview over logo use approval e.g. on website etc.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 7 - Action 7

• What happens: Branches based on HubSpot list membership; 2 branches
• What triggers it: After action 5
• System condition: 2 branch condition(s) returned by HubSpot.
• What data is used: properties: 4f_Deal Source Level 1 (n4f_deal_source_level_1); lists: none detected

DATA MEANING:

• 4f_Deal Source Level 1 (n4f_deal_source_level_1): used for attribution of marketing deals, synchronized with touchpoint types (and lead sources)

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: marketing generated
  • Condition summary: marketing generated
  • Default branch: no
  • Next action IDs: 6
  • Referenced properties: 4f_Deal Source Level 1 (n4f_deal_source_level_1)
  • Referenced lists: none detected
  • Filter-like criteria returned: 2
  • Returned branch logic:
    • OR group
      • AND group
        • 4f_Deal Source Level 1 is any of Event booth meeting, 4flow event, Event session, Webinar, Content download, Inbound, Externally hosted Webinar
• Branch: not marketing generated
  • Condition summary: not marketing generated
  • Default branch: yes
  • Next action IDs: workflow exit or not returned
  • Referenced properties: none detected
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch name: not marketing generated

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 8 - Action 6

• What happens: Sends an internal notification
• What triggers it: After action 7
• 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
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Sends an internal notification
• Returned action type: SINGLE_CONNECTION
• Returned field keys: body, subject, user_ids
• subject: A new marketing generated deal was set to “ordered”
• user_ids: Kathrin Witt, Patrick Gälweiler, Mai-Britt Subei, Steven Chase, Nicola Berz

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 9 - Action 14

• What happens: Uses HubSpot list membership; 1 list dependencies
• 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: 12658

DATA MEANING:

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

ACTION EVIDENCE:

• Action category: connected_action
• Detected intent: Uses HubSpot list membership
• Returned action type: SINGLE_CONNECTION
• Returned field keys: listId, targetObject

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• List 12658 (12658)
  • Business meaning: Logic not derivable from system.
  • Filters: Logic not derivable from system.
  • Referenced properties: none detected
  • Filter logic: Logic not derivable from system because no list filter branch was returned.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 10 - Action 8

• What happens: Branches based on a returned value or property; 3 branches
• What triggers it: After action 1
• System condition: 3 branch condition(s) returned by HubSpot.
• What data is used: properties: Logo use approved (marketing_approval); lists: none detected

DATA MEANING:

• Logo use approved (marketing_approval): Did the customer sign our contract including approval of logo use?

ACTION EVIDENCE:

• Action category: static_branch
• Detected intent: Branches based on a returned value or property
• Input value: value from property marketing_approval
• Returned action type: STATIC_BRANCH

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• Branch: true
  • Condition summary: marketing_approval = true
  • Default branch: no
  • Next action IDs: 9
  • Referenced properties: Logo use approved (marketing_approval)
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch value: true
• Branch: false
  • Condition summary: marketing_approval = false
  • Default branch: no
  • Next action IDs: 10
  • Referenced properties: Logo use approved (marketing_approval)
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch value: false
• Branch: default branch
  • Condition summary: default branch
  • Default branch: yes
  • Next action IDs: 10
  • Referenced properties: Logo use approved (marketing_approval)
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch name: default branch
      • Next action: 10

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 11 - Action 10

• What happens: Branches based on HubSpot list membership; 2 branches
• What triggers it: After action 8
• System condition: 2 branch condition(s) returned by HubSpot.
• What data is used: properties: 4f_Deal Source Level 1 (n4f_deal_source_level_1); lists: none detected

DATA MEANING:

• 4f_Deal Source Level 1 (n4f_deal_source_level_1): used for attribution of marketing deals, synchronized with touchpoint types (and lead sources)

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: marketing generated
  • Condition summary: marketing generated
  • Default branch: no
  • Next action IDs: 11
  • Referenced properties: 4f_Deal Source Level 1 (n4f_deal_source_level_1)
  • Referenced lists: none detected
  • Filter-like criteria returned: 2
  • Returned branch logic:
    • OR group
      • AND group
        • 4f_Deal Source Level 1 is any of Event booth meeting, 4flow event, Event session, Webinar, Content download, Inbound, Externally hosted Webinar
• Branch: not marketing generated
  • Condition summary: not marketing generated
  • Default branch: yes
  • Next action IDs: 16
  • Referenced properties: none detected
  • Referenced lists: none detected
  • Filter-like criteria returned: 0
  • Returned branch logic:
    • AND group
      • Branch name: not marketing generated
      • Next action: 16

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 12 - Action 11

• What happens: Sends an internal notification
• What triggers it: After action 10
• 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
• Connection: object with keys: edgeType, nextActionId
• Detected intent: Sends an internal notification
• Returned action type: SINGLE_CONNECTION
• Returned field keys: body, subject, user_ids
• subject: A new marketing generated deal was won - please check the marketing relevance rating
• user_ids: Kathrin Witt, Patrick Gälweiler, Mai-Britt Subei, Elizabeth Whitney, Steven Chase, Nicola Berz

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 13 - Action 15

• What happens: Uses HubSpot list membership; 1 list dependencies
• What triggers it: After action 11
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: none detected; lists: 12658

DATA MEANING:

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

ACTION EVIDENCE:

• Action category: connected_action
• Detected intent: Uses HubSpot list membership
• Returned action type: SINGLE_CONNECTION
• Returned field keys: listId, targetObject

ACTION-LEVEL CONDITIONS:

• No extra action-level filter logic detected.

BRANCH LOGIC:

• No branch paths detected in this step.

LIST LOGIC:

• List 12658 (12658)
  • Business meaning: Logic not derivable from system.
  • Filters: Logic not derivable from system.
  • Referenced properties: none detected
  • Filter logic: Logic not derivable from system because no list filter branch was returned.

PROPERTY MAPPINGS:

• No property mappings detected in this step.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

Step 14 - Action 16

• What happens: Sends an internal notification
• What triggers it: After action 10
• 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, user_ids
• subject: A deal was won - please check the marketing relevance rating
• user_ids: Kathrin Witt, Patrick Gälweiler, Mai-Britt Subei, Elizabeth Whitney, Steven Chase, Nicola Berz

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 15 - Action 9

• What happens: Sets HubSpot property values; properties: n4f_logo_use_approved = static value Yes
• What triggers it: After action 8
• System condition: Previous workflow connection or enrollment trigger returned by HubSpot.
• What data is used: properties: 4f_Logo use approved (n4f_logo_use_approved); lists: none detected

DATA MEANING:

• 4f_Logo use approved (n4f_logo_use_approved): Set after deal is won by Account Manager. Gives Marketing overview over logo use approval e.g. on website etc.

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: n4f_logo_use_approved
• 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_Logo use approved (n4f_logo_use_approved) is set or updated; value: static value Yes; confidence: high. Purpose: Set after deal is won by Account Manager. Gives Marketing overview over logo use approval e.g. on website etc.

CUSTOM CODE LOGIC:

• No custom code detected in this step.

System Behavior

• Workflow actions: 15
• Branch actions: 5
• Custom code actions: 0
• Property operations: 2
• List dependencies: 3
• Action categories: connected_action: 4, internal_notification: 4, list_branch: 3, set_property: 2, static_branch: 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: Deal: 2 property operation(s)
• Associations created: Logic not derivable from system.
• Marketing emails sent: 0
• Internal notifications: 4
• Sequence enrollments: 0
• Subscription updates: 0
• Webhooks: 0
• Custom code actions: 0

How It Is Implemented

Workflows

• Workflow: ELEVATE - Admin notifications for created deals and won deals

  logo use approved in company

  • Workflow ID: 2393497840
  • Revision ID: 55
  • Enabled: yes
  • Current HubSpot description: No workflow description returned.
  • Purpose: Logic not derivable from system.
  • Key logic: connected_action: 4, internal_notification: 4, list_branch: 3, set_property: 2, static_branch: 2
  • Branching logic: 13 branch detail(s) returned by HubSpot
  • created: created; next actions: 12; properties: dealstage, hs_lead_name, n4f_lead_source_level_1; lists: none detected
  • ordered: ordered; next actions: 2; properties: dealstage; lists: none detected
  • won: won; next actions: 8; properties: dealstage, hs_is_closed_won; lists: none detected
  • true: marketing_approval = true; next actions: 5; properties: marketing_approval; lists: none detected
  • false: marketing_approval = false; next actions: 7; properties: marketing_approval; lists: none detected
  • default branch: default branch; next actions: 7; properties: marketing_approval; lists: none detected
  • marketing generated: marketing generated; next actions: 6; properties: n4f_deal_source_level_1; lists: none detected
  • not marketing generated : not marketing generated ; next actions: not returned; properties: none detected; lists: none detected
  • true: marketing_approval = true; next actions: 9; properties: marketing_approval; lists: none detected
  • false: marketing_approval = false; next actions: 10; properties: marketing_approval; lists: none detected
  • default branch: default branch; next actions: 10; properties: marketing_approval; lists: none detected
  • marketing generated: marketing generated; next actions: 11; properties: n4f_deal_source_level_1; lists: none detected
  • Dependencies: lists: 12658 (12658); properties: Deal Stage (dealstage), Is Closed Won (hs_is_closed_won), Lead Name (hs_lead_name), hs_name, hs_value, Logo use approved (marketing_approval), 4f_Deal Source Level 1 (n4f_deal_source_level_1), 4f_Lead Source Level 1 (n4f_lead_source_level_1), 4f_Logo use approved (n4f_logo_use_approved); 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.
• Is Closed Won (hs_is_closed_won) - True if the deal is in the closed won state, false otherwise Roles: branch condition, step data. internal name: hs_is_closed_won; object: Deals; type: bool.
• Lead Name (hs_lead_name) - The full name of the lead. Roles: branch condition, step data. internal name: hs_lead_name; object: Leads; type: string.
• 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.
• Logo use approved (marketing_approval) - Did the customer sign our contract including approval of logo use? Roles: branch condition, step data. internal name: marketing_approval; object: Deals; type: enumeration.
• 4f_Deal Source Level 1 (n4f_deal_source_level_1) - used for attribution of marketing deals, synchronized with touchpoint types (and lead sources) Roles: branch condition, step data. internal name: n4f_deal_source_level_1; object: Deals; type: enumeration.
• 4f_Lead Source Level 1 (n4f_lead_source_level_1) - used for attribution of marketing leads, synchronized with touchpoint types (and deal sources) Roles: branch condition, step data. internal name: n4f_lead_source_level_1; object: Leads; type: enumeration.
• 4f_Logo use approved (n4f_logo_use_approved) - Set after deal is won by Account Manager. Gives Marketing overview over logo use approval e.g. on website etc. Roles: property updated, step data. internal name: n4f_logo_use_approved; object: Companies; type: enumeration.

Evidence And Gaps

• Domain evidence: Derived from configured workflow scope prefix: ELEVATE
• 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.