Automations

Conditional Branches (If/Else)

Send contacts down different paths inside one workflow based on what they do or the data on their record.

Watch · 5 min Conditional branches — full walkthrough Read the article
1

Add a Condition step

A conditional branch is a fork in your workflow. You drop one step into the timeline, and from that point on contacts split into a "Yes" path and a "No" path depending on whether they match the rule you set.

Open the workflow you want to edit, then click the + button at the spot in the timeline where you want the split to happen. In the action picker, choose the If/Else condition step. Once it's added, every contact that reaches that point in the workflow is evaluated against your condition and routed to the matching branch.

Tip: Place the condition step after the action you want to react to. If you're branching on whether someone replied to a text, add the condition below the SMS step (and any wait time) so there's time for the reply to land before the workflow checks.
2

Branch on data or behavior

When you open the condition step, you choose what to test. You can branch on something the contact did (behavior) or on the data already sitting on their record — and each outcome becomes its own path.

Common conditions include whether the contact replied versus didn't reply, whether they have a specific tag, or whether their source equals "Website." You set the rule once, and the workflow sends everyone who matches down one branch and everyone who doesn't down the other. You can stack multiple rules with AND/OR when you need to be more precise — for example, source is "Website" and the contact is tagged "Buyer."

3

Build the paths

A branch is only useful once you fill it in. After the split, build out what happens on each side so the right people get the right message instead of a one-size-fits-all blast.

Click into a branch and keep adding steps to it just like the main workflow — sends, waits, tags, notifications, or even another nested condition. For example, contacts who replied might drop into the "Yes" branch and get a notification to your team, while contacts who didn't reply go down the "No" branch for a follow-up text a day later. When you're done, save and publish the workflow so the branching goes live for new contacts entering it.

Tip: You don't have to fill in both sides. Leaving the "No" branch empty simply lets those contacts continue down the workflow unchanged — handy when you only want to add an extra step for the people who match.