Branch · Flow · Runs every branch
Sends each record down every branch at once, so the same record can be acted on several ways in parallel.
When to use it
Use it when one record should trigger more than one outcome — for example, send a matched account to your CRM *and* post it to Slack *and* enrich its contacts.
What it does
Branch sends every record down each of its arms in parallel — there are no conditions to match. By default, the arms reunite at the next step you place after the branch (the "join"); you don't have to wire that yourself, the canvas connects them for you. At the join, the arms merge back into one record carrying every arm's outputs, so any step below the join runs once and Activity shows one row per record — not one per arm. A branch lets a record do several things and then carry on down one shared path.
Configure it
Branches — add an arm for each parallel path and give it a label. Each arm leads to its own steps before rejoining.
Rejoin the shared steps — a switch on each arm, on by default. Turn it off for an arm so records taking it stop after its steps instead of rejoining the shared path. At least one arm must stay switched on.
Cost
No credit cost. See Credits in workflows.
Gotchas
Arms rejoin by default. If you want an arm to finish on its own instead, turn off Rejoin the shared steps for it. At least one arm has to keep rejoining.
You can use more than one Branch or Route in a workflow, including nested inside another arm, and a Branch can be the very first step after the trigger.
Use Route instead when a record should take only one path based on its data.