A Branch is a type of Control that lets you create multiple paths inside a single Automation. When a user reaches a Branch step, Optix checks the condition at the start of each path from left to right and runs the first path that matches. If no path matches, the Fallback path runs.
Branching is an Automations+ feature.
Branch helps you:
Keep related workflows in one Automation: Instead of creating a separate Automation for each plan type or member segment, build one Automation with paths for each scenario.
Reduce re-enrollment conflicts: When the same trigger (like "New plan added") would otherwise fire multiple Automations, branching keeps the logic in one place and prevents members from being enrolled in more than one Automation for the same event.
Handle exceptions cleanly: Use the Fallback path to define what happens when no branch condition is met — whether that's a default action or simply doing nothing.
How a Branch works
How a Branch works
When a user reaches a Branch step, Optix evaluates each path from left to right. The first path whose condition matches is the one that runs. All other paths are skipped.
For example, in an Automation for new plan sign-ups:
Trigger: New plan added
Branch:
Branch A: Plan template is Balance Membership → Send the Balance onboarding email
Branch B: Plan template is Wellbeing Membership → Send the Wellbeing onboarding email
Fallback: Send a general welcome email
Action: Change account type
In this example, a user who signs up for the Balance Membership receives the Balance onboarding email. The Automation then continues to the tag step after the Branch completes.
How to add a Branch
How to add a Branch
Click the "+" button to add a new step.
Select Branch.
Configure the condition for each path. Each path (except Fallback) must start with a Condition.
Add steps inside each path — these can include Actions, Delays, Conditions, or a Stop step.
To add another path, click + Add branch.
Note: Each Branch step requires at least two paths. The last path is always the Fallback.
FAQs
FAQs
What is the Fallback path?
The Fallback path is the final path in a Branch. It runs when none of the earlier path conditions match. You can add steps to Fallback, or leave it empty if no action is needed for unmatched cases.
What happens after a Branch path finishes?
After the selected path finishes, the Automation continues with the next step after the Branch — unless the path ends with a Stop step, which ends the enrollment at that point.
Can I stop the Automation inside a Branch?
Yes. You can add a Stop step inside any Branch path to end that enrollment at that point. The Stop step is only available inside a Branch path.
Can I see which path a user took?
Yes. In the enrollment view for that user, Optix shows which path was selected and which paths were skipped.
Do Actions inside a Branch count toward my monthly Action limit?
Actions inside the selected path run and count toward your monthly Action limit. Actions inside skipped paths do not run and are not counted.
Which plan includes Branching?
Branching is an Automations+ feature and is not available on the base Automations tier.
Can I save a Branch before it is fully configured?
Yes. You can save an Automation with incomplete Branch steps as a draft. However, the Automation cannot go live until all Branch paths are fully configured — each non-Fallback path must start with a Condition and include at least one Action or Stop step.
Troubleshooting
Troubleshooting
My Automation won't go live after adding a Branch
Every non-Fallback path must be fully configured before an Automation can go live. Each path must start with a Condition and include at least one Action or Stop step. Check each path for incomplete steps and complete or remove them.
The Fallback path is always running
This means none of the earlier path conditions are matching. Check that the condition variable and value in each path exactly match what is set on the user's profile or plan. Even a small mismatch (such as a different plan template name) will cause the path to be skipped.
A user went through the wrong path
Paths are evaluated left to right and the first match runs. If a user is matching an earlier path when they should match a later one, reorder your paths so the more specific conditions appear first. Check the enrollment view to see exactly which path was selected and why.
I can't find the Stop step
Stop steps are only available inside a Branch path. If you don't see Stop as an option, make sure you are adding the step inside a Branch path rather than in the main Automation flow.
Actions inside a Branch are not running
Open the enrollment view for the affected user and check which path was selected. If the path was skipped, its Actions will not run. If the correct path was selected but Actions still did not run, check whether a Condition inside that path stopped the flow before reaching the Action.
To learn more about Conditions, check out this article.
To learn more about Actions, check out this article.
To learn more about Automations+, check out this article.