Zapier bills every action, so the bill grows with orders times steps. This is the volume where that stops being cheap, worked through one five-step order flow.
A small business on Zapier rarely decides to leave. The bill decides. A team that started on the Professional plan at $29.99 a month for 750 tasks can be on the 10,000-task tier at $193.50 a month a year later without adding many zaps, because the same orders now run through more steps. Our rough line: below about 2,000 tasks a month with simple, straight-line zaps, stay where you are. Past 10,000 tasks, or once zaps start making judgment calls, per-task pricing stops being the cheap option. Prices here come from Zapier's pricing page in October 2026, on monthly billing.
Where per-task pricing starts to hurt
Zapier charges for actions, and the tiers climb in steps. On the Professional plan with monthly billing, 2,000 tasks cost $73.50, 5,000 cost $133.50 and 10,000 cost $193.50. Paying annually takes 33% off, which brings the 10,000 tier down to $129 a month. The Team plan, which adds shared connections and up to 25 seats, starts at $103.50 for 2,000 tasks.
None of that is expensive for what it does. The trouble is the shape of the curve. Your bill tracks orders multiplied by steps, and both numbers grow when the business does.
Going over your tier ends one of two ways, depending on a setting called pay-per-task. Switched off, your zaps stop at the limit until the next cycle. Switched on, extra tasks are billed at 2.5 times your base rate on a monthly plan, or 1.25 times on an annual one, and usage still stops at three times your subscription. A holiday spike on a monthly plan is the expensive case.
What Zapier counts as a task, and what it doesn't
Zapier's help article on how task usage is measured defines a task as a successful action. Triggers never use tasks. Filter and Paths steps don't either, and nor does Formatter. Failed actions aren't billed.
AI by Zapier and Code by Zapier steps draw from the same task pool as everything else. Add an AI step to sort incoming email and you've added at least one task to every run, including the runs where the email turns out to be spam. Zapier's help article on AI model tiers bills the Standard tier at one task a run, Advanced at three and Premium at five, and a new AI step on a paid plan starts on Premium.
If you're still working out which jobs deserve automating at all, our list of business processes worth automating first covers the inputs and failure modes of twelve of them.
A worked example: one order, five tasks
Take an illustrative online shop. A new Shopify order triggers a zap that does five things: finds the customer in HubSpot, uses an AI step, set to the Standard tier, to read the order note and flag anything odd, creates an invoice in Stripe, adds a row to a Google Sheet and posts to Slack. The trigger is free, so each order costs five tasks. Leave the AI step on the default Premium tier and it's nine tasks an order, which puts 2,000 orders at 18,000 tasks, well past the 10,000 tier.
- 400 orders a month: 2,000 tasks, $73.50.
- 1,000 orders a month: 5,000 tasks, $133.50.
- 2,000 orders a month: 10,000 tasks, $193.50.
- 2,500 orders in a busy December: 12,500 tasks, so 2,500 of them go to the overage rate, or the zap stops partway through the month.
At 2,000 orders a month that's about $2,320 a year for one workflow, or $1,548 on annual billing. That's a fair price for something that saves hours. It's also a cost that never ends, and it rises again with the next step somebody adds.
AI automation vs Zapier, side by side
Zapier isn't the only meter. Make bills in credits, and its pricing page says most actions cost one credit, reading data from an app or webhook included, while its Router module is free. n8n bills per execution, and its pricing page defines an execution as a single run of the entire workflow, however many steps it has. A custom build runs on your own server and pays for hosting and model tokens.
| Zapier | Make | n8n | Custom build | |
|---|---|---|---|---|
| What you pay for | Tasks (successful actions) | Credits (most actions) | Workflow executions | Hosting and model tokens |
| The five-step order above | 5 tasks | About 6 credits, since reading the trigger counts | 1 execution | No per-step charge |
| Branching | Paths free, actions inside them billed | Router free, modules billed | Same run, same price | Ordinary code |
| An AI step | Uses tasks from the same pool | One credit, sometimes more | Inside the execution, plus your own model bill | Paid per token to the model provider |
| Where it runs | Zapier's cloud | Make's cloud | n8n's cloud or self-hosted | Your server |
n8n's Starter plan is 20 euros a month on annual billing for 2,500 executions, and Pro is 50 euros for 10,000. The 2,000-order shop above fits inside Starter. That per-run model is the middle ground most people skip past.
When branching makes it worse
Paths are free in Zapier, which sounds generous until you see what sits inside them. A zap that sends wholesale orders one way and retail orders another often repeats the same lookup and update steps in both branches, and every one of those is billed.
There's a ceiling too. Zapier's limits page caps a zap at 100 steps, counting every step inside every path. Few zaps get near it. The ones that do are doing a job a few dozen lines of code would do more clearly, and they're the zaps nobody wants to edit because nobody remembers why the fourth branch exists.
Where AI steps change the math
The model itself is cheap. Anthropic lists Claude Haiku 5.5 at $0.10 per million input tokens and $0.50 per million output tokens. As an illustrative sum, reading 2,000 order notes a month at about 1,500 tokens in and 200 out comes to roughly 50 cents.
Inside Zapier, those same 2,000 AI steps are 2,000 tasks on the Standard tier and 10,000 on Premium, which is the whole 10,000 tier on its own. You're paying for the step, and the thinking is the small part.
The bigger issue with AI in a zap is what happens when the model is unsure. A zap moves forward or it stops. It has no natural place for "this might be a complaint, can someone look?" A custom system can hold the doubtful ones in a review queue, show a person the message next to the model's reading, and log which kinds of message keep landing there.
Signs you've outgrown Zapier
- One or two zaps use more than half your monthly tasks.
- You've switched on pay-per-task to get through a busy month, more than once.
- A zap has several paths, and the same steps repeat in each.
- An AI step makes a call you'd want a person to check, and there's nowhere for that check to happen.
- Errors show up days later, when a customer asks where their invoice went.
Any one of these on its own isn't a reason to leave. A few together are.
What a custom build changes
On our side, custom AI automation built around your own tools starts with an audit of your workflows, each task scored by hours lost, so you see the shortlist before anything is built. The first automation is usually live in two to four weeks. It connects through the APIs your tools already expose, such as Gmail, HubSpot, Shopify, Stripe and Google Sheets, runs on infrastructure you control, keeps an audit log of every action and puts sensitive steps behind a human approval.
What it costs you is an upfront build and someone to look after it. When an app changes its API, Zapier's team fixes the connector. On a custom build, that job falls to whoever maintains it. For a shop doing 400 orders a month, that trade rarely makes sense. At 2,000 orders with AI steps and approvals in the flow, it often does.
Start with the zap, not the platform
You don't have to move everything. Check task usage by zap first. A couple of heavy workflows tend to sit on top of a long tail of small ones: a form to a spreadsheet, a booking to a Slack channel. Leave the tail where it is. It's cheap and it works.
Then take the heaviest zap and multiply its tasks per run by next year's volume, not this year's. If that lands past the 10,000 tier, price a replacement for that one workflow and set it against two years of what Zapier would charge for it.
Five questions before you leave Zapier
Is Zapier cheaper than building a custom automation?
At low volume, yes. Under a few thousand tasks a month, $73.50 or less is hard to beat with any build. The gap closes when one workflow runs thousands of times a month with five or more actions each.
Do Zapier filters and paths use tasks?
No. Zapier's help documentation says triggers, Filter, Paths and Formatter steps don't use tasks. The actions inside each path still do.
What happens if I run out of Zapier tasks?
With pay-per-task off, your zaps stop until the next billing cycle. With it on, extra tasks cost 2.5 times your base rate on a monthly plan or 1.25 times on an annual plan, and usage stops at three times your subscription.
Is n8n a good alternative to Zapier?
For high-volume workflows with many steps, it can be. It bills per execution, so a ten-step run counts once. It takes more setting up, and if you self-host it, updates and uptime are yours to manage.
Can I keep Zapier for some workflows and move others?
Yes, and for most accounts it's the better plan. Move the one or two workflows that use most of your tasks and leave the small ones where they are.
