Branching
The Branching Node lets you split your workflow into multiple paths based on set conditions — ideal for segmenting your data into personas, geographies, funnel stages, or any other custom logic.
Think of it as a multi-lane highway where each record is routed to the right destination.
When to Use It
Use the Branching node when you want to:
Route different types of records to different actions
Personalize follow-up based on persona, region, or stage
Run parallel logic paths from the same dataset
How It Works
The Branching node doesn’t contain logic itself — instead, it creates multiple paths, each of which needs to be followed with a Condition node.
Each branch:
Starts immediately after the Branching node
Is treated independently (you can configure totally separate workflows per branch)
Can contain unique conditions, enrichment, sync actions, etc.
Example Use Cases
Persona-Based Branching: → Branch 1: Marketing roles → HubSpot → Branch 2: Sales roles → Outreach → Branch 3: RevOps roles → Salesforce
Geographic Segmentation: → US contacts → US sales team → EMEA contacts → EMEA SDRs → APAC contacts → filtered out
Last updated