Zapier Cost Calculator

How Zapier Task Pricing Works

Zapier bills per task, and a task is one action step that successfully runs. That definition does more work than it looks like it does.

The trigger is free. A Zap that fires 1,000 times a month with three action steps uses 3,000 tasks, not 4,000.

A Zap that stops early costs less. If a Filter step halts the run, the actions after it never execute and never count. This is the single most useful thing to know about the pricing model, and it is why filter placement matters so much.

Some built-in steps do not count. Filter and Paths are free. Formatter historically has been too. Vendors change these rules, so treat this as the shape of the model rather than a guarantee, and check Zapier's own note on how task usage is measured against the current plans and pricing before you build a strategy on it.

Failed steps generally do not count, but retries do. A step that errors and is retried can consume a task on each attempt.

What Changed Recently

Zapier retired the Starter plan name, so any article or calculator still comparing "Free, Starter, Professional, Team" is out of date and the numbers beside those names should not be trusted. The free tier runs two-step Zaps at a small monthly task allowance, and the cheapest paid tier is now Professional, which unlocks multi-step Zaps, paths and premium apps.

Prices differ between monthly and annual billing, differ again by region and currency, and usage above your included tasks is billed at an overage rate rather than simply stopping. Take the task figure from this calculator to Zapier's own pricing page and read it against today's tiers. Any fixed price printed here would be wrong within a quarter.

A Worked Example

A small agency runs four Zaps:

• New lead from a web form to CRM plus Slack. Two actions, fires 300 times a month → 600 tasks.
• Invoice paid to accounting plus a client email. Two actions, 80 times a month → 160 tasks.
• Daily report pulling rows and posting a summary. Three actions, 30 times a month → 90 tasks.
• Every new email in a shared inbox creating a task, filtered to just one sender. One action, but the trigger fires 2,000 times a month and the filter passes 90 of them → 90 tasks.

Total: 940 tasks a month.

That last Zap is the interesting one. It fires more than twice as often as everything else combined and costs less than any of them, purely because the filter sits immediately after the trigger. Move that filter to the end and it would still be 90 tasks in that particular Zap, but add a second action before the filter and the same Zap suddenly costs 2,090. Filter first, act second.

Four Ways People Overspend

Dormant Zaps. Zaps built for a campaign that ended, or for a tool nobody uses any more, keep firing and keep billing. Sort your Zap list by task usage rather than by name and the dead weight becomes obvious immediately.

Filters placed too late. Every action before the filter runs for every trigger, including the ones you were about to discard.

Polling triggers on noisy sources. A Zap watching a busy inbox or a frequently edited spreadsheet fires constantly. Where the app offers an instant webhook trigger instead of polling, use it — it is more responsive and it fires only on the events you care about.

Multi-step Zaps that should be one. Three separate update steps against the same record is three tasks. One update carrying all three fields is one.

When to Consider Alternatives

Zapier is excellent at simple, reliable connections between popular apps, and the breadth of its app directory is genuinely hard to match. It becomes the wrong tool when:

• You need real logic. Loops, proper branching, iterators and error handling are where Make.com is stronger, and its billing unit behaves differently enough that the comparison is worth running properly rather than assuming.
• Volume is the problem rather than complexity. Self-hosted n8n moves the cost from per-task to per-server, which changes the economics completely once you are into tens of thousands of runs. n8n Self-Hosted Setup covers what that actually involves, including the parts that are not free.
• You are mostly moving webhooks around and transforming them. A lighter-weight webhook platform will do it for less.

Zapier Alternatives and the No-Code Tool Comparison Matrix go through the trade-offs in more detail.

Frequently Asked Questions

Does a Zap that fails still use a task?

A step that errors outright generally does not consume a task, but each retry attempt can. The practical risk is a Zap failing repeatedly against an API that is down, which burns tasks without ever completing. Set up Zapier's error notifications so a persistently failing Zap reaches you rather than quietly running up usage.

What happens when I run out of tasks?

You are billed for the overage rather than being cut off, which is friendlier than a hard stop but easier to overlook. Check your usage against your allowance mid-month rather than discovering it on the invoice, and set a reminder if your volume is seasonal.

Do Filter and Formatter steps count as tasks?

Filter and Paths do not. Formatter has historically not counted either. Zapier does change these rules, so confirm against their current documentation before designing around it — the cost of being wrong is a bill built on an assumption that expired.

Is annual billing worth it?

Only if your volume is stable. Annual billing is meaningfully cheaper per month, but it commits you to a tier, and automation usage tends to grow in steps rather than smoothly. If you are still adding Zaps every few weeks, stay monthly until the shape of your usage settles.

Audit Your Automation Stack

Dormant Zaps and late filters are the two problems almost every account has, and both are quick to fix once you can see them. Book a session for a full automation stack audit, or take the work on through Fiverr.