Zapier vs Make vs n8n: The Billing Model Decides It
These three bill differently, and that decides your cost more than features do. Where each wins, the self-hosting trade-off, and the error handling nobody compares.
Quick answer
Zapier has the most integrations and the simplest interface, and it gets expensive as volume grows because it bills per task. Make is cheaper at volume with far better handling of complex logic, at the cost of a steeper interface. n8n is cheapest of all if you self-host and are comfortable maintaining a server. The decision is not really about features — it is about whether your constraint is time, money, or control, and only one of those can be your priority.
The standard comparison of these three lists integration counts and pricing tiers, which tells you almost nothing, because the number that determines your bill is not the plan price. It is how each platform counts what you run.
Two people running identical workflows on Zapier and Make can see very different invoices, and the reason is architectural rather than commercial. That is what this covers.
TopTut takes no affiliate commission from any of the three.
The billing difference that decides your cost
Zapier bills per task, where a task is broadly each action step that runs. Make bills per operation, and its architecture handles bundles of items differently. n8n’s cloud plans bill per workflow execution, and self-hosting bills you nothing per run at all.
Same job: a form arrives, you enrich it, add it to a CRM,
notify Slack, and add a row to a sheet.
Zapier: 1 trigger + 4 actions
= 4 tasks per submission
Make: counted as operations per module run,
with bundle handling that changes the arithmetic
on anything that loops over multiple items
n8n cloud: 1 workflow execution, regardless of
how many steps are inside it
n8n self-hosted: no per-run charge at all
At 100 submissions/month the difference is trivial.
At 50,000 it decides which platform you can afford.That last line is the whole point. Below a few thousand runs a month, pick on interface preference and stop thinking about it. Above that, the counting model dominates every other consideration.
Where each one genuinely wins
| Zapier | Make | n8n | |
|---|---|---|---|
| Integrations | Most, by a wide margin | Extensive | Good, plus easy custom nodes |
| Learning curve | Gentlest | Moderate | Steepest |
| Complex logic | Adequate, gets awkward | Excellent. Visual branching and iteration | Excellent, with code when needed |
| Cost at high volume | Highest | Lower | Lowest, especially self-hosted |
| Self-hosting | No | No | Yes. The main reason to choose it |
| Data residency control | Limited | Limited | Complete, if self-hosted |
| Non-technical users can maintain it | Yes | With training | Rarely |
My take
Start on Zapier even if you suspect you will outgrow it. The fastest way to discover which automations actually matter is to build ten cheaply and watch which ones you keep. Migrating three proven workflows to Make later costs a day; spending a fortnight learning a more powerful tool before you know what you need costs a fortnight and frequently produces automations nobody uses. Optimise for learning first, cost second.
The self-hosting question
n8n’s distinguishing feature is that you can run it on your own infrastructure. This gets recommended enthusiastically and the trade is usually understated.
Genuine reasons to self-host: data that legally cannot leave your infrastructure, very high volume where per-run pricing becomes punitive, or connecting to internal systems not reachable from a cloud platform.
What you take on: a server to patch, upgrades to apply, backups to verify, uptime to monitor, and — the one people forget — being the person who fixes it at 11pm when a workflow that runs payroll notifications stops. “Free” describes the licence, not the total cost.
Watch out
n8n uses a fair-code licence rather than a standard open-source one, with restrictions on offering it as a hosted service to others. For internal business use this is almost never a problem, but if you intend to build a product on top of it, or resell automation as a managed service to clients, read the licence terms properly first. Assuming “open source” means unrestricted commercial use is a mistake that surfaces late.
Error handling, which nobody compares
The genuinely important difference and the one absent from every comparison table. What happens at 3am when a step fails?
- Does it retry, and how many times? Automatic retries fix transient API failures for free — and can also duplicate an action if the first attempt actually succeeded before timing out.
- Can you build an error branch? Make and n8n handle this well. It is the difference between a failure being logged and a failure notifying someone.
- How long is the run history? Debugging a failure from last Tuesday requires last Tuesday’s log still existing, and retention varies by plan.
- Can you replay a failed run after fixing the cause, or must the source event happen again?
Configure failure notifications on whichever platform you pick, before you rely on anything. The most common automation disaster is not a workflow that breaks — it is one that broke six weeks ago and nobody noticed.
Choosing
| If you… | Choose |
|---|---|
| Are automating for the first time | Zapier. Learn what you need cheaply |
| Run under a few thousand tasks a month | Any of them. Pick on interface |
| Have high volume and a real bill | Make, or n8n |
| Need genuinely complex branching and loops | Make |
| Have data that cannot leave your infrastructure | n8n, self-hosted |
| Have no one to maintain a server | Not self-hosted n8n, whatever the cost saving |
| Need non-technical staff to edit workflows | Zapier |
| Are building automation as a service for clients | Read n8n’s licence before assuming |
My verdict
These are genuinely different products aimed at different constraints. Zapier sells time — you will build something today. Make sells capability per pound — more logic, lower cost at volume, more to learn. n8n sells control — you own the infrastructure and everything that comes with owning infrastructure.
My honest recommendation for most small businesses is to start on Zapier, get ten automations running, and see which survive three months. Then move the survivors somewhere cheaper if the bill justifies it. Choosing the most powerful tool before you know what you are automating is how people end up with a sophisticated platform and two workflows.
And whichever you pick, turn on failure alerts on day one.
For deciding what to automate in the first place, see the workflow automation guide. Where a process needs judgement rather than rules, agentic AI explained covers what changes and what it costs.
Frequently asked questions
Zapier vs Make vs n8n, which should I use?
Zapier if you are starting out or need non-technical staff to maintain workflows, because it is the simplest and has the most integrations. Make if you have real volume or need complex branching and loops, since it is cheaper at scale and handles logic better. n8n if you need to self-host for data residency or very high volume.
Why is Zapier expensive at high volume?
Because it bills per task, and a task is broadly each action step that runs. A workflow with one trigger and four actions consumes four tasks every time it fires. At a hundred runs a month that is irrelevant; at fifty thousand it dominates every other cost consideration and is the usual reason people migrate.
Is n8n really free?
The self-hosted licence has no per-run charge, but free describes the licence rather than the total cost. You take on a server to patch, upgrades to apply, backups to verify, uptime to monitor, and being the person who fixes it at 11pm. If nobody can own that, the cloud plans or a hosted competitor work out cheaper in practice.
Is n8n open source?
It uses a fair-code licence rather than a standard open-source one, with restrictions on offering it as a hosted service to others. For internal business use this is rarely an issue. If you intend to build a product on it or resell automation as a managed service to clients, read the licence terms before assuming unrestricted commercial use.
Which automation platform handles complex logic best?
Make, for visual branching, iteration over collections and error routes, with n8n comparable and able to drop into code when needed. Zapier is adequate for straightforward sequences but becomes awkward once you need real branching, loops over multiple items, or sophisticated error handling.
What should I check about error handling before choosing?
Whether failed steps retry automatically and how many times, since retries fix transient failures but can duplicate actions that actually succeeded before timing out. Whether you can build an explicit error branch. How long run history is retained for debugging. And whether you can replay a failed run after fixing the cause.
Should I start with the most powerful automation tool?
Usually not. The fastest way to learn which automations matter is to build ten cheaply and see which you still use in three months. Migrating three proven workflows later costs about a day. Spending a fortnight learning a powerful platform before knowing what you need frequently produces sophisticated automations nobody uses.
What is the most common automation failure?
Not a workflow that breaks, but one that broke weeks ago while nobody noticed, because its output was something nobody checks until they need it. Configure failure notifications on day one, and where possible alert on silence too, since a daily workflow that has stopped running produces no errors at all.
