n8n vs Zapier vs Make: who will look after it?
Somebody was told to pick a tool. The demo looked easy, the first workflow worked, and six months later nobody remembers how it runs. This guide compares n8n, Zapier and Make by what each asks of the person who looks after it, how each charges and where your data sits. It also says when you need none of them.
Updated
n8n vs Zapier vs Make: what goes wrong after the demo
Somebody in the firm was told to pick a tool. The demo made it look easy, the first workflow worked by teatime, and everyone went back to their day. The months after that are where the three tools start to differ.
-
Six months on, nobody remembers how it runs
The person who built it knew why step four drops the enquiries from outside your area. They have since moved to other work and the reason went with them. The workflow carries on running, so nothing prompts anyone to look at it.
-
A step fails on a Friday night
Picture a physiotherapy clinic whose online booking form feeds the diary and the reminder texts. An app it connects to changes how it logs in, or a password expires, and the workflow stops, or carries on without the step that failed. The one person who built it is on holiday and nobody else has the login, so the clinic finds out on Monday from a patient who did not get a confirmation.
-
The bill grows with the usage
The first month was small because one form was connected. Then somebody connected a second, and added a step that goes through every line of an order. Each tool counts its work in a different unit, so one workflow can cost very different amounts depending on where it runs. The charging section below shows how.
-
The data now sits on a server nobody chose
Names, phone numbers and notes from customer enquiries pass through the tool. A salon owner who is asked where that information goes may find the answer was settled by whoever signed up first, in a hurry, and nobody wrote it down.
-
n8n vs Zapier, and where Make sits
Zapier, Make and n8n's own cloud all run on the vendor's servers, which asks little of you to start with. Only n8n can also run on a server you look after, and the control and the upkeep both come from that. Zapier and n8n do much the same job, so the choice is ease against control. Set n8n vs Make side by side and the trade is the same, except that Make asks you to learn more of its builder and gives you more ways to branch a workflow and handle errors.
Who is going to look after it?
Picture the person who will look after the tool a year from now. They can be non-technical, but they must be named, hold the logins and read the failed runs on an ordinary Tuesday. The table sets out what each tool asks of that person, as the vendors describe it in November 2026.
| Compare | Zapier | Make | n8n |
|---|---|---|---|
| Who tends to look after it | A person comfortable with web tools, with no server involved | A person who is patient with detail and will learn the builder | A person who runs servers, or one who is happy with n8n's own cloud |
| How it charges | By tasks. Each successful action step counts, triggers and filters do not | By credits. An action a scenario performs usually uses one | Cloud plans by runs of the whole workflow. Self-hosted, no plan fee for the Community edition |
| Where it runs | Zapier's servers. Zapier says it hosts data in the United States | Make's servers, in an EU or US zone your organisation sets | n8n's cloud, in Frankfurt per its pricing page, or a server you choose |
| When a run fails | Shows in Zap history. A Zap that keeps failing switches itself off | Stops and rolls back by default. Incomplete executions, if switched on, wait to be fixed | Shows in the executions list. An error workflow can alert someone, once built |
| Custom code and logic | Code steps in JavaScript or Python | Routers and error handlers in the builder | A Code node in JavaScript or Python |
| AI features | Some actions use more than one task | Some advanced AI features use more credits | Assistant credits are a separate allowance on Cloud |
-
Zapier suits a firm with no technical person
Zapier runs in a browser on Zapier's servers. A failed run shows in your Zap history, and a Zap that errors repeatedly switches itself off. That stops a runaway loop, and it also leaves a broken Zap broken until somebody looks. Its help pages describe an email for each error by default and an optional automatic replay of failed runs, so decide whose inbox those emails reach. The task count is the sore point, because it climbs quickly when a workflow has many steps. If you are torn on Zapier vs Make, ask how much detail you want to handle yourself.
-
Make, for somebody who likes detail
Make also runs on the vendor's servers. By default a failed scenario stops and rolls back, and it cannot be resumed unless somebody switched on incomplete executions, which keep the run waiting for a person to fix it. A scenario that keeps failing is switched off. The learning curve is steeper than Zapier's, and the return is more control over branching and error handling. Whoever has the patience for that should also be the one who reads the incomplete executions tab.
-
n8n, if a technical person is around
n8n shows failed runs in an executions list and can run an error workflow that alerts someone, once somebody has built one. On your own server, n8n's documentation lists configuration, monitoring, logging and updates as the self-hoster's work. That makes hosting weigh as much as features when you compare Make vs n8n. n8n recommends its own cloud service to people without server experience, so a firm that likes n8n's control but has no technical person may do better with that, or with an n8n alternative that Zapier or Make run for you.
-
When a developer is involved
Where the ready-made steps stop, a builder can write custom code in Zapier and in n8n, and use routers in Make. That helps with complex workflows, but it makes them harder for anyone else to read. Ask for a short note beside any code.
-
The person who is away
Get a second person onto the account and register it in the firm's name. Write one page per workflow covering what starts it, what it does and what to do when it stops. Then switch on the failure alerts and choose who receives them, because the usual setting is an email to whoever signed up.
How each one charges, and why the bill grows
Zapier counts tasks, Make counts credits and n8n's cloud counts runs of the whole workflow, as of November 2026. This guide gives no prices, because they depend on your plan and the vendors change them. Each vendor's pricing page is linked at the foot of the guide.
-
Take one workflow and count it
A web enquiry arrives. The workflow checks the postcode is in your area, tidies the name, adds the person to your customer list, sends a confirmation email, posts a note in the team chat and creates a task. That is one starting event, two housekeeping steps and four actions. Say 200 enquiries arrive in a month. Zapier does not count triggers, filters or formatting, so it counts four tasks per enquiry, 800 in the month. Make says an action usually uses one credit, so the tidy-up and the four actions come to at least five per enquiry, 1,000 or more in the month. n8n's cloud counts one run per enquiry, 200 in the month, however many steps it has.
-
Then the workflow grows
Add two more steps, an entry in a spreadsheet and a text to the owner. Zapier now counts six tasks per enquiry and the month moves from 800 to 1,200. Make rises with the extra steps in much the same way. n8n's cloud still counts 200 runs. Now turn it round. A workflow that wakes every few minutes to look for news is a run each time on n8n, as we read its pricing page, whether or not it found anything, while Zapier says it does not count polling checks. Which tool counts fewer depends on the shape of the workflow.
-
What happens at the end of the month
Zapier either stops at your limit or carries on at a higher rate, depending on a pay-per-task setting that somebody has to choose. Make stops scenarios when credits run out, and queues incoming webhooks until you add more. Check what n8n does at your plan's limit before you rely on it. Whichever tool it is, decide who gets told and who decides.
-
Where AI features are metered
All three now sell AI features, and each puts them on its own meter. Make says some advanced AI features use more credits, n8n lists assistant credits separately, and Zapier says some actions use more than one task. If an AI step is part of the plan, ask what a run costs with it in.
-
The part of the bill nobody invoices
Running n8n on your own server removes the plan fee for the Community edition, which is free to use for your own business. It adds a server to keep patched and monitored, backups, and the time of whoever answers when it stops. That can come out cheaper or dearer, depending on how many runs you have and whose time you count, so work it out with your own figures. The Community licence covers using n8n for your own organisation, and who may build workflows on your instance is a licence question, so read the terms before outsiders get access.
Where your data sits, and who answers for it
A customer's name, number and enquiry pass through whichever tool you choose. Where that tool runs is a question to settle before the first workflow, when it costs nothing to answer.
-
On the vendor's servers
Zapier's data privacy page says it hosts data on AWS servers in the United States and does not support an EU-only option. Make sets a data zone for each organisation, and its help pages describe EU and US zones, with a note that some AI features are processed in the US even in an EU zone. n8n's pricing page says its hosted plans store data in the EU, in Frankfurt. Vendors change these, so check the page on the day you decide.
-
On a server you look after
Of the three, only n8n offers this. Its documentation says it runs on your own infrastructure, on premises or in a private cloud, and the data sits where you put it. A server in your own account does not settle your data protection duties by itself, because somebody still decides who can log in, what is backed up and how long records are kept.
-
Every tool keeps a record of each run
That record usually holds the customer details that passed through. Zapier's data privacy page describes a monthly clean-up of old run history, and n8n's documentation describes how long its cloud plans keep saved executions. Ask each vendor what it keeps, for how long, and who in your firm can open it.
-
What customers are told, and what you keep
We help clients meet UK GDPR, the Data Protection Act 2018 and PECR requirements, in the places where their customers are. That covers what customers are told, consent, how long records are kept, who can read them and where the data sits. It is part of setting up a workflow, and we do not sell it separately. Meeting the rules stays your business's own responsibility.
n8n vs Power Automate for a firm on Microsoft 365
If you already pay for Microsoft 365, look at what the licence includes before you compare anything, because part of Power Automate may be in it. How much depends on the licence, and Microsoft's licensing pages say what each one includes.
-
What the licence you have may already include
Microsoft's page on Power Automate licence types, updated on 22 September 2026, says other Microsoft 365 licences include a limited set of Power Automate capabilities. It also says the free licence builds cloud flows with standard connectors only, and that premium connectors need a Power Automate Premium or process licence. Ask whoever manages your Microsoft account what yours includes.
-
Where it fits better
A workflow that starts and ends inside Microsoft's own apps, such as an email arriving in Outlook that should become a task in Teams, is the natural home for Power Automate. The person who looks after it can be the same person who already manages your Microsoft accounts.
-
Where Power Automate does not fit
If the data must stay on your own hosting, that settles n8n vs Power Automate, because Power Automate's cloud flows run on Microsoft's servers and n8n is the one of the two that can be put on yours. A step that needs a premium connector brings in a paid licence, so count how many people will build or run flows before you call it free.
An n8n alternative, or none of the three
People who search for an n8n alternative, or a Zapier alternative, are often after something simpler. For some of them the simpler answer is no automation tool at all.
-
A feature in software you already own
Booking systems send reminders, customer systems move a lead from one stage to the next, and phone systems can email a voicemail. Before you build anything, look in the settings of your booking, accounting, customer and phone software for words like rules or automations. If one of them does the job, use it. We say so when it does.
-
A scheduled export and an hour on Friday
If the job is to get a list from one system into another once a week, a report that is emailed to somebody on a schedule may be enough. Nobody has an extra account or login to look after.
-
A person with a checklist
If it happens twice a month, doing it by hand costs less than keeping a tool alive. Write the steps down once. If you still repeat them in six months, the checklist is already the first draft of the workflow.
-
When one of the three is worth it
It happens most days, it joins two or more systems with no built-in link, a missed step costs you a customer, and somebody is named to look after it. If that sounds like you, the choice between the three comes back to who looks after it and where the data may sit.
Where we come in, and where we do not
We start from the workflow and pick the tool afterwards. We look at the job, who will look after it and where the data has to sit, then say which kind of tool fits, including one you already own.
-
A second opinion before you sign up
Bring the workflow. We compare at least two options, write the choice down in plain words and say why the others were not chosen. If we were ever to earn anything from a vendor we recommended, we would tell you before we made the recommendation.
-
Accounts and logins in your name
The accounts, subscriptions and logins stay in the firm's name. Each workflow comes with a page you keep describing what it does, so you are free to move it or to leave.
-
Phone numbers and messages
We connect your business phone numbers, including your business WhatsApp number, and help set up calls and messages on them, inbound and outbound. Outbound calls and messages go to people who agreed to receive them, with the wording, audience and frequency agreed with you in writing first.
-
Naming the person is your call
We cannot name who in your firm looks after the workflow. Only you can, and it does more for the result than which of the three you pick.
What owners ask before they choose
Plain answers to the questions that come up before anyone picks a tool.
n8n vs Zapier: do we need a technical person for either? You can start Zapier without one, since it runs in a browser on Zapier's servers, though somebody has to own the account and read the failures.
You can start Zapier without one, since it runs in a browser on Zapier's servers, though somebody has to own the account and read the failures. n8n on your own server needs a person who can run a server, and n8n's documentation recommends its cloud service to people without that experience.
What happens to our workflows if the person who built them leaves? They keep running until something changes, and then nobody knows why.
They keep running until something changes, and then nobody knows why. A second person with the login, the account in the firm's name and a page describing each workflow mean the next person can pick it up.
Can we start on one tool and move to another later? Usually, but each tool stores workflows in its own way, so moving means rebuilding more often than copying.
Usually, but each tool stores workflows in its own way, so moving means rebuilding more often than copying. Keep a plain description of each workflow, and the accounts in your own name, so you are free to leave.
Can we try one before we commit? Yes: Zapier and Make each list a free plan, and n8n's Community edition is free to run on your own server, all as of November 2026.
Yes: Zapier and Make each list a free plan, and n8n's Community edition is free to run on your own server, all as of November 2026. A trial shows you the builder rather than a failed run, so try one low-stakes workflow and look at what happens when it breaks.
We have a developer. Does that change the choice? It does, mostly towards n8n and the code steps in all three.
It does, mostly towards n8n and the code steps in all three. You then depend on that developer, so you still need to know who looks after the workflow when they are away.
Seven questions before you pick a tool
Put these to whoever is choosing, including us, and write the answers down.
- 1.How many workflows do you need now, and how many in a year?
- 2.How many steps does the busiest one have, and how often does it run?
- 3.Who looks after it, who covers when they are away, and where are the logins kept?
- 4.Where must customer details sit, and who can open the record of each run?
- 5.What do you already pay for that might do the job?
- 6.What does each tool's charging unit do to your busiest workflow, with your own numbers?
- 7.How would you leave, and is the account in the firm's name?
Continue with the decision you need
Each page below picks up one point from this guide.
General information for owners of small UK firms weighing n8n vs Zapier vs Make. The situations in it are ordinary examples, not clients of ours. It ranks no tool and quotes no prices, and product details are as of November 2026. Meeting data-protection rules stays your business's own responsibility.
Bring us the workflow first
Tell us the job you want done, who would look after it and what you already own. We say which kind of tool fits, including one you already pay for, and if the answer is none of the three we say that too.