Zapier costs climb with tasks: where they go, how to cut them

Zapier bills one task for every action that runs successfully, and the price of a task depends on how many you buy. So a bill grows in two ways at once. Your Zaps quietly do more actions than you think, and small accounts pay the most for each one. Both are visible in Zapier’s own pricing and help pages, which we read on October 22, 2026.

The quiet multipliers are specific. An action after a loop runs once per item, and a form with no filter pays for its spam. An AI step on the default tier costs 5 tasks, plus 5 per tool call. We priced every Professional tier with a short script, then counted three hypothetical Zaps before and after one change each, using only Zapier’s documented rules.

Small accounts pay the most per task

Zapier’s pricing page sells Professional in tiers of tasks a month. The base price falls steeply per task as the tier grows, so the first tasks are the dearest.

Tasks a month	Pro, billed yearly	Per 1,000 tasks	Pro, billed monthly	Per 1,000 tasks
750	$19.99	$26.65	$29.99	$39.99
1,500	$39.00	$26.00	$58.50	$39.00
2,000	$49.00	$24.50	$73.50	$36.75
5,000	$89.00	$17.80	$133.50	$26.70
10,000	$129.00	$12.90	$193.50	$19.35
20,000	$189.00	$9.45	$283.50	$14.18
50,000	$289.00	$5.78	$433.50	$8.67
100,000	$489.00	$4.89	$733.50	$7.33
200,000	$769.00	$3.84	$1,149.00	$5.75

Prices in US dollars per month, read October 22, 2026. The per-1,000 columns are our arithmetic. Tiers above 200,000 tasks, Team (from $69 a month yearly for 2,000 tasks) and Enterprise are on the same page.

Two rules on that page change how the table reads. “Self-serve (Free, Pro, Team): task allowance resets monthly, even on an annual subscription,” so a quiet month does not bank tasks for a busy one. And the Free plan gives 100 tasks with “two-step” Zaps only, one trigger and one action, so any Zap with a second action needs a paid plan.

Going over the limit costs 1.25 or 2.5 times the base rate

When you use up your tier, pay-per-task billing takes over if it is on. Zapier’s page sets the overage at “1.25× base rate” on yearly plans and “2.5× base rate” on monthly ones. Pay-per-task, it says, “costs about 3× more on a monthly plan than on an annual one”. It stops at a ceiling: “usage stops once it reaches 3× your task subscription, until the next cycle.”

The help article on pay-per-task (updated August 15, 2026) says it is on by default for accounts that joined after January 2024. Only the account owner can turn it off on Professional and Team. With it off, new runs are held until the cycle resets, per Zapier’s task usage article.

Zapier publishes no dollar rate; the help article says it “depends on your plan and billing cycle type”. Our script assumes the base rate is the tier price divided by its tasks, so treat the overage figures below as estimates and check your own Billing settings. With that assumption, here is the cheapest Professional option for a given monthly count:

Tasks needed	Cheapest, billed yearly	Cheapest, billed monthly
3,000	2,000 tier + 1,000 overage: $79.63	5,000 tier: $133.50
6,000	5,000 tier + 1,000 overage: $111.25	10,000 tier: $193.50
12,000	10,000 tier + 2,000 overage: $161.25	20,000 tier: $283.50
25,000	20,000 tier + 5,000 overage: $248.06	50,000 tier: $433.50
40,000	50,000 tier: $289.00	50,000 tier: $433.50

The pattern: on yearly billing a little overage usually beats the next tier, while on monthly billing the 2.5 times rate makes the upgrade cheaper in every row above. In our script, monthly overage stayed cheaper only while it was small: 500 tasks over the 2,000 tier, but not 1,000.

What counts as a task, and what does not

Zapier’s rule is short: “Only successful actions count toward your task usage,” says its task usage article (updated August 21, 2026). The pricing page lists what is free:

Free: triggers and polling; Formatter, Paths, Filter, Delay, Looping, Digest, Zapier Manager, Storage, Tables and Forms; actions that error or halt; steps a filter or path skips.
1 task: each successful action, and a Code by Zapier step within its included runtime (30 seconds a step on Pro). Past that, each extra 30-second block costs another task.
1 task or none: a search step set to carry on when it finds nothing uses 1 task; one set to stop uses none.
More than 1: AI steps, priced by model tier, and MCP calls, where the pricing page’s example is “one MCP tool call is 2 tasks”. MCP and Zaps draw on the same pool.
Again on replay: replaying a whole Zap run counts each previously successful step that runs again as 1 task.

Sub-Zaps are the one conflict we found. The pricing page lists Sub-Zap among the built-in tools that use no tasks. The task usage article counts “The Call a Sub-Zap action step” and “The Return From a Sub-Zap action step” as tasks, as well as each action inside the sub-Zap. If you lean on sub-Zaps, check a run in your Zap history before you plan around either answer.

Zapier Agents sit outside all this. The pricing page bills them in “activities, not tasks”, with 1,500 a month on Pro.

Loops multiply every action after them

Looping by Zapier is free itself, but “each action step after the loop uses 1 task for each loop that runs”, up to 500 iterations. An order with six line items, followed by two actions, costs 12 tasks.

Zapier’s own looping guide gives the fix. Put any step that should run once before the loop, “if possible”. If it has to come after, add a filter that passes only on the last iteration. Then, per the guide, “Any action step after the filter runs once in the last loop and uses only 1 task.”

AI steps now cost up to 5 tasks, plus tool calls

Since June 15, 2026, AI by Zapier steps are priced by model tier: Standard 1 task, Advanced 3, Premium 5, and your own AI account 1. The tier pricing article, updated October 1, 2026, has the formula: “Tasks used per run = (1 × model rate) + (number of tool calls × model rate).” Its example, a Premium step with two tool calls, uses 15 tasks.

The default matters most. The same article says “New AI by Zapier steps default to the Premium (5x) tier, so expect higher task usage unless you choose a lower tier.” Zapier’s June announcement, updated August 12, said Advanced. We take the newer page as current, and either way the default is not the cheapest tier.

Standard covers models such as GPT-5 mini and Gemini 2.5 Flash; Premium covers GPT-5 and Claude Sonnet and Opus models. A step pauses for approval if a run reaches its task limit, 75 by default and up to 500.

Three fixes, counted

We wrote a 64-line Node.js script with the price list above and Zapier’s counting rules. The three Zaps below are hypothetical: the run counts are ours, every rule behind the task counts is Zapier’s. We ran the script on Node.js 22 on October 22, 2026. This is its output:

A. Order to sheet, per line item (400 runs): 4800 -> 2800 tasks
   before: loop 6 items -> add row + Slack each
   after:  loop 6 items -> add row; filter on last iteration, then one Slack
B. Email triage with AI (600 runs): 9600 -> 1200 tasks
   before: AI step Premium (5x), 2 tool calls + 1 action
   after:  AI step Standard (1x), no tools + 1 action
C. Form leads, 30% spam (1000 runs): 3000 -> 2100 tasks
   before: CRM + sheet + Slack, no filter
   after:  filter drops spam first, then 3 actions
Total: 17400 -> 6100 tasks a month
Cheapest yearly Pro: $189.00 (20000) -> $113.47 (5000 +1100 PPT)

The AI step is the biggest lever by far: 16 tasks a run fall to 2. Together the three changes cut the hypothetical account from the 20,000 tier at $189 a month to the 5,000 tier plus an estimated $24.47 of overage. The core of the pricing logic is short:

// Cheapest way to cover `need` tasks: a tier alone, or a smaller tier plus pay-per-task.
function cheapest(need, billing) {
  const col = billing === 'yearly' ? 1 : 2;
  let best = null;
  for (const row of PRO) {
    const [t] = row, price = row[col];
    if (need > t * CAP) continue;           // past the pause ceiling: runs stop
    const extra = Math.max(0, need - t);
    const cost = price + extra * (price / t) * PPT[billing];
    if (!best || cost < best.cost) best = { tier: t, extra, cost };
  }
  return best; // null when even the largest tier at 3x cannot cover it
}

Each fix has a cost of its own

None of these is free of trade-offs, and some are wrong for some Zaps.

A cheaper AI tier can do worse work. Zapier sells Premium as the tier with the “best performance for complex tool workflows”. Test the Standard tier on a week of real inputs before you switch, and keep Premium where a wrong answer costs more than the tasks.
A filter only saves if it runs first. Put it after the CRM step and you still pay for every spam lead there. A filter that is too strict drops real leads without an error, so test it on a batch of real entries.
Batching delays the work. Digest by Zapier collects entries and releases them daily, weekly, monthly or at a set count, and its steps use no tasks. That suits a summary to Slack, not an alert someone needs now. A digest holds at most 1 MB.
Replays cost tasks again. Replaying a whole run to fix one failed step re-bills every step that had already worked.
Turning off pay-per-task trades money for missed runs. New runs are held until the cycle resets or you upgrade.

What this means for you

The decision is which Zap to fix first, and Zapier shows you. In Zap history, select the Task usage tab. It shows the current billing period by default and lists up to 100 Zaps, “sorted by Tasks used (highest first)”. For the account total, MCP included, the Usage Insights tab on the Billing page shows billable tasks by product type; owners and admins can see it.

Then work down the top three Zaps:

Check every AI by Zapier step’s tier. Note its tool calls; each one costs the tier rate again.
Move filters to the top, right after the trigger, so rejected runs cost nothing.
Look for loops. Move once-only actions before the loop, or add the last-iteration filter.
Batch what can wait with Digest.
Match the billing to the pattern. Yearly with some overage is usually cheapest; a monthly plan that goes over by more than a few hundred tasks should move up a tier.

If your workflows are long and busy, another tool may be cheaper outright. Our Zapier, Make and n8n comparison prices one workflow on all three, and Power Automate against Zapier does the sums for Microsoft 365 offices. To decide whether a Zap earns its tasks at all, use the payback formula. More is under automation.

Start with the first row of that Task usage tab. It is the Zap where any of these fixes saves the most.

How we made this

We read Zapier’s pricing page and nine Zapier help center articles on October 22, 2026, and noted where two of them disagree (sub-Zaps, and the default AI tier). We wrote a 64-line Node.js script and ran it on Node.js 22 that day. It computes the per-task prices, the cheapest tier or overage mix, and the task counts for three hypothetical Zaps. The overage figures assume Zapier’s base rate is tier price divided by tasks, because Zapier publishes no dollar rate. We have no paid Zapier account, so we did not build these Zaps or check a real invoice.

Sources

Zapier, Plans and pricing (tiers, pay-per-task multiples and ceiling, what counts, monthly reset; read October 22, 2026)
Zapier Help Center, How is task usage measured in Zapier? (updated August 21, 2026)
Zapier Help Center, How pay-per-task billing works in Zapier (updated August 15, 2026)
Zapier Help Center, Understanding Looping by Zapier and Loop your Zap actions (updated May 29, 2026)
Zapier Help Center, AI by Zapier model tier pricing (updated October 1, 2026) and AI by Zapier new model-based pricing starting June 15, 2026 (updated August 12, 2026)
Zapier Help Center, Compile data in a digest in Zap workflows (updated July 24, 2026)
Zapier Help Center, Where to review your task usage in Zapier (updated October 12, 2026)
Zapier Help Center, View and manage your Zap history (updated June 15, 2026)
28creation script, October 22, 2026: 64 lines of Node.js, run on Node.js 22.22.0, prices and rules from the pages above

Zapier costs climb with tasks: where they go, how to cut them

The short read

What you can do with this