Zapier vs Make vs n8n vs custom code: which should you use?
For most small firms, start with a no-code platform. Zapier is the easiest, Make suits visual multi-branch flows, and n8n is the cheapest at volume because a whole run counts once. Move to custom code when a workflow is central to client delivery, has complex logic, or breaks often enough that someone spends hours fixing it.
| Zapier | Make | n8n | Custom code | |
|---|---|---|---|---|
| Typical cost, US | Free (100 tasks); Professional from $19.99 a month billed annually for 750 tasks | Free plan with 1,000 credits a month; paid prices not shown on its pricing page | Cloud from €20 a month billed annually for 2,500 executions; self-run version free | $2,000-5,000 for a single automation or integration, plus upkeep |
| Typical cost, UK | Same plans, billed in dollars or local currency | As left | As left | £1,600-4,000 for a single automation or integration |
| Speed to start | Minutes | Minutes to hours | Hours (more if you run it yourself) | 1-2 weeks |
| Who maintains it | Whoever built the Zap - often the ops lead | Whoever built the scenario | Whoever built it, plus whoever looks after the server if self-run | A developer, or us on a monthly plan |
| Best for | Simple two-to-five-step flows between popular apps | Visual flows with branches and data shaping | High-volume or many-step flows on a budget | Core client workflows, complex rules, custom screens |
| Worst for | Many-step flows at high volume | Teams who want the simplest possible tool | Teams with no one technical at all | Simple, low-volume tasks a Zap does fine |
Platform prices are from each vendor's pricing page in October 2026 (Zapier, October 2026; Make, October 2026; n8n, October 2026). Custom code costs are the typical market range for a single automation or integration from our custom software cost guide, compiled from published rate guides.
What you are really comparing
All four do the same basic thing: when something happens in one app, do something in another. A new client signs, so a project gets created, a folder appears and a welcome email goes out. The differences are in how they count usage, how much logic they can handle, and who has to look after them.
We use all of these at Forge, and we use custom code too. The aim of this page is to help you pick the right tool for each job, not to talk you out of no-code.
Real 2026 prices at three usage levels
The tricky part of comparing prices is that each platform counts differently. Zapier counts tasks: every action step that runs counts as one. A five-step Zap that runs once uses five tasks. n8n counts executions: a whole workflow run counts once, however many steps it has. Make counts credits, and its pricing page shows only the free allowance of 1,000 credits a month, so we have left its paid tiers out rather than guess.
Here is one five-step workflow (say, a new client triggers a project, a folder, a Slack message, a CRM update and a welcome email), at three volumes.
| Runs a month | Zapier tasks used | Zapier plan (annual billing) | n8n executions used | n8n Cloud plan (annual billing) |
|---|---|---|---|---|
| 150 | 750 | Professional, $19.99 a month | 150 | Starter, €20 a month |
| 400 | 2,000 | Professional, $49 a month (or Team, $69) | 400 | Starter, €20 a month |
| 2,000 | 10,000 | Professional, $129 a month (or Team, $169) | 2,000 | Starter, €20 a month |
Zapier prices are from Zapier, October 2026; monthly billing costs more ($29.99, $73.50 and $193.50 for the Professional tiers above). n8n prices are from n8n, October 2026: Starter is €20 a month for 2,500 executions and Pro is €50 for 10,000, billed annually. n8n's page also says a standard self-hosted version is free on GitHub, though someone has to set up, secure and update the server.
The pattern is clear: at low volume, the prices are close. As runs and steps grow, Zapier's per-task counting climbs and n8n's per-run counting does not. That is the main reason people search "zapier vs n8n". It is not the only factor, though, because the cheapest platform is the one your team can actually look after.
Where each one breaks down
Zapier
breaks down on cost at volume with many steps, and on logic. Once a Zap has several paths, filters and lookups, it becomes hard for anyone but the person who built it to follow. It is also the easiest of the four for someone non-technical to build, which is a real strength.
Make
breaks down when the person who built the scenario leaves. Its visual canvas is powerful, but a large scenario with many branches becomes its own small piece of software, and it needs someone who understands it.
n8n
breaks down when nobody on the team is comfortable with a slightly more technical tool, or when you choose to run it yourself and nobody is looking after the server. The cloud version removes most of that worry.
Custom code
breaks down on simple jobs. Writing and looking after code to move a form response into a spreadsheet is overkill. It also needs someone to maintain it, and if that is a freelancer who moves on, you are stuck.
The maintenance burden nobody prices in
The platform fee is the small number. The bigger cost is time. When a connected app changes a field name or adds a security step, flows stop working, often silently. Someone has to notice, work out which of forty Zaps broke, and fix it.
In a people business - a business that sells its people's expertise and time, such as an agency, accountant, law firm or consultancy - that someone is usually the ops lead or the owner. Their time is the expensive part. If they are spending a morning a week keeping automations alive, that is the real price of the tool, whatever the invoice says.
When to move off Zapier
You do not need to move off Zapier because a blog said so. Here are the signs it is time:
Your bill keeps climbing
because a few many-step Zaps run hundreds of times a month. Try n8n Cloud before custom code; it may solve it for €20-50 a month.
A workflow has become core to client delivery.
If it breaking means a client does not get their deliverable, it deserves proper error handling and someone watching it.
The logic has outgrown the canvas.
Many paths, lookups across several apps and special cases per client are easier to read, test and change in code.
You need a screen, not just a sync.
A client portal, a status page or a one-click capture tool is a piece of software with a user, not an automation.
Only one person understands it.
If your automations are a mystery to everyone but one person, the risk is bigger than the cost.
If none of those apply, stay where you are. Zapier is doing its job.
Pick Zapier if...
- Your flows are simple and connect popular apps.
- The person building them is not technical.
- Volume is modest - a few hundred runs a month.
Pick Make if...
- Your flows need branches, loops or reshaping data between apps.
- Someone on the team enjoys a visual builder and will own it.
- You can work with its credit-based pricing (check the current plans directly on Make's site).
Pick n8n if...
- You run many-step flows at volume and Zapier's task counting is getting expensive.
- Someone on the team is comfortable with a slightly more technical tool.
- You want the option to run it on your own server later.
Pick custom code if...
- The workflow is central to how you serve clients.
- It needs a real screen for people to use, not just data moving in the background.
- The logic is complex enough that no-code has become hard to follow or test.
- You have someone to look after it - a developer, or a monthly plan like ours.
- You want it rolled out properly. A tool only gives hours back if people use it, so training the team matters as much as the code.
Our recommendation: how we'd decide for a 20-person firm
For a 20-person agency or accounting firm with ten apps and no engineer:
- Keep the simple Zaps. If something runs fine, costs little and nobody worries about it, leave it.
- List the flows that break or cost the most. Those are the candidates for change, not everything.
- Try n8n Cloud for the expensive ones. If the problem is task counting at volume, switching platform is cheaper than writing code.
- Move to custom code only for the core few. The two or three workflows that touch clients, have complex rules, or need a screen are where code pays for itself.
- Decide who looks after it. Whatever you pick, name the person or service responsible for noticing when it breaks.
Honestly, plenty of firms we talk to should stay on Zapier or move to n8n, not hire us. Our business automation consultant page covers when a monthly plan makes sense instead.
Worked example: a one-click research tool, four ways
Take one real job: the guest research Chrome extension, a browser extension that captures a person's profile from any site straight into the right record. Our custom software cost guide puts the typical market cost of a single automation or integration at $2,000-5,000 in the US or £1,600-4,000 in the UK, taking 1-2 weeks (typical, compiled from published rate guides). At Fame, bookers stopped copy-pasting guest profiles into briefs, a job they do dozens of times a week.
With Zapier, Make or n8n
None of them can add a button to your browser that reads the page you are on, so a pure no-code version is a workaround: a form or a bookmarked link that sends a URL into a flow. That can work for low volume. If the team captures 400 profiles a month through a five-step flow, that is about 2,000 Zapier tasks ($49 a month on Professional, billed annually) or 400 n8n executions (inside the €20 Starter plan).
With custom code from a freelancer or agency
Expect something in that $2,000-5,000 (£1,600-4,000) range, built in 1-2 weeks. Then plan for upkeep: browser extensions need updating when browsers and the sites you capture from change.
With Forge
The ops audit ($2,500 / £2,000) is credited to month one, and the extension can be the first build included in your plan. On the $2,000 / £1,600 plan, the 3-month minimum is $6,000 / £4,800 in total, and we keep it working after that. For one small extension on its own, a one-off build is cheaper. Our plan makes sense when the extension is one of several tools you want built and looked after. See all prices.
Across all of Fame's tools, the team got back 5,460 hours as of 14 October 2026. For how platform fees and consultant fees add up, see our automation consultant rates guide.
Questions, answered plainly
Is Make or Zapier better?
Zapier is easier for simple flows between popular apps. Make handles branching, loops and data reshaping better on its visual canvas. Choose by how complex your flows are and who will look after them.
Why use n8n instead of Zapier?
Price at volume and flexibility. n8n counts a whole workflow run once, while Zapier counts every action step, so many-step flows that run often are much cheaper on n8n. n8n Cloud starts at €20 a month for 2,500 executions, billed annually.
Is Zapier outdated?
No. It is still the easiest way to connect popular apps without code. It gets expensive for many-step flows at volume, and complex logic is hard to follow, which is when teams look at n8n or custom code.
What to use instead of Zapier?
Make for visual, branching flows; n8n for high-volume or many-step flows on a budget; custom code for workflows central to client delivery or that need a real screen.
How long can I use Zapier for free?
Zapier's Free plan has no time limit. It includes 100 tasks a month and two-step Zaps only. Paid plans start at $19.99 a month billed annually for 750 tasks.