Outbound - AE to BDR - Step 1 (Event Followup)

FieldValue
ID101298366
StatusEnabled
Object TypeCONTACT
Scopesales
CreatedJan 15, 2026
UpdatedJan 15, 2026

Functional Analysis

Business Trigger: Event followup requires AE to BDR handoff

Business Outcome: Initiates BDR followup sequence for post-event prospects

Type: Routing | Complexity: medium

Multi-step process with event followup specific logic

**HubSpot Workaround:** Multi-step workflow pattern for complex routing logic

How This Workflow Functions

This workflow is designed to convert the trigger "Event followup requires AE to BDR handoff" into the outcome "Initiates BDR followup sequence for post-event prospects".

Runtime MetricValue
Total action nodes7
Decision points (branches)3
Data update actions0
Delay/wait actions1
Notification actions0
Task creation actions0
External call actions0

Enrollment / Entry Criteria

_No explicit enrollment criteria were found in the extracted payload._

Step-by-Step Action Flow

SequenceContextAction TypeWhat Happens
1Main FlowBRANCHEvaluate branch logic and route to the matching path
1.A.1Main Flow > AcceptedSET_COMPANY_PROPERTYExecute SET_COMPANY_PROPERTY action
1.R.1Main Flow > RejectedDELAYDelay for a configured period
1.R.2Main Flow > RejectedBRANCHEvaluate conditions: num_associated_deals GTE 1 OR lifecyclestage SET_ANY 48512630;opportunity;customer
1.R.2.R.1Main Flow > Rejected > RejectedBRANCHEvaluate conditions: hubspot_owner_id SET_ANY 86258918;80981656;84417371;86526326;69713900;87573378;86866057;82757388;86970735;85412724;84996041;80432059;88115994;83340986;81613954;83632252
1.R.2.R.1.A.1Main Flow > Rejected > Rejected > AcceptedUNSUPPORTED_ACTIONExecute UNSUPPORTED_ACTION action
1.R.2.R.1.R.1Main Flow > Rejected > Rejected > RejectedLEAD_ASSIGNMENTExecute LEAD_ASSIGNMENT action

Data Touchpoints

FieldUsageContexts
num_associated_dealsreadbranchCondition
lifecyclestagereadbranchCondition
hubspot_owner_idreadbranchCondition

Action Narrative

Group: AE-BDR Lead Routing