Add branching logic to Zaps with paths

Available on plans:





Paths let you build advanced workflows to perform different actions based on different conditions. Paths use conditional, if/then logic: if A happens in your trigger app, then do X. If B happens, then do Y, and so on.

With each path, you set up rules and decide which actions should occur when those rules are met. 


Path limitations

  • You can add up to 10 paths in your Zap, and up to 3 nested paths. 
  • Zaps are limited to 100 steps, including all steps within paths.
  • You can only set up paths after adding a trigger to your Zap, and paths must be the final step of your Zap.


1. Add a path to your Zap

  • In the Zap editor, ensure you’ve set up your trigger and any necessary action steps. Paths must be the final step in a Zap.
  • Click plus icon to add a step.
  • Search for and select Paths. Two paths, A and B, will automatically be created in a single path group (a group of paths on the same level).Screenshot Zap editor with paths.png
  • Click three dot icon next to Path A.
  • A field for entering the path's name will appear. Enter a descriptive name for your first path to easily identify it later.Screenshot in the Zap editor of how to rename a path.png
  • Click form check icon to confirm the new path name.


2. Set your path rule(s)

  • Click Path rules.

In the Rules section, set the rule(s) for your path using the three dropdown menus. Each path rule requires three pieces of information:

  1. Field: in the first dropdown menu, select a field to base the rule on.
  2. Rule: in the second dropdown menu, select the rule for the field. Learn more about different rule types.
  3. Value: in the third dropdown menu, enter the specific value the rule must meet.

Screenshot of setting up Path rules in the Zap editor.png

There are two types of logic for multiple path rules:

  • AND logic: to identify data that meets all the path rules, click the plus icon button.
  • OR logic: to identify data that meets at least one path rule, click the plus icon button.

  Learn more about the difference between AND and OR.

ratingStar icon Tip

To implement if/else logic, you can set the rules for two paths with opposite conditions. For example, in Path A: if the email address exists, and in Path B: if the email address does not exist.

When you’re done setting up your rules, click Continue.


3. Test your path rule(s)

In the Rules setup & testing section, Zapier will test your path rules based on your sample data. A message will inform you if your Zap would or would not have continued down this path based on the sample data.

If the data the Zap checks matches multiple paths, all matching paths will be used.

Screenshot of Zap editor showing a Path rule being tested.png

When you're done reviewing your test, click Continue.


4. Add actions to your path

Add actions to your path the same way you would add actions to a regular Zap. You must add at least one action to a path before creating another path.

When you’re done setting up your action(s), click X in the top right-hand corner to close the right sidebar controls. This will allow you to proceed with setting up Path B by repeating the steps outlined above.


5. (Optional) Add more paths to your Zap

You can add up to 10 paths in your Zap, and up to 3 nested paths (paths within a path). If you want the same actions to occur for each path at the end of your Zap, add the actions to each path.

To add a path:

  • Click plus iconto the right of Path B.
  • To set up your paths, repeat the steps above.

screenshot of Zap editor showing two Paths within a Zap.png

To add a nested path:

  • Within a path, after your last action, click plus icon
  • Search for and select Paths. Two nested paths, A and B, will automatically be created in a single path group.
  • Repeat the steps above for setting up your path(s).

Screenshot of the Zap editor showing nested Paths.png

When you’re done setting up all your paths, turn on your Zap.


If you need to use conditional logic to create an alternative workflow to handle any errors that occur in your Zap, use custom error handling instead of Paths.

Was this article helpful?
20 out of 36 found this helpful