Zapier gives you two ways to handle conditional logic: filters and paths. They sound similar—both let you control what happens based on specific conditions—but they work differently, cost differently, and solve different problems.
If you’ve ever built a Zap that runs but does nothing, or one that burns through tasks faster than expected, you’ve probably picked the wrong tool for the job.
What filters do (and when they’re the right choice)
A filter is a checkpoint. It evaluates a condition and either lets the Zap continue or stops it immediately. If the condition isn’t met, the Zap ends—no further steps run, and Zapier counts it as a task used.
Filters work best when you want to exclude certain triggers from running the rest of your workflow. For example:
- Only send a Slack notification if a form submission includes “urgent” in the subject line
- Only add a contact to your CRM if their email domain isn’t gmail.com or yahoo.com
- Only log a new row in Google Sheets if the order total is above $100
The key trait: you’re saying “if this isn’t true, do nothing.” You’re not offering an alternative action—you’re just stopping early.
One non-obvious benefit: filters are psychologically clean. When you review a Zap history and see tasks that were filtered out, you know exactly why they didn’t proceed. There’s no ambiguity, no hidden branch you forgot about.
What paths do (and when you need them instead)
Paths let your Zap fork into multiple routes based on conditions. Each path can have its own set of actions, and Zapier will execute only the path whose conditions are met. If none match, the Zap can either stop or fall through to a default path.
Paths are the right tool when you want to route a trigger to different outcomes. For example:
- If a new subscriber chooses “weekly digest,” add them to MailerLite list A; if they choose “daily brief,” add them to list B
- If a support ticket is tagged “billing,” create a Stripe invoice; if it’s tagged “technical,” post to a dev Slack channel
- If a Typeform response selects “enterprise,” send to your CRM and notify sales; if it selects “self-serve,” send a welcome email via Postmark
The structure is “do X if A, do Y if B”—not “do X or do nothing.”
Paths count as one step in your Zap, but each action inside a path counts separately toward your task limit. If you have three paths and only one executes, you’re only billed for the actions in that path—not all three.
The mistake that burns tasks: using paths when a filter would do
Here’s the pattern I see most often: someone builds a Zap with two paths. Path A has five actions. Path B is empty, labeled “Do Nothing.”
That’s a filter dressed up as a path. And it’s wasteful.
Every time the Zap runs, Zapier evaluates the path logic—even if the result is to do nothing. You’re adding complexity and making your Zap history harder to read. Worse, if you later add actions to Path B “just in case,” you risk doubling your task usage without realizing it.
The fix: if one outcome is “do nothing,” use a filter instead. Reserve paths for workflows where every branch does something.
How they affect your task count (and your bill)
Both filters and paths count as tasks, but in different ways.
A filter counts as a task every time the Zap runs, even if the filter stops it. If 100 triggers come in and 90 are filtered out, you’ve used 100 tasks—because Zapier had to evaluate all of them.
A path counts as one task for the path step itself, plus one task for each action that runs inside the chosen path. If you have a three-path Zap and only one path executes two actions, you’ve used three tasks total (path evaluation + two actions).
This means paths can be more efficient if you’re routing high-volume triggers to different outcomes. But if you’re just trying to exclude certain triggers, a filter up front will keep your history cleaner—even if the task count is the same.
One rule of thumb that makes the decision easy
Ask yourself: if this condition isn’t met, should something else happen, or should nothing happen?
If the answer is “nothing,” use a filter.
If the answer is “something else,” use paths.
That’s it. You don’t need to overthink routing logic, task costs, or Zap readability. That one question will steer you to the right tool almost every time.
Got a Zapier workflow that’s burning tasks faster than expected? Subscribe to One Two Three Send and get one operator-focused automation breakdown every week—no fluff, no beginner tutorials, just the details that matter when you’re running a real business.