Asset 20 8 2
Does AI recommend your business? Run the free check →

Join 15,000 business owners, marketers and entrepreneurs. The Sunday newsletter you'll be annoyed only arrives once a week.

Article

How to Use Paths in Zapier: Branches, Rules and Fallbacks

In your Zap, click the plus sign to add an action, search for Paths and select it, and two branches, Path A and Path B, appear. Set rules on each branch using Custom rules, Always run or Fallback, add at least one action to every branch, test the rules and publish the Zap.

Branching instead of stopping

Paths let one Zap do different things depending on the data: if A happens, do X; if B happens, do Y. A Filter stops the Zap entirely for runs that don't match. Paths route each run to the right actions, so one Zap can handle several outcomes instead of you building a separate Zap for each.

A useful detail for anyone watching usage: Paths and Filter steps don't count toward task usage. Only the action steps inside a branch that runs use tasks.

Adding Paths to a Zap

  1. In the Zap outline, click the plus sign and search for Paths.
  2. Two branches, Path A and Path B, appear in one path group. Rename them from the menu next to the path rule so they're easy to read.
  3. Select Path rules for each branch and choose Custom rules, Always run or Fallback.
  4. For custom rules, set a Field, a Condition and a Value, and join several rules with and logic, or logic, or both.
  5. Click Continue to test the rules against sample data, then add at least one action to each branch.
  6. Add more branches or a nested Paths step if you need them, then publish the Zap.

The three rule types

Rule typeWhen the branch runs
Custom rulesWhen the field, condition and value rules are met
Always runOn every run
FallbackOnly if no other branch's rules are met

Only one branch per path group can be a Fallback, and Always run and Fallback can't both be used in the same group.

Limits worth knowing

  • Up to 10 branches in one path group.
  • Paths nested up to 3 levels deep.
  • One Fallback per path group.
  • At least one action in every branch.

Branches run in order, and can overlap

The Zapier Help Center makes two points that explain most surprising results. Branches run one at a time, left to right. If an earlier branch contains a Delay, later branches wait until it finishes, so a branch with a one-day delay on the left holds everything to its right for a day.

Second, if more than one branch's rules can match the same run, more than one branch will fire. A lead that's both from the UK and a returning customer could trigger both branches. Make the conditions mutually exclusive, or use a Fallback for the catch-all, so each run takes one route.

The update-or-create pattern

A common use is avoiding duplicates. Add a search step, say finding a contact in your CRM, and untick Create a new record if one is not found. Then add Paths: one branch where the search's Zap Data was found field is true, which updates the existing record, and one where it's false, which creates a new one. That's cleaner than letting every run create a record and tidying up later.

A worked example: routing new leads

Say a form feeds new enquiries into a Zap. Path A has a custom rule for enquiries where the field Service equals Consulting, and sends them to the senior consultant with a Slack message. Path B handles Service equals Training and adds them to a course list. A Fallback catches everything else and creates a general task, so no enquiry falls through a gap.

When rules aren't enough

Code by Zapier runs JavaScript inside a Zap, which is the alternative when your logic is too complex for Paths. n8n's If node splits a workflow based on comparisons, and its Switch node routes a workflow to one of several outputs. My comparison of n8n and Zapier covers when each tool suits, and if the branching is getting beyond you, here's how to hire an automation expert. For ideas on what to automate next, these business automation tips are a good start.

Work with me

Want AI doing the heavy lifting in your marketing?

I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.

My advice for your first path

Start with two branches and a Fallback, rename each so it says what it handles, and make the rules mutually exclusive. Keep Delays in the right-most branch so they don't hold up the others. Test with sample data for each branch before publishing, then check the Zap history after the first few real runs.

Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.

Frequently asked questions

What is the difference between Paths and Filter?

Filter stops the Zap for runs that don't match; Paths routes the data to different actions.

Do Paths use tasks?

Paths and Filter steps don't; actions inside a running branch do.

How many branches can a path group hold?

Up to 10.

What is a Fallback branch?

A branch that runs if no other branch's rules are met.

Can I nest Paths?

Yes, up to 3 levels.

Published and maintained by the Lilach Bullock team, covering marketing, AI and business growth.
Your buyers are asking AI who to use. Does it say you?

See for free whether ChatGPT, Claude, Perplexity, Gemini and Google name you, and get the plan to become the answer.

Check my AI visibility →
Sundays only

Get the Sunday newsletter.

One email a week. AI experiments, marketing tactics, and the workflows Lilach is building right now in her own business.

Subscribe free

Let’s get your marketing running on AI.

Book a free 30-minute call

We figure out what you need, where AI fits in, and what working together would look like.

Book the call →

Or take the 30-second calculator

You’ll see the hours and the money quietly leaking out of your week, and the three workflows worth building first.

Take the calculator →

Or grab the free AI resource library

Prompt packs, templates, checklists, and swipe files. The exact tools I build for paying clients. Yours, free.

Get the library →
Keep reading

More from the blog.