Zapier Pricing in 2026: What You Actually Pay for Tasks

The 2026 Zapier pricing plans, verified

Every figure in this section was read directly off zapier.com/pricing in September 2026, in USD. One detail on that page does most of the damage: it loads with Pay yearly (Save 33%) already switched on. That default is why half the internet quotes you a price you will never see on a monthly invoice.

Zapier's plan ladder, verified September 2026. The task slider runs 100, 2K, 10K, 100K, 1M and 2M tasks, and the price moves with it, which is why Professional and Team say "starting from".

Read that ladder the way a buyer actually experiences it: four tiers, two billing toggles, eight prices for one product, and exactly one of them is the number that will land on your card. The billing toggle is not a footnote. It is the single question that decides whether you are reading a real quote or a marketing figure.

The Zapier free plan is more capable than its reputation suggests. It includes 100 tasks a month and it runs two-step Zaps, meaning one trigger plus one action per run. Two-step is what the page says, and it is worth stating plainly because several third-party guides still call it single-step. Filters and Paths, which are conditional logic, are not part of it: both are paid-plan features, which is why branching has no home inside a two-step Zap. Free also polls every 15 minutes, and that polling interval becomes a billing story of its own below.

Professional unbundles the parts that make automation useful: multi-step Zaps, unlimited premium apps, webhooks, AI fields, and a two-minute polling floor. Team adds shared Zaps and folders, shared app connections, SAML SSO, 25 users, priority support, and a base allowance of 2,000 tasks. Enterprise hides the price behind a sales call and is the only tier with annual task limits, advanced admin controls, analytics, and an assigned technical account manager. Every account also gets a 14-day Professional trial with no credit card.

Why third-party pages quote three different Professional prices

The $19.99 versus $29.99 argument is not a correction waiting to happen. It is the same plan, quoted from two different toggles, by writers who never said which one they clicked.

The first four rows are not wrong. Each is a real price for a real product, quoted without its billing toggle, and without its task allowance. That is the whole mechanism: an unlabeled toggle plus an unstated task tier produces a shelf that looks like it is contradicting itself, and a reader who tries to reconcile the numbers by force assumes somebody is lying. Nobody is. The last three rows are a different problem, because they are genuinely stale or genuinely muddled, and they are the ones to discard.

There is a second thing Zapier does not publish in quotable form: the price at 5K, 10K or 50K tasks. The slider moves and the number moves with it, but the page never gives you a stable figure to cite. So when an article hands you a precise monthly price at 50,000 tasks, treat it as a single screenshot someone read once, not a rate you can hold Zapier to. The arithmetic in the next section stays deliberately at the published base tiers, where every number is checkable.

Task math: the number that decides your Zapier bill

Here is the arithmetic almost nobody runs before they commit.

A task is charged when a Zap successfully moves data or completes an action, and each successful action counts separately. Triggers do not count. Polling does not count. Failed actions do not count. Filters, Paths and Formatter do not count. That sounds generous until you count actions instead of the steps you drew on the canvas.

Take one ordinary workflow. A lead arrives, gets enriched, gets written to your CRM, triggers a Slack notification, and queues a follow-up email. That is five steps, which in billing terms is one trigger plus four actions:

• One run = 4 tasks (the trigger is free)
• 20 runs a day = 600 runs a month = 2,400 tasks per month
• Professional's base allowance is 750 tasks
• Team's base allowance is 2,000 tasks

One routine Zap, running twenty times a day, is 3.2 times the entire Professional base allowance and already past the Team baseline. On a plan advertised at $19.99, a single lead-routing workflow has outgrown both entry tiers before you built the second one.

Put it in cost per task and the headline gets flatter still. At the published entry tiers:

None of this is dishonest. It is metering, and metering is how the product is priced. But the $19.99 headline assumes a workflow far smaller than the one you intended to build, and it assumes you spend your allowance exactly. nocode.mba, the freshest explainer on the shelf, arrives at the same conclusion from the other direction: "real teams typically land between $50 and $200 per month."

Now the trap. Polling is free. The consequence of polling is not. Free checks for new data every 15 minutes, Professional every 2 minutes, Team every minute. When a workflow watches a busy source on a slow interval, records arrive in a pile rather than a trickle. Two hundred new rows in one poll window, pushed through a three-action Zap, is 600 tasks in a single burst. One import can consume six months of the Free allowance in a few minutes, and you did nothing except receive data you asked for.

Where your Zapier cost actually explodes

The most quoted line about Zapier pricing is not on zapier.com. It is a forum post. A practitioner in r/automation: "What started as $10 per month has now jumped to over $750 for basic automations."

That is not a pricing-page failure. It is four specific mechanics stacking on each other, and each one is boring on its own.

Multi-step chains. Every step you add is another task on every run, permanently. The step you added for convenience six months ago is now 600 tasks a month, and nobody remembers adding it.

Polling-trigger bursts. As above: slow polling does not save money, it batches the same cost into spikes you cannot predict. A quiet workflow and a spiky workflow can cost the same per month and only one of them survives your budget review.

Retry loops on failing apps. Failed actions do not bill, so a hard error is free. The expensive case is the half-broken app: runs that technically land, burn tasks, and produce nothing usable. An intermittently failing connection can multiply your run count without a single useful outcome to show for it.

Tier and seat sprawl. Team brings 25 users at $69/mo billed yearly, which sounds reasonable until the 2,000-task base turns out to be smaller than what you have already built, and you are back on the slider. Enterprise is a quote, not a price.

Then there is what happens when the allowance runs out. Zapier emails you and switches the account to pay-per-task billing for the rest of the period, so your automations keep running instead of dying mid-month. That rate is higher than your subscription's per-task rate (one third-party estimate puts it near 1.25 times, which Zapier itself does not publish). There is a hard ceiling: maximum pay-per-task usage is 3x your plan's task limit. Zapier's own example is a Professional plan with 750 tasks plus 1,500 pay-per-task, which equals 2,250 tasks. Past that, workflows pause until the next billing period.

Here is the single most useful sentence on this whole shelf. You can turn pay-per-task billing off in Billing settings. The effect is that your workflows pause at your limit instead of quietly billing you past it. If you would rather your automations stop than your invoice surprise you, that is the setting to find this week. Almost no pricing guide on this shelf mentions it, and it is the difference between a predictable bill and a monthly argument with your finance team.

One more rule changed in 2026 that most comparisons have not caught up with. AI steps, code, and the SDK now follow the same task-based model, and the AI model tier, code runtime, and connector type each affect how many tasks an action uses. A single MCP tool call costs two tasks, not one. The plan ladder still reads like a flat meter, one task per action. It is not flat, and if you are putting AI or code steps in the middle of a workflow, your real task burn is higher than your step count suggests.

Zapier vs Make vs n8n: what your tasks actually cost

Before the table, the sentence that makes the table usable: these tools do not bill the same unit, so cost per unit is not directly comparable across rows. Zapier bills per successful action. n8n bills per workflow execution, no matter how many nodes run inside it. Make bills credits, which are not the same unit as Zapier tasks, and which have counted differently since Make switched from operations to credits on 27 August 2025. Activepieces and Lindy bill per task or per credit depending on tier.

The cleanest way to feel the difference: a five-step Zap is 4 tasks on Zapier and 1 execution on n8n. Four units against one, for the same automation doing the same work. Any table that lines those two numbers up without saying so is comparing a metre to a kilogram.

Two caveats worth carrying rather than dropping. Make's entry point is from $9/month and the unit is credits, so do not convert those credits into Zapier tasks and pretend the result is a rate. The exact credit count per Make tier is churn-prone as well: Make's own page rendered "5k credits/mo" for the $9 plan in one extraction while third parties consistently say 10,000 for the same price. Lindy relaunched between January and March 2026 and removed its free plan, so the $49.99 Plus and $59.99 Pro figures you will still find widely published are pre-2026 and stale. Activepieces is worth a mention only with a warning: third-party sources put its cloud tiers near $19 for 10,000 tasks while its own page advertises flat $25 Plus and $150 Business with unlimited tasks. Those cannot both be right, so treat Activepieces pricing as unresolved until you check the page yourself.

What can you state at volume? Only what is published:

At 1,000 tasks a month, Zapier cannot give you a published price because 1,000 is already above its base tier, while Make, n8n and Integrately all publish something that covers it. At 10,000 tasks, Zapier still publishes nothing quotable and n8n publishes €50. At 100,000 tasks, self-hosted n8n and Activepieces stop being a discount and become a different economic model entirely, one where you trade a subscription for a server and your own time.

For context on why these meters keep shifting: report vendors put the workflow automation market somewhere between roughly $20B and $27B for 2026, growing at a rate they variously estimate between about 9% and 15% a year. Four vendors, four different slopes, so treat that as a direction rather than a forecast.

Is Zapier worth the premium?

Here is my honest read, and it is the same read whether or not you ever open Allable.

Zapier is worth the premium when you use the breadth. Thousands of app connectors, no-code setup your ops team can own without a developer, and reliability that mostly holds. The scale claim attached to it, that it is used by 69% of the Fortune 1000, comes from a secondary aggregator and fits that picture. If your workflows touch a long tail of niche SaaS tools, that integration surface is not something a cheaper per-task competitor replicates, and the premium buys you the ability to connect almost anything to almost anything in an afternoon.

Zapier is a bad deal when you pay for breadth you do not use. If your automations touch four apps and run a few hundred times a month, you are subsidising a connector library you will never open, and you are metered per action for the privilege. The pricing page is a menu, not a shopping list. Order the part you eat.

That is the gap my team builds into. Allable Pro is €37/month (€31/month billed annually), and the unit is the work you ask for rather than the number of nodes a workflow happens to contain. That matters most for exactly the pattern above: a multi-step workflow with a few AI or code steps in the middle, which is where per-action metering gets expensive fastest. It is not the right answer for everyone. If your team needs a thousand niche connectors and a visual canvas, use Zapier and stop reading this.

If you are still picking a category rather than a vendor, our breakdown of marketing automation tools covers what each platform is actually for, and the workflow automation tools roundup maps the no-code shelf. If the per-action meter is the thing you want to escape, n8n for marketing walks through the execution-based model with marketing workflows in mind. And if what you want is automation you can hand a brief to instead of a canvas to draw on, agentic marketing tools and our piece on running an AI automation agency both go deeper on where that is heading.

You will not get your automation bill right on the first try. Nobody does. What you can control is which unit you are being metered in, and whether you checked that unit before you built twelve workflows on top of it.