HubSpot Process Documentation
- 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 - Update Subscription Status
METADATA
title: TEST ELEVATE - Update Subscription Status
type: process
domain: Consent
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: EVENT_BASED
- Criteria type: EVENT_BASED
- Filter-like criteria returned: 8
- Property references: Unsubscribed from all email (hs_email_optout), Opted out of email: Marketing information (hs_email_optout_125011299), Opted out of email: Webinar & event news (hs_email_optout_159354956)
- List references: none detected
- Filter types: EMAIL_SUBSCRIPTION: 1, PROPERTY: 3
- Operators: BOOL: 1, ENUMERATION: 2, HAS_COMPLETED: 1, IS_ANY_OF: 2, IS_EQUAL_TO: 1
- Trigger logic:
- Enrollment criteria type: EVENT_BASED
- Enrollment branch 1:
- AND group
- Returned branch keys: eventTypeId, filterBranchOperator, filterBranchType, filterBranches, filters, operator
- Enrollment branch 2:
- OR group
- AND group
- Opted out of email: Marketing information is any of Yes
- AND group
- Unsubscribed from all email equals True
- AND group
- Opted out of email: Webinar & event news is any of Yes
- AND group
- EMAIL_SUBSCRIPTION filter matches
- Enrollment branch 3:
- AND group
- Opted out of email: Marketing information is any of Yes
- Enrollment branch 4:
- AND group
- Unsubscribed from all email equals True
- Enrollment branch 5:
- AND group
- Opted out of email: Webinar & event news is any of Yes
- Enrollment branch 6:
- AND group
- EMAIL_SUBSCRIPTION filter matches
- Trigger property meaning:
Steps
Step 1 - Action 3
- What happens: Updates communication subscription status
- 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: subscription_update
- Connection: object with keys: edgeType, nextActionId
- Detected intent: Updates communication subscription status
- Returned action type: SINGLE_CONNECTION
- Returned field keys: channel, legalBasis, legalBasisExplanation, optState, subscriptionId, targetContact
- legalBasis: CONSENT_WITH_NOTICE
- optState: OPT_IN
- subscriptionId: 159354956
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 6
- What happens: Runs a connected HubSpot workflow action
- 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: 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 3 - Action 8
- What happens: Branches based on HubSpot list membership; 1 branches
- What triggers it: After action 6
- System condition: 1 branch condition(s) returned by HubSpot.
- What data is used: properties: 4f_Custom DOI (n4f_doi); lists: none detected
DATA MEANING:
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: branch_1
- Condition summary: 2 returned criteria
- Default branch: no
- Next action IDs: 7
- Referenced properties: 4f_Custom DOI (n4f_doi)
- Referenced lists: none detected
- Filter-like criteria returned: 2
- Returned branch logic:
- OR group
- AND group
- 4f_Custom DOI is any of Nein
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 7
- What happens: Updates communication subscription status
- What triggers it: After action 8
- 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: subscription_update
- Detected intent: Updates communication subscription status
- Returned action type: SINGLE_CONNECTION
- Returned field keys: channel, legalBasis, legalBasisExplanation, optState, subscriptionId, targetContact
- legalBasis: CONSENT_WITH_NOTICE
- optState: OPT_OUT
- subscriptionId: 159354956
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: 4
- Branch actions: 1
- Custom code actions: 0
- Property operations: 0
- List dependencies: 0
- Action categories: connected_action: 1, list_branch: 1, subscription_update: 2
- 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: None detected.
- Associations created: Logic not derivable from system.
- Marketing emails sent: 0
- Internal notifications: 0
- Sequence enrollments: 0
- Subscription updates: 2
- Webhooks: 0
- Custom code actions: 0
How It Is Implemented
Workflows
- Workflow: TEST ELEVATE - Update Subscription Status
Property Context
Evidence And Gaps
- Domain evidence: Derived from workflow name term: subscription
- Quality flags: branching_logic_present: Workflow contains branching logic.
- Narrative context: not used as source of truth.