Zapier pricing breakdown 2026: what it really costs at volume

Zapier connects your business apps so work happens without a person: a form gets filled, the customer record updates, the email goes out. It is the easiest automation tool to start with, and the easiest to end up overpaying for. The billing unit is the task: every step in an automation (a "Zap") uses one task each time it runs, so a busy five-step automation quietly burns thousands a month. Right for most teams starting out. Wrong once your automations run hundreds of times a day. Here is the real math.

How we checked

Every figure on this sheet comes from Zapier's official pricing page, pulled July 10, 2026. The page publishes entry prices per plan and a task-tier selector rather than a full rate card, so where a tier's exact dollar figure is not printed publicly, this sheet says which tier you land in instead of inventing a rate. The overage and helper-step rules are quoted from the same page. One moving part to know about: Zapier has announced a pay-per-task rate change for monthly subscribers taking effect from the first billing cycle on or after July 15, 2026, so check your own billing screen for the rate that applies to you.

Plan tiers

Two structural facts sit behind that table. First, each paid plan scales through task tiers, from 100 tasks a month up to 2 million before pricing goes custom, so "Professional" is a family of prices, not one price. Second, paying monthly instead of committing to a year runs roughly 33% higher: Professional lands near $29.99 a month on a month-to-month basis. Pricing checked July 2026.

The Free plan is genuinely usable for testing: 100 tasks, two-step Zaps, and unlimited Zaps, Tables, and Forms. It is not usable for running a business function, which is the point of the 100-task ceiling. The sharper limit is the two-step shape itself, a trigger plus one action: that covers "form to sheet" and nothing that resembles a pipeline. Free also caps Zapier Tables at 2,500 records and Forms at 10 pages with 5 MB uploads, numbers worth knowing before a plan leans on the zero-task surfaces to dodge the meter.

What counts as a task

One completed action step in a Zap = one task. A Zap with five action steps uses five tasks every time it fires successfully. Zapier's page also notes that external connector calls consume tasks, and that a task only counts on successful completion: polling for new data costs nothing, and a run that fails on step one does not bill the steps that never happened.

What does NOT count: the helper steps. Filters (skip this run unless a condition is met), Paths (branch into different routes), Formatter (reshape text and numbers), Delay, Looping, Sub-Zap, Digest, Zapier Tables, Zapier Forms, Zapier Manager, and Zapier Storage are all free. Zapier added those exemptions in January 2026, which makes the if-this-then-that logic genuinely free.

So a three-step Zap that fires after a filter passes still uses three tasks per run, not four. That is a real improvement from how the billing worked before.

The real bill at common usage levels

This is where most teams get surprised.

A lead-capture Zap that fires 100 times a day and touches five apps burns 15,000 tasks a month. The Team plan's entry allowance covers 2,000. You are past your monthly allowance on day two.

Overage billing

When you hit your plan's limit, Zapier can keep your automations running and bill for the extra ("pay-per-task"), but only if you opted in. The per-task overage rate depends on your plan tier. The extra billing is capped at three times your plan's task limit; past that, your Zaps stop until next month.

Note the date: Zapier is changing pay-per-task rates for monthly subscribers effective the first billing cycle on or after July 15, 2026. Annual subscribers are not affected in that round. Check your billing settings for your exact rate before that cycle lands.

The AI features and what they cost

Zapier now ships a stack of AI products alongside the core automation plans, and they bill separately. From the July 2026 pricing page:

• Zapier Agents, its autonomous AI workers, include 400 activities a month on the free tier; Agents Pro is $400 billed annually (about $33 a month) for 1,500 activities.
• Zapier Chatbots run free for 2 chatbots; Chatbots Pro is $160 billed annually for 5, and Advanced is $800 billed annually for 20.
• Zapier MCP, which lets an outside AI assistant fire Zapier actions directly, costs 2 tasks per tool call, so an AI agent hammering your Zaps consumes task budget twice as fast as the Zaps themselves.
• Copilot, the build-a-Zap-by-chat assistant, ships on every plan including Free.

None of these replace task billing; they sit on top of it. An AI agent that triggers a five-step Zap still burns the five tasks.

Three scenarios, priced

Scenario 1: a 3-step lead-capture Zap at 2,000 tasks a month. About 22 leads a day: form in, CRM record, notification out. That volume is exactly the Team plan's entry allowance, $69 a month, with zero headroom; one busy week tips it into overage or a pause. On Professional you would need a task tier above the 750 entry stop. This is the most common small-business shape, and it sits awkwardly between Zapier's two published entry prices.

Scenario 2: a 5-step pipeline at 100 runs a day. Enrichment, scoring, two system updates, and a log row: 15,000 tasks a month, every month. That is far past both entry allowances and into task tiers the pricing page only reveals through its selector. At this shape, price the same build in Make credits before renewing; the unit math is in the Make vs Zapier comparison.

Scenario 3: a webinar burst. A 4-step registration Zap sits at 30 runs a day normally (3,600 tasks, needs a mid Team tier), then a launch week spikes it to 500 registrations. That single week adds 2,000 tasks. With pay-per-task on, a Team entry plan absorbs it at the overage rate, capped at 6,000 extra tasks (three times the 2,000 allowance). With pay-per-task off, registrations silently stop mid-campaign. Bursty marketing calendars need that toggle decided in advance, not discovered during the launch.

Scenario 4: the AI agent tax. Zapier MCP prices an outside AI assistant's tool call at 2 tasks. Wire an agent that fires 50 Zapier actions a day and the agent alone consumes 3,000 tasks a month, before counting whatever the Zaps it triggers burn on their own steps. AI-driven automation lands on the same meter as everything else, at double rate. Budget agent activity as its own line item, not as a rounding error on the Zap bill.

The task audit, step by step

Zapier's billing screen reports task usage by Zap, which makes the audit mechanical rather than forensic. Fifteen minutes, once a quarter:

1. Open Billing and usage and sort the current cycle by tasks used.
2. For the top three Zaps, write down two numbers: steps per run and runs per month.
3. Walk each step and mark the ones a free helper could replace. The list of zero-task steps is long, and most accounts use two of them.
4. Check the trigger order. A Filter placed first stops a run before any action bills; the same Filter placed after two actions lets those two tasks bill on runs that were always going to be thrown away.
5. Kill the zombie Zaps. Every account past its first year has automations still firing for a process, a form, or a teammate that no longer exists.
6. Rerun the plan math with the cleaned numbers before renewing.

The audit usually returns 10 to 30 percent of the bill, which is worth doing before any migration conversation starts.

Cutting the bill without switching

Four moves keep the same automations on a smaller meter:

• Filter first, always. A task only bills when an action completes, so a run rejected at the top of the Zap bills nothing. Every condition you can test before the first action is free protection.
• Batch the logging. A Zap that appends one row per run to a spreadsheet pays one task per run for a log nobody reads live. Digest, which is free, collects entries and releases them on a schedule, so thirty log actions become one.
• Keep reference data in Tables and Storage. Both are on the zero-task list. A lookup against Zapier Tables costs nothing, where the same lookup as an external action step bills a task per run.
• Commit annually once volume is proven. The 33% gap between month-to-month and annual is the single largest discount on the page. Take it after a month or two of measured usage, not before.

None of this changes what the automations do. It changes how many billable steps they take to do it.

Run them in that order, too: audit first, structural fixes second, annual commit last. Locking the 33% discount onto an unaudited bill preserves the waste at a discount, and a year is a long time to pay 67 cents on the dollar for tasks a Filter should have stopped.

Which plan fits which team

A solo operator proves the workflow on Free's 100 tasks, then lives at Professional's entry tier. 750 tasks covers a handful of low-volume Zaps: think 25 runs a day across everything at one step each, or a single three-step Zap firing eight times a day. The meter does not care that you are one person; a daily 5-step digest alone is 150 tasks a month, a fifth of the entry allowance.

A small team with real lead flow outgrows Professional's shape before its task count. Team at $69 buys 2,000 tasks and, more importantly, up to 25 users, so the person who builds the Zap is no longer the only person who can fix it at 6 pm on a Friday. The 2,000 is the entry stop, not the ceiling; the task selector scales the same plan when the team's volume does.

Past roughly 2,000 sustained tasks, stop reading plan names and run the tier selector against your audited number, then price the same workflows in Make credits and n8n executions before talking to Zapier's sales team about Enterprise. The alternatives sheet is the decision framework for exactly that conversation.

Who should skip Zapier

Skip it if you run more than 2,000 tasks a month and cost is the main constraint. Make charges per credit instead of per task, and its per-unit cost is lower at volume for the same logic. The Make pricing breakdown covers the credit model, and the automation tools roundup puts all four major options side by side.

Also skip it if your build needs complex branching, loops over big lists, or direct connections to custom systems. Those are possible in Zapier but awkward. Make or n8n handle that shape better; the wider field is priced in the Zapier alternatives comparison.

Stay if the workflow count is small, the volumes are low, and the people maintaining it are non-technical. That is the profile Zapier is priced for, and at that profile it is genuinely the least friction of the lot.

The part that breaks

The step-count multiplier catches teams by surprise. A five-step Zap running 200 times a day uses 30,000 tasks a month. At that volume you are looking at Enterprise pricing or heavy overage charges.

The second trap: turning on pay-per-task without an alert. Zapier will bill up to 3× your plan limit before stopping anything. On a Team entry plan that means up to 6,000 extra tasks billed before your Zaps pause. Set a budget alert in your billing settings first.

The third trap: creep. Automations start at three steps and grow. Each new step costs a task per run, forever. Audit your active Zaps quarterly and delete steps that a free filter or formatter step already handles.

Copy this

Run this before committing to a plan:

(steps × daily_runs × 30) = monthly tasks needed

Example: 5 steps × 100 runs/day × 30 = 15,000 tasks/month

Free  =   100 tasks → 0.67 runs/day at 5 steps
Pro   =   750 tasks → 5 runs/day at 5 steps
Team  = 2,000 tasks → 13 runs/day at 5 steps

If your number exceeds 2,000 tasks, get a quote from Zapier Enterprise or run the same formula against Make's credit pricing before deciding.

Upgrade path

Once the billing is understood and the Zaps are running, the next issue is whether the emails they send actually arrive. Mail providers now block senders who have not proven they own their domain, and the email authentication guide covers the three settings that fix it in under an hour.

For the speed-to-lead build Zapier handles well (form submission to customer list to instant follow-up), the lead-to-CRM automation tutorial walks through the same flow using Make. Run both at your task volume and pick the cheaper one.

Browse the full automation topic for the builds worth wiring up next.