Branching with Paths, Filters, and Condition Branches
Use Filter, Condition Branch, and Paths steps to send each contact down the right route in a workflow.
Not every contact should get the same follow-up. SAMI OS gives you three flow-control steps — Filter, Condition Branch, and Paths — that decide who continues and which route they take. You'll find all three under the Flow Control group in the builder palette.
When to use each flow-control step
Each step changes the flow in a different way, so reach for the one that matches the decision you're making.
- Filter is a gate. The contact only continues if your conditions are met. If they aren't, the workflow stops for that contact.
- Condition Branch is a router. It checks conditions top-to-bottom and jumps to whichever step matches first, with a fallback for everyone else.
- Paths splits the flow into separate, named branches that each run their own steps — ideal for buyers vs. sellers, or hot vs. cold leads.
Use a Filter when you just want to drop contacts who don't qualify, and Paths when each group needs its own sequence of steps. Reach for Condition Branch when you want to redirect to an existing step rather than build a whole branch.
Build a Filter
Open a workflow from Workflows, drop a Filter step onto the canvas, and select it to open its panel.
Choose the match logic
Set Continue when to either All conditions match or Any condition matches. With "all," every condition must pass; with "any," one is enough.
Add a condition
Click Add condition, pick a field from your trigger or earlier steps using the data picker, then choose an operator.
Pick an operator and value
Operators are grouped Zapier-style: Text (Contains, Exactly matches, Starts with), Number (Greater than, Less than), Date/time (After, Before, Equals), Boolean (Is true, Is false), and General (Exists, Does not exist). Enter a value unless the operator doesn't need one.
If the conditions fail, the contact stops here — nothing after the Filter runs for them.
Split with Condition Branch or Paths
A Condition Branch redirects to a specific step. Add conditions in order; SAMI evaluates them top-to-bottom and the first match wins. For each row, set the If field, the Condition operator (equals, not equals, greater than, less than, is in, contains, exists, does not exist), a Value, and Then go to the target step. Anything that matches nothing follows the Default (no match) step you choose.
A Paths step creates labeled branches you can rename (Path A, Path B, and so on). For each path, set Match to All conditions or Any condition, add conditions, and connect that path's branch to its own steps. You can add condition groups and choose whether Any group matches or All groups match. Contacts who fit no path fall through to the Everything Else path.
The field picker pulls live data from your trigger and upstream steps, including contact details like Stage and SAMI Status, call outcomes, and custom fields — so you can branch on anything the workflow already knows.
Jump around with Go to Step
Need to loop a contact back or skip ahead? Add a Go to Step step and choose Jump to step. The contact continues from that point instead of moving to the next step in line — handy for re-checking a condition after a delay or rejoining a shared sequence. Combine it with branches from a workflow to keep your automation tidy instead of duplicating steps.
Related articles
Last updated 2026-06-21