TopolearnPaths let one Zap handle several cases instead of maintaining near-duplicate Zaps.
A filter can only say "continue or stop". Paths let a Zap choose between several routes, like an "if this, do that; otherwise do something else" decision.
Adding a Paths step creates branches, starting with Path A and Path B. Each branch has its own rules (written exactly like filter rules) and its own actions. Example for new support tickets:
- Path A, rule
PriorityequalsHigh: page the on-call person and post in #urgent. - Path B, rule
PriorityequalsLow: add to the weekly backlog sheet.
Each branch can use one of three rule types:
- Custom rules: run when the conditions match.
- Always run: run every time.
- Fallback: run only when no other branch in the group matched. Use it to catch the unexpected case instead of silently doing nothing.
A group can hold up to 10 branches, and you can put paths inside paths (up to 3 levels). If more than one branch matches, each matching branch runs. Branches run one after another, left to right, so a slow step such as a long Delay in Path A holds up Path B.
The Paths step itself does not use tasks; only the actions in the branches that run do.
Keep paths readable: name each branch ("High priority"), keep rules simple, and if a branch grows long, move its steps into a Sub-Zap.
Remember
- Paths = several rule-based branches in one Zap
- Add a Fallback branch to handle data no rule matched
- Branches run in order, left to right
Watch out for
- Forgetting that several branches can match at once, so two different actions run for the same item.