vcusers.org

Home / Guides / Zapier pricing explained

PRICING

How Zapier pricing actually works

A Zapier task is one action step that runs, not one Zap and not one automation. Misunderstanding that unit is the single most common reason people hit their plan's limit earlier than they expected to.

The unit: one task, one completed action step

Every time a Zap's action step successfully runs, that's one task. A Zap with a single trigger and a single action, say, "new form response creates a row in a spreadsheet," uses one task per run. A Zap with a trigger and three chained actions, "new form response creates a spreadsheet row, sends a Slack message, and adds a CRM contact," uses three tasks per run, because three action steps completed.

The trigger itself, the part that checks whether something new happened, doesn't cost a task. Only completed action steps do. A failed step also doesn't cost a task, since it never finished.

Estimating real usage before you commit to a plan

Multiply action steps per Zap by expected runs per month, then sum across every active Zap. A three-step Zap that fires 500 times a month is 1,500 tasks on its own, already past the free plan's 100-task ceiling and most of the way through the 750-task entry paid tier.

Free100 tasks/mo, single-step Zaps only
Professional, entry750 tasks/mo
Team, entry2,000 tasks/mo

What happens at the limit

By default, Zapier holds the runs rather than either blocking them outright or silently overcharging you: task-limited Zap runs pause and sit in your Zap history, replayable once you have tasks available again. Nothing is lost, but a workflow that depends on running in real time, an urgent Slack alert, a time-sensitive CRM update, effectively stops working until you free up capacity or upgrade. If you'd rather automations keep running past the limit, pay-per-task billing is available as an opt-in, charged at a markup over your plan's included rate. Check task usage partway through the first billing cycle on any new plan, rather than finding out at the point something stops firing.

Annual vs monthly billing

Annual billing runs about 33% cheaper per month than the equivalent monthly plan, a larger gap than most SaaS products offer for prepaying a year. For a workflow you're confident is staying in production, annual billing is close to a default-yes; for something still being tested and might get replaced, monthly avoids locking in a plan you outgrow or abandon.

The most expensive mistake isn't picking the wrong tier, it's building a Zap with more action steps than the job needs. Combining two simple filter-and-format steps into one code step, where the platform allows it, can meaningfully cut task consumption on high-volume Zaps.

Frequently asked

Do failed Zap runs count as tasks?

No. Zapier only bills for steps that complete successfully. A step that errors out before finishing doesn't consume a task, though the trigger check itself is free regardless of outcome.

What happens if I go over my task limit?

By default, Zapier holds the runs rather than losing them: they pause and stay in your Zap history, replayable once you have tasks available again. Pay-per-task billing is available as an opt-in if you'd rather automations keep running past the limit.

Is annual billing actually cheaper?

Yes, meaningfully. Annual billing runs roughly 33% cheaper per month than paying monthly at the same tier, which is a bigger discount than most SaaS annual plans offer.

Sources