Using branches in automation workflows

Branches let you split subscribers into separate paths within a single automation based on conditions, percentages, or a combination of both. Instead of building multiple automations to handle different subscriber scenarios, you can handle them all within one workflow.

beehiiv offers three branch types: True/false, Multi-split, and Random cohort. Each is suited to different use cases, and all of them share the same reconnection behavior, meaning after each path does its thing, subscribers flow back into a single unified point and the workflow continues together.

This article explains how each branch type works, when to use each one, and how to set them up.

Before diving into each branch type, there are two behaviors that apply to all of them.

When you add any branch to your workflow, all paths automatically reconnect at a shared exit point. This means you can send different subscribers down different paths — different emails, different delays, different actions — and then bring them all back together to continue through the same steps afterward.

For example, you could send different welcome emails based on how someone subscribed, then continue with the same nurture sequence for everyone, all within a single automation.

If you want a path to end early, rather than reconnect, add an Exit automation node to that path. Subscribers who reach an Exit node leave the automation entirely from that point and do not continue to the reconnected steps.

You don't need to add an Exit node to every path, only to paths where you want the journey to end early.

Use this handy chart to determine which branch to use, then see the directions for each below.

The True/false branch splits subscribers into two paths based on conditions you define. Subscribers who meet the conditions follow the True path; everyone else follows the False path. 

This is the simplest branch type and works well when you have a single condition or set of conditions that cleanly divides your audience into two groups.

When to use it: Use a True/false branch when you want to separate engaged from unengaged subscribers, check whether someone has a specific tag or custom field value, or route paid vs. free subscribers differently.

1. From your account dashboard, go to Audience > Automations, then open an existing workflow or create a new one.
2. Click the + icon at the point where you want the split to occur and select True/false branch from the Flow control actions.
   
   
   

3. The Properties panel opens on the right. Click + Add condition to define your conditions using the dropdowns and input fields. Add multiple conditions if needed.
   
   
   
4. When finished, click Save or click outside the panel to return to the canvas.
5. Build out the True path by clicking the + icon beneath it and adding actions for subscribers who meet your conditions.
6. Build out the False path by clicking the + icon beneath it and adding actions for subscribers who don't meet your conditions.
   
   
   

A Multi-split branch lets you create up to 5 parallel paths, each with its own conditions. Paths are evaluated in order, and the first path whose conditions a subscriber meets is the one they enter. An All others fallback path ensures every subscriber is routed somewhere, even if they don't match any defined path.

When to use it: Use a Multi-split branch when your audience needs to be routed into more than two groups based on different attributes, tags, custom fields, referring URLs, or segment membership. It's especially powerful for personalized onboarding flows where different subscriber types need meaningfully different experiences.

1. In your workflow, click the + icon at the point where you want the split to occur and select Multi-split branch from the Flow control actions.
   
   
   
2. The Properties panel opens on the right. Click + Add path to add paths, up to five total.
3. For each path, click + Add condition and define the conditions using the dropdowns and input fields.
4. Reorder paths by dragging them in the side panel if needed. The path at the top is evaluated first.
5. Click Save on conditions or click outside the panel to return to the canvas.
6. Build out each path by clicking the + icon beneath it and adding the relevant actions.
7. The All others path is always present, you can leave it empty (subscribers will pass straight through to the reconnection point) or add steps to it.

A Random cohort branch randomly distributes subscribers across 2-5 paths based on percentages you assign. Unlike True/false and Multi-split branches, subscriber attributes don't determine which path they enter, it's purely random based on the weights you set.

When to use it: Use a Random cohort branch for testing different post-signup flows, gradually rolling out a new email sequence to a portion of your audience, or creating a control group to measure the impact of specific automation steps.

1. In your workflow, click the + icon at the point where you want the split to occur and select Random cohort branch from the Flow control actions.
   
   
   
2. The Properties panel opens on the right. You'll start with two paths by default. Click + Add another path to add more, up to five total.
3. Assign a percentage to each path. Percentages must add up to 100%.
   
   
   
4. Click Split evenly to reset all paths to equal distribution at any time.
5. To lock a path's percentage, click the lock icon next to it. Locked paths stay fixed while you adjust the others.
6. Click outside the panel to return to the canvas.
7. Build out each path by clicking the + icon beneath it and adding the relevant actions.

Can I use more than one branch type in the same automation?
Yes. You can combine branch types within a single workflow. For example, you might use a Random cohort branch to split subscribers for a test, then use a True/false branch further down to route based on engagement.
What happens if I leave a path empty in a Multi-split or True/false branch?
Subscribers routed to an empty path pass straight through to the reconnection point without any additional steps being applied.
Can I nest branches inside other branches?
Yes. You can add a branch within a path of another branch. This lets you build more granular logic without creating separate automations.
What's the difference between deleting a branch path and adding an Exit automation node?
Deleting a path removes it entirely. Adding an Exit automation node keeps the path in the workflow but ends the journey for subscribers who enter it — they leave the automation at that point rather than continuing to the reconnected steps.