The Paths app lets you perform different actions in your Zap based on rules that you define. These rules determine whether the Zap will perform subsequent steps in the path. Paths use conditional logic: “If A happens in your trigger app, then do X. If B happens, then do Y.”

Paths terminology

• Path step: this is a starting point for using Paths in your Zap.
• Path branch: a single vertical column of action steps in one path that only run when the path rules are met.
• Path rules: the conditions that determine whether the path branch will run.
• Path group: a set of path branches at the same horizontal level.
• Nested path step: a path group nested within a path branch.

1. Add a Paths step to your Zap

• In the Zap outline, click the Action step or the plus sign + to add a new action. A dialog box will open.
• Search for and select Paths. Two path branches, “Path A” and “Path B”, will automatically be created in a single path group (a set of paths that are on the same level).

(Optional) Rename your path branch

• Click the three dot icon next to a path branch rule.

• A dropdown menu will appear. Select Rename.
• An input box will appear. Enter a name for the path branch.
• Click the checkmark icon to confirm the new path name.

2. Create path rules

Rules determine whether a path branch should run. To create path rules:

• In your path branch, select the Path rules. The right sidebar will open to the Rules setup & testing tab.
• Select the type of rule you want to use for your path branch:
  • Custom rules
  • Always run
  • Fallback

3. Test your path rule(s)

• Click Continue to test your path rule(s).

Zapier will test your path rules based on the sample data in the fields used in your rules. At the bottom of the Rules setup & testing tab, a message will tell you if your Zap would or would not have continued down the path branch.

4. Add actions to your path

Add actions to your path the same way you would add actions to your Zap. You must add at least one action to each path branch.

5. (Optional) Add more path branches

You can add up to 10 path branches within the same path group. Path branches all run at once as long as their rules are satisfied. They do not run sequentially or separately.

To add a path branch:

• Click the plus icon above the existing path branches.

• A new path branch will appear as “Path C”.
• Continue setting up your path rule(s) and action(s).

You can also copy and paste path branches or path groups.

6. (Optional) Add a nested Paths step

A nested Paths step lets you create up to 3 levels of path groups within a Zap. Path branches, including nested Paths steps, all run at once as long as their rules are satisfied. They do not run sequentially or separately.

To add a nested path step:

• Add a new action step where you want the new path to start.

• Select Paths as the app.
• A nested Paths step will appear, creating a single path group containing two path branches.

• Continue setting up your path rules and actions.

7. (Optional) Reposition path branches

You can reposition your path branches within a path group to organize your branching logic visually. Repositioning paths does not influence when the path branch will run.

To move a path branch:

• Hover to the left of the Path name. The icon will appear.

• Using the icon, drag the path branch into its new position.
• A pop-up message will appear to confirm the path branch has moved.

Additional info

How paths run

By default, path branches in Zaps created before June 30, 2025 use a feature called “parallel execution”. The Zap evaluates all path branch conditions at the same time to determine if the branch should continue running. All path branches run as soon as they pass evaluation, so the order of execution will depend on which path branches finishes evaluation first.

After June 30, you can opt into running path branches sequentially instead. This feature, “sequential execution”, evaluates and runs path branch conditions one by one in the order they appear in the Zap editor (left to right). This does not change the conditional logic of your Paths branches.

To opt in:

• Open your Zap in the Zap editor.
• In the left sidebar, select the Advanced settings icon .
• In the Path execution settings section, select Sequential execution

After September 30, 2025, sequential execution will become the only option.

Note

When you switch to sequential execution, Zaps may behave differently if:

• You have multiple path branches that run at the same time.
• A path branch uses apps like Delay, Code, Looping, Digest, or Sub-Zaps.
• You rely on when a step runs across different branches (not just if it runs).

If this impacts your workflows, you can:

• Change the order of path branches. Branches now run top to bottom, then left to right, so the order will impact when steps run.
• Move time-sensitive steps higher up in your path branch.
• Split your Zap into multiple Zaps using Sub-Zaps if you need steps to run in parallel.
• Combine steps into the same path branch.

Example

With sequential execution, if path A has a Delay step that delays for 1 day, and path B triggers a Slack message immediately, path B’s steps will be held until path A finishes. This could delay subsequent steps from running unless you reorder your paths.

Path limitations

• Each path group can have up to 10 path branches.
• Each Zap can have a maximum of 3 nested Path steps.
• Zaps are limited to 100 steps, including all steps within paths.
• You can only set up paths after adding a trigger to your Zap.
• Deleting a Paths step deletes all path groups within that step, including nested paths.
• Once you add a Paths step to your Zap, it must be the final step in your Zap.
  • If you add a Paths step before the last step in your Zap, any subsequent steps will automatically be shifted into “Path A” (the first path branch).
• If a path errors, subsequent paths will still run.