Make to n8n

Moving from Make to n8n: when it's worth it

Make bills per module, n8n bills per run. That's not why you move. The reason is what your flow does when it can't run at all.

I move a scenario when Make is getting in the way of the work. If you are already on n8n, and the question is whether a flow needs an agent node, that is in n8n AI agents.

When to move

When I move a scenario

The bill is a clue. It is not the reason. I move a scenario when one of these is true.

01

Ops cost is climbing

More modules means more places it can stop, and more time spent keeping it alive. When that cost is climbing and the flow is not getting simpler, I look at n8n.

02

Self-hosting or a code step

You need the workflow on your own server, or a step that is a short bit of code. Those are reasons I move it. A simple scenario that needs neither can stay.

03

An AI agent node

The next step depends on reading something and deciding. n8n has an agent node for that. I only add it where a person is reading, judging, or drafting.

04

A proper error workflow

You want a named path for a failed run, not a red mark on a screen nobody opens. I switch an n8n error workflow on before the new flow takes live work.

When to stay

When I leave it in Make

A few simple scenarios that just work can stay in Make. If the team is happy there, I leave them. Moving a flow nobody is struggling with only gives you a new place for it to fail.

The move

How the move goes

I do not switch Make off and hope. The n8n flow has to earn the job.

01

Audit the scenarios first

I list what each scenario does, which apps it touches, and who notices if it stops. If I cannot explain it, it stays in Make.

02

Run both side by side

I rebuild the scenario in n8n and run both side by side. Make stays paused as the fallback. If the n8n version is wrong, I turn Make back on.

03

An error workflow from day one

The n8n error workflow is on before the flow takes live work. A failed run goes to one named person. I do not wait for the first quiet weekend to add it.

04

A green run with 0 items

A run can finish green and still have done nothing. Nothing errored, and nothing happened. I check the item count, not just the status.

One case

A quiet weekend

A hotel group's staff bot went quiet over a weekend, and how I watch for that is in automation monitoring.

FAQ

Questions I get asked

Is n8n cheaper than Make?

Make bills per module and n8n bills per run, so which one costs less depends on the scenario. I will not put a number on it until I have seen the flows. A smaller bill is not why I move one.

Can I keep Make running while we move?

Yes. I rebuild in n8n and run both side by side. Make stays paused as the fallback, so you can turn it back on if the new flow is wrong.

What breaks when you migrate?

The connections have to be made again, and a filter or a router does not arrive unchanged. The quiet break is a green run with 0 items. Nothing errors, and nothing happened. I check item counts, not just the status.

Do I have to move every Make scenario?

No. A few simple scenarios that just work can stay, and so can a team that is happy in Make. I move a scenario when the ops cost is climbing, or you need self-hosting, a code step, an AI agent node, or a proper error workflow.

Get in touch

Precision, then PowerFlow

Precision is the $300 audit. I look at the scenarios and say which ones should move. PowerFlow is the $700 pilot, once we know which ones. Same two packages as on the homepage.