Make or n8n: which to choose, and when you need neither
Somebody reads ten reviews, decides nothing and builds no automation. Meanwhile both platforms cover eighty per cent of standard tasks identically. Below are four questions giving an answer in two minutes, and a check on whether you need a builder at all.
Somebody reads ten reviews, decides nothing and builds no automation. Meanwhile both platforms cover eighty per cent of standard tasks identically. Below are four questions giving an answer in two minutes, and a check on whether you need a builder at all.
---
The choice people get stuck on before starting
Somebody has decided to automate their processes. They open a search and see two camps: one says a visual builder is simpler and faster, the other that a flexible platform is more powerful and cheaper.
Ten reviews read, nothing decided, no automation built.
This is the case where choosing the tool eats more time than the work. And both options cover eighty per cent of standard tasks, and across those eighty per cent there is no difference at all.
Let us go through where the difference is and what to decide by.
First: do you need a builder
A question worth asking before the choice.
Three categories of task, and only one of them is about these tools.
The task is mechanical, repeats, the rules are firm. "An email arrived with this subject — create a row in a spreadsheet." That is where a flow builder is needed.
The task requires understanding the content. "Read the email and decide whether it is a complaint or an order." Rules will not solve that — an AI agent or an assistant is needed.
The task is producing content or documents. "Turn the content plan into a month of carousels." Here you need not a flow builder but a chain with generation, where each step's result feeds the next.
The practical conclusion: a substantial share of what sends people to builders gets solved by ready assistants or chain templates. Check that before you start choosing between two platforms.
A visual builder: when
What it is. You assemble a flow with the mouse from ready blocks. Each service is a module, with arrows between them.
Strengths:
The lowest barrier to entry. Somebody makes their first working flow in an hour with no preparation.
Visibility. The diagram is visible whole, it can be shown to a client and explained in two minutes.
There are plenty of ready integrations with popular services, connected in a couple of clicks.
Weaknesses:
Complex logic on a canvas becomes unreadable. A dozen conditions and branches turn into a web you yourself will not understand in a month.
You pay for volume of operations as it grows. At large flows that becomes a noticeable line item.
Anything non-standard hits a ceiling: if there is no ready block, getting around it is hard.
Who it suits: people starting out; people building flows for clients that they have to explain; people with standard tasks and modest volumes.
A flexible platform: when
What it is. The same visual assembly, but with the ability to write logic where the ready blocks fall short.
Strengths:
There is practically no ceiling. Anything missing gets written.
It can be deployed on your own infrastructure. For companies with data requirements that is not an advantage but a condition: the information does not leave the building.
At large volumes the economics are better — you pay for infrastructure rather than per operation.
Weaknesses:
The barrier is higher. Not programming, but not two clicks either.
Deploying it yourself means updates, compatibility and breakages are now your concern.
It is harder to show and hand over to a client.
Who it suits: people with large volumes; people working with sensitive data; people who have hit the builder's ceiling.
How to choose in two minutes
Four questions. The answers give a decision with no reviews read.
Are you doing this for yourself or to sell? For yourself, take whichever you will learn faster. To sell, take what you can hand over and explain to a client.
How many operations a month? Hundreds — there is no difference in money. Tens of thousands — do the sums.
Is there data that must not leave the building? If yes, the question is closed: you need what deploys on your own infrastructure.
Are you prepared to work things out when there is no ready block? No — the visual builder. Yes — the flexible platform.
And a general rule: start with the simpler one. Move when you hit a specific named constraint — "there is no block for this", "too expensive at this volume". "People say the second one is more powerful" is not a constraint.
The rule that matters more than the choice
Describe the process first, build second.
If a process gets done differently every time, a flow will cement that state and make it harder to fix. Automated chaos is chaos that now also runs by itself.
Describe it in words: what happens, where it comes from, what has to come out, what the exceptions are. If you cannot describe it, it is too early to automate, and the platform has nothing to do with it.
The second rule: any flow has to be able to report an error. A flow that broke silently is the worst scenario: you spend a week thinking the process is running when it has stopped.
What people actually buy
Here is the money side, and the conclusion is unexpected.
The client does not care what you built it on. They are buying not a platform but the fact that enquiries stopped getting lost and the report arrives by itself.
Two things follow from that.
The choice of tool is your internal business and does not need discussing with a client. The conversation is about the result.
But transferability matters. If the client wants to change something themselves in a year or hand it to another contractor, the diagram has to be readable. That is an argument for the more visible option on client projects, even if you personally prefer the other.
The price range. By my scrape of 848 listings: a system or pipeline — $490–1 460, against a $30–75 median for one-off work. Those are different units: there an operation, here a result with stages and a handover.
What is available on the platform
Automation templates — more than 3 000 ready flows. Before choosing a platform, check whether what you need has already been built. Most tasks are standard.
The descriptions are open to everyone, the ordinary templates come with the Plus plan, advanced ones with Full.
AI Workflow — if the task is not about connections between services but about production: chains where each step's result becomes the next one's input. Thirteen ready templates, blocks for conditions, loops, an iterator and approval. The quote is visible before the run.
Scheduled and webhook-triggered runs — the Full plan.
More than 140 AI assistants across 14 categories — if the task needs understanding rather than a rule. From the Basic plan.
The "AI agents" express course — twenty ready projects across four platforms. $9, included in the Make and Team plans. Not in the three free days of Basic.
Registration is free and opens three days of full Basic access.
Where to start today
One action, and it is not about choosing a platform.
Start a list of tasks you did by hand more than once this week. Keep it for a week, automating nothing.
After a week look at the list and answer one question about each task: is this a rule or an understanding?
Rules go to a builder, any of them. Understanding goes to assistants. And only after that does it make sense to think about which platform to open.
---
The blunt comparison from the course
In the programme the two platforms get compared directly, with no diplomacy.
Data handling. Make processes data one bundle at a time; n8n works with whole arrays. At large volumes that is a fundamental difference in speed and in how the logic gets written.
The phrasing that explains everything else: Make is renting a flat, n8n is building your own house.
What follows in money terms. Large businesses fear two things: leaks and bills from cloud platforms where every action is metered. Deploying n8n on a client's server via Docker gives them unlimited automations for a fixed $5–10 a month.
What Make gives in return. Speed of entry and ready connections. The phrasing from the course: 99% of companies are not served by template bots, they need bespoke flows, and those fetch from $1 500.
What is in each archive
Choosing a platform is also choosing a library.
Make: more than 1 000 ready AI agents in the aggregator, CRM integration templates, and fourteen Legacy agents with blueprint files — from a quote assistant to an extended business setup.
N8N: more than 500 templates, RAG agent templates, the sales department monitoring system, LinkedIn lead generation, a base of 132 000 business cases.
Undecided — the "AI agents" express course at $9 gives you four platforms at once: Make, n8n, Relevance and Lindy.
---
What to read next
[n8n and Make automation templates](/en/blog/n8n-automation-templates-guide) — a full breakdown of both platforms.
[Three automations people buy](/en/blog/three-automations-that-sell) — what is actually worth building.
[What AI agents are, in plain words](/en/blog/what-are-ai-agents-basics) — when rules cannot cope.
[Build once, run always](/en/blog/build-once-run-always) — the alternative if the task is about production.