Zapier Pricing Explained: What a Small Business Actually Pays After the Free Plan

Zapier’s free plan is genuinely useful for testing an idea, and genuinely misleading about what running real automation on Zapier actually costs. The gap between «I tried it for free and it worked» and «here’s my monthly bill three months in» is where most small businesses get surprised, and it’s almost always for the same handful of reasons. Here’s what’s actually in each plan in 2026, and where the bill grows past what the pricing page implies.

What the free plan actually covers

The free plan gives you 100 tasks a month and, critically, single-step Zaps only — one trigger, one action. You also get unlimited Zaps, Tables, and Forms, plus access to Zapier’s AI-assisted builder (Copilot) in beta. That’s a real, workable setup for testing whether an automation idea works at all.

What it doesn’t cover is almost any real small business process. The moment a workflow needs to do more than one thing after the trigger — create a CRM record and send a Slack notification, say — the free plan can’t build it. Multi-step Zaps require a paid plan. This is the single most common reason people move off free faster than they expected: not because they ran out of tasks, but because they hit the one-action ceiling on day one.

The paid plans, with real prices

Annual billing saves roughly a third off the monthly price across every paid tier — that’s not a small discount, and it’s the main lever Zapier gives you to bring the effective monthly cost down. The catch is you’re committing for a year to a task allowance you’re estimating, not one you’ve actually measured yet.

Each tier’s task allowance also scales upward — Professional and Team both offer higher task-count versions of the same plan at a higher price, so «Professional» isn’t one price, it’s a starting price that climbs with volume. Two businesses both on «Professional» can be paying quite different amounts depending on which task tier they picked.

What actually counts as a task

A task is charged every time a Zap successfully completes one action step. The trigger itself is free — it’s only the actions after it that count. Built-in utility steps like filters, paths, formatting, and delays generally don’t consume a task on their own, which is a detail worth knowing because it means the cost driver is specifically how many external actions (create a record, send an email, post a message) a Zap performs, not how complex its logic looks on screen.

This matters because a «simple» Zap on paper can still burn through tasks fast if it does several external actions per run. A single Zap that checks a form submission, creates a CRM contact, sends a confirmation email, and posts an internal Slack notification uses three tasks every time it fires — not one. Run that 300 times a month and you’ve used 900 tasks on a single workflow, which alone exceeds the Professional plan’s starting allowance.

Where people actually get surprised by the bill

A few patterns show up over and over in real small business accounts:

Multi-step Zaps forcing an upgrade immediately. Anyone testing on the free plan with a real workflow in mind hits the single-step wall almost immediately, which means the real evaluation period starts on a paid plan, not the free one.

Task usage multiplying with every action added to a Zap. Adding a second or third action to an existing Zap to «make it do a bit more» quietly multiplies its task cost per run. A two-action Zap that becomes a four-action Zap roughly doubles its monthly task consumption without anyone updating the budget for it.

Overage billing kicking in past the plan limit. Once you exceed your task allowance, Zapier can continue running Zaps on pay-per-task overage billing (a workspace setting), at a rate less favorable than your base subscription tier — or Zaps pause entirely once usage hits roughly three times the plan’s limit, whichever happens first. Either way, exceeding your allowance isn’t free.

Add-on products billed separately from the core plan. Zapier’s newer AI products — Agents and Chatbots — are not included in Professional, Team, or Enterprise. Agents has its own free tier (capped activities per month) and its own paid tier priced per year; Chatbots works the same way, with free, mid, and advanced tiers. A team that starts using these alongside its core Zaps is paying for two or three Zapier products, not one, even though it feels like a single subscription in the dashboard.

Monthly billing being chosen by default. Because monthly billing costs roughly 50% more than the equivalent annual rate, a business that signs up monthly to «try it first» and never switches is paying a meaningful premium indefinitely, not just during a trial period.

One Zap eating the whole account’s allowance. Tasks come from a single shared pool across the entire account, not a separate budget per Zap. A workflow that starts firing more often than expected — a form that gets spammed, a trigger polling more frequently than planned — can burn through the monthly allowance for every other Zap on the account, not just itself. On a small team, that usually shows up as «why did everything stop working on the 20th of the month» rather than a clean warning about the one workflow actually responsible.

A realistic small business bill

Picture a small service business running three workflows: quote follow-up (three actions, 200 runs/month = 600 tasks), lead routing from a web form into a CRM (two actions, 150 runs/month = 300 tasks), and an internal Slack alert for high-value deals (one action, 50 runs/month = 50 tasks). That’s 950 tasks a month before anything grows — already past the Professional plan’s starting 750-task tier, meaning the actual plan needed is the next task tier up, at a higher monthly price than the advertised «starting at» figure most comparisons quote. Add a chatbot or an AI agent step to any of those workflows and there’s a second subscription on top.

How to keep the bill predictable

A few habits keep the surprise out of the invoice: count actions per Zap, not just the number of Zaps, when estimating task usage. Check actual task consumption in the dashboard after the first full month on a paid plan, before assuming the tier you picked will hold. Commit to annual billing only after that first real month’s usage is known, not before. And treat Agents, Chatbots, and other add-on products as separate purchasing decisions with their own cost, not features bundled into whatever core plan you’re already paying for.