Paths by Zapier, Zap branches or branching logic
Paths let one Zap split into different routes based on rules, so each type of record gets its own actions. Paths don't use tasks, but they do need a paid plan.
Paths add if this, then that logic to a Zap. Instead of one straight line of steps, the Zap splits into routes, and each route has its own rules and actions.
For example, a new enquiry could go down a ClickUp route if it mentions ClickUp, and down a recruitment route if it comes from an agency. A path group can hold up to 10 paths.
The Paths step itself doesn't use tasks. Only the actions on the routes that actually run do. Paths need a paid plan.
I use Paths when the same trigger needs different handling, like routing leads by service or by region. It keeps everything in one Zap the client can open and follow.
I keep Paths shallow and give every route a plain English name, like UK leads or ClickUp enquiries. When a Zap needs paths inside paths, that's usually a sign the process needs simplifying first.
Paid plan. Only the route that runs uses tasks.
The Paths step doesn't. Only the successful actions on the routes that run use tasks.
A path group can have up to 10 paths. I rarely need more than three or four.
A Filter is a yes or no gate. Use Paths when different records need different actions.
I set these up and train your team, in your own ClickUp or Zapier account.
Book a callContact Jack - jack@withtoki.co.uk