Sistava

Zapier Tasks: What Counts, What Does Not, and Why

How-to — — by Mahmoud Zalt

Exactly which Zapier steps consume a task, which are free, how pay-per-task billing and its cap work, and the practical ways to cut your usage.

Nearly everyone's first surprise Zapier bill comes from the same misunderstanding. People count workflows and assume that is what they are paying for. Zapier counts completed actions, and a busy workflow contains several.

The good news is that Zapier documents this properly, and once you know the free list you can restructure a Zap to cost half as much without losing anything. Here is the whole model, the pay-per-task safety net, and the specific moves that reduce usage.

What exactly counts as a task?

Zapier's task usage documentation states that an action step uses one task per successful run. That is the base rule, and everything else is either an exception to it or a product with its own rate.

Step or productTasks used
A standard action step1 per successful run
An error handler step1 per successful run
Code by Zapier, standard runtime1 per run, more with extended runtime
AI by ZapierVaries by the model tier you select
Zapier MCP2 per successful tool call
Zapier Lead Router5 per successful lead routed
A search action set to proceed if nothing is found1
A search action set to stop if nothing is found0

That last pair is a genuinely useful detail. Zapier's documentation states a search step only costs a task when it is configured to carry on when nothing was found. If your search should halt the run on a miss, it is free.

Sub-Zaps are the opposite kind of surprise. Zapier's documentation states that each action inside the sub-Zap costs a task, and so do the call step and the return step. A sub-Zap with two actions is four tasks, not two.

Which steps are free?

This list is where the savings live, and most people have never read it. Zapier's task usage documentation states that none of the following consume a task.

One caveat on replays. Zapier's documentation states that when you replay a Zap run, previously successful steps that run again count again. A bulk replay after an outage can be an expensive click, so check how many runs are queued before you press it.

What happens when you run out of tasks?

Zapier does not simply switch you off. Their pay-per-task documentation states that once you pass your plan's task limit within a billing cycle, pay-per-task billing takes over so workflows keep running, and you are charged for the extra.

There is a ceiling on that. Zapier's documentation states the maximum is three times your plan's task limit, counting both your plan allocation and the pay-per-task usage. Their own worked example is a Professional plan with 750 tasks, which allows 750 included plus 1,500 paid, for 2,250 in total.

Reach that ceiling and Zapier's documentation states that Zap workflows stop running. Their task usage documentation separately notes that held runs do not consume tasks while they wait, and can be replayed once your billing period resets or your plan is upgraded.

How do you actually reduce task usage?

Every technique below follows from the free list. None of them require giving anything up, which is why they are worth doing before you consider a bigger plan.

Six ways to cut your task count

  1. Move every filter as early as it can go — Filters are free. Put them directly after the trigger so discarded runs never touch a paid step.
  2. Filter in the source app where you can — A Gmail label rule or a form's own conditional logic runs on their side entirely. Zapier then only sees the records that already qualify.
  3. Set searches to stop when nothing is found — Zapier's documentation states a search costs a task only when configured to continue on an empty result. If halting is the correct behaviour anyway, you get it free.
  4. Use Digest instead of one message per event — Digest steps are on the free list, and a single daily summary action replaces one action per event. This is the biggest saving available on high-volume notification Zaps.
  5. Reach for Formatter, Delay, and Looping without fear — All three are free. Reshaping data inside Zapier costs nothing, so there is no reason to push formatting work into a paid action step.
  6. Audit before you replay — Replayed steps count again. After an outage, look at how many runs are held and whether you actually need all of them before triggering a bulk replay.

One more structural point. Zapier's Zap limits documentation states a maximum of 100 steps per Zap, including every step inside every path branch, and a lower cap of 30 steps during a free trial. Long before you hit that, a Zap with dozens of paid actions is worth splitting or rethinking rather than growing.

What the plans actually cost

Zapier's pricing page as of 17 August 2026 lists the Free plan at 100 tasks per month with a 15 minute polling time. Professional and Team are priced on sliding task volume, and the page showed Professional starting at $19.99 per month billed annually or $29.99 billed monthly, and Team starting at $69.00 billed annually or $103.50 monthly, all in US dollars.

Those numbers move, so treat them as a shape rather than a quote and read the current page before you commit. The shape that matters is that you pay for volume, and volume is measured in successful actions.

Where to check your usage

Zapier surfaces task usage on its task usage page and in Zap History. History is the more useful of the two when you are hunting for a leak, because it shows which Zap ran how often rather than just a total.

The usual culprit is not the workflow you were worried about. It is a small helper Zap you built six months ago, pointed at something that got busier, running quietly all month. Sort by run count and it will be near the top.

Zapier's billing model is one of the more transparent ones in software, and the documentation behind it is unusually complete. Spend twenty minutes with the free list and you will get more out of your plan than most people on the tier above.

FAQ

How many tasks does one Zap use?

As many as it has successful action steps. Zapier's task usage documentation states that an action step uses one task per successful run, while trigger, filter, and paths steps do not count. So a trigger with three actions behind it uses three tasks each time it runs.

Do failed Zap runs use tasks?

No. Zapier's documentation states that action steps which error or halt do not count, and neither do steps that never ran because a filter stopped the workflow, a path did not match, or an earlier step failed. You are billed for successful actions only.

What happens when I hit my Zapier task limit?

Pay-per-task billing takes over so workflows keep running, and you are charged for the extra. Zapier's documentation states a cap of three times your plan's task limit, counting the plan allocation and the paid usage together, and that workflows stop running once that maximum is reached.

Do filters and paths cost tasks in Zapier?

No. Zapier's task usage documentation lists filter and paths steps as not counting toward task usage. Only the action steps inside a branch that actually runs are charged, which is why placing filters early in a Zap is the cheapest optimisation available.

Do Zapier Agents use my tasks?

No. Zapier's task usage documentation lists Zapier Agents as running on a separate quota. Agents consume activities measured against your agents plan, while Zap runs consume tasks measured against your Zapier plan.

Does replaying a Zap run cost me again?

Yes. Zapier's documentation states that when a Zap run is replayed, previously successful steps that run again count as new tasks. Held runs waiting to be replayed do not consume tasks while they wait, and can be replayed once your billing period resets or you upgrade.

Sources