task usage, or Zapier task count
A task is one successful action step in a Zap. Triggers, Filters, Paths, Formatter and failed steps don't count, and your Zapier plan is priced on tasks.
A task is one successful action that a Zap carries out. Create a contact, that's a task. Send an email, that's another. Zapier's plans are priced on how many tasks you use each month, so this is the number that drives your bill.
Loads of things don't count. Triggers never use tasks, even when Zapier checks an app every couple of minutes. Filter, Paths and Formatter steps use no tasks either, though they need a paid plan. Nor do Delay, Looping, Digest and Storage, or steps for Zapier Tables and Zapier Forms. Steps that error, halt or never run don't count either, and nor does testing in the editor.
A few things count differently. Each successful Zapier MCP tool call uses 2 tasks. Code by Zapier uses 1 task per run, more if you extend its runtime. AI by Zapier depends on the model you pick.
On paid plans, when you hit your limit, Zapier switches you to pay-per-task billing unless you've turned it off. On Free, or if it's off, new Zap runs are held until your billing cycle resets, you upgrade or you turn pay-per-task on.
When I audit a Zapier account, the task count is usually the first place I find savings. The cheapest task is the one you don't use.
So I move checks into Filters and Paths, which never use tasks, so a Zap stops early instead of running three paid steps and then giving up. I swap AI steps for Formatter or Code wherever the job gives the same answer every time. And I look for Zaps that run on every update when they only need to run on one.
2 tasks per won deal. If the Filter stops a run, it costs nothing.
No. Zapier says trigger steps never use tasks, including all the checks a polling trigger makes in the background.
No. Filter and Paths steps don't count, and neither do Formatter, Delay, Looping, Digest, Storage, Zapier Tables or Zapier Forms steps. Filters, Paths and Formatter do need a paid plan, though.
No. Testing steps in the editor doesn't use tasks, even though testing an action really does the action in your app. So test with dummy data.
If pay-per-task billing is on, you carry on and pay for the extra tasks, up to three times your plan's limit. On Free, or if it's off, Zapier holds new runs until your billing cycle resets, you upgrade or you turn pay-per-task on, and you can replay them afterwards.
I set these up and train your team, in your own ClickUp or Zapier account.
Book a callContact Jack - jack@withtoki.co.uk