Sistava

Zapier Filters vs Paths: Build a Multi-Step Zap

How-to — — by Mahmoud Zalt

When to use a Zapier filter, when to use paths, the exact rule types available, the branch and nesting limits, and why neither one costs you a task.

Almost every Zap that survives contact with real data eventually needs logic. Not every form submission deserves a Slack message. Not every new deal should get the same follow-up. This is the point where a two-step Zap becomes a multi-step one.

Zapier gives you two tools for that logic and they are genuinely well designed. The trouble is that people reach for paths when a filter would do, and end up maintaining a branching diagram where one condition would have been enough.

What is the difference between a filter and paths?

A filter creates one set of conditions in a linear Zap and decides whether the steps after it run at all. Paths create several branched sets of conditions, each with its own steps, and Zapier's documentation is explicit that one, some, all, or none of the branches may run.

That last detail is the one people miss. Paths are not a switch statement where the first match wins. If two branches both qualify, both branches run. Zapier's Paths documentation states that branches are evaluated and run one by one in the order they appear in the editor, left to right.

FilterPaths
ShapeOne gate in a straight lineSeveral branches from one point
OutcomeContinue or stopOne, some, all, or none of the branches run
Use it whenYou only need one set of steps afterwardsYou need different steps for different cases
Task costDoes not count as a taskDoes not count as a task
PlanProfessional, Team, EnterpriseProfessional, Team, Enterprise

Both are listed on Zapier's paid plans, Professional and above, and neither is available on the Free plan. Zapier's pricing page as of 17 August 2026 also lists the Free plan as two-step workflows only, so multi-step logic is a paid-tier concept in both directions.

How do you add a filter to a Zap?

In the Zap editor you click the plus icon to add a step and choose Filter. Zapier's documentation notes you can add a filter at any point after the trigger, and you can use more than one filter in the same Zap.

The rule itself is three dropdowns in the Configure and test section: the field you want checked, the rule to apply, and the value to compare against. Add more conditions with the And option, or create an alternative set with an Or rule group where any single group passing is enough.

Adding and testing a filter

  1. Add the step — Click the plus icon in the editor and select Filter. Place it immediately after the step that produces the data you want to check.
  2. Pick the field — Choose the field from the previous step's output. If the field you want is not listed, your earlier test did not produce it, and you need to re-test with better sample data.
  3. Pick the rule — Rules are typed. Text rules work on text fields, number rules on numbers. Zapier's documentation notes that mismatching the rule to the data type is a common cause of a filter behaving oddly.
  4. Enter the value — Type a fixed value, or map a field if you are comparing two pieces of data from the run.
  5. Test it — Continue to run the test. Zapier shows a green tick when the sample passed and a yellow warning triangle when it did not, along with a note that the Zap would not have continued.
  6. Read the warning if there is one — Zapier's documentation notes that it flags a filter configured in a way that always passes. That warning almost always means the rule is not doing what you thought.

Which conditions can a filter actually check?

Zapier's filter and path rules documentation groups the conditions into five families. Knowing the list saves you from building a formatter step to do something a rule already does.

There is a genuine sharp edge with line items. Zapier's documentation states that when all your conditions are positive ones, at least one line item passing all of them lets the Zap continue. When the conditions are mixed or all negative, every line item must pass every condition.

How do paths work, and what are the limits?

You add paths the same way you add any step, by searching for Paths in the step picker. Zapier's documentation states that two branches, Path A and Path B, are created for you, and you then define rules and actions inside each.

The limits are the part worth memorising before you design anything ambitious, because hitting one halfway through a build means restructuring.

One structural point catches people out. Zapier's Paths documentation describes a paths group as the end of the workflow, with the subsequent actions living inside the branches rather than after them. If you need something to happen for every case regardless of branch, it goes before the paths group or gets repeated inside each branch.

The cost model, and why it favours branching

Zapier's task usage documentation states that filter steps and path steps do not count toward task usage, and that only action steps inside a running branch consume tasks. This is more generous than people assume.

The practical consequence is that filtering early is free money. A filter placed immediately after the trigger, before any action, means unqualified runs cost you nothing at all. Move the filter down below two actions and you have just paid for both on every run that was going to be discarded anyway.

A rule of thumb for choosing

Write the sentence out loud first. If it has the word only in it, you want a filter. Only tell me about deals over five thousand. Only file the PDFs.

If the sentence has an otherwise in it, you want paths. Enterprise leads go to the sales channel, otherwise they go into the nurture list. If it has several otherwises, you still want paths, but check the ten branch ceiling before you commit to the design.

Zapier's logic tools are one of the strongest parts of the product. They are cheap to run, clearly documented, and predictable in a way that matters when money moves through them. The discipline is keeping the diagram small enough that the person who inherits it can still read it.

FAQ

Do Zapier filters and paths use tasks?

No. Zapier's task usage documentation states that filter steps and paths steps do not count toward task usage. Only action steps that run successfully count, which for paths means only the actions inside a branch that actually executes.

Are filters available on the Zapier free plan?

Zapier's conditional logic documentation lists both filters and paths as available on the Professional, Team, and Enterprise plans, and not on the Free plan. Their pricing page as of 17 August 2026 also lists the Free plan as two-step workflows only.

Can more than one path branch run at the same time?

Yes. Zapier's documentation states that one, some, all, or none of the branches may run, and that branches are evaluated in the order they appear in the editor from left to right. If your data satisfies two branches, both execute, so write rules that are mutually exclusive when you want only one outcome.

How many branches can a Zapier path have?

Zapier's Paths documentation states a maximum of 10 branches in a single path group, and that paths can be nested up to three levels deep. The overall Zap limit of 100 steps includes every step inside every branch.

Why does my filter pass when it should not?

The two usual causes are a rule applied to the wrong data type, for example a text rule on a number field, and a rule that is technically always true. Zapier's documentation notes it displays a warning when a filter is configured to always pass, so read the editor carefully before you turn the Zap on.

Should I use a filter or just add conditions in the app itself?

If the source app can filter for you, let it. A Gmail label rule or a form's own conditional logic runs on their side, costs you nothing, and keeps your Zap simpler. Use a Zapier filter when the condition depends on data the source app does not know about.

Sources