n8n vs Make: Why I Ended Up Recoding Everything (and How to Choose Your Side)

Low-code automation is marketed as the miracle cure for repetitive tasks. "Save 10 hours a week!", "Zero lines of code!". I took the bait early on. Back then, Make was still called Integromat — before the 2022 rebrand — and I spent entire nights aligning bubbles on a canvas to try and tame my workflows.

Then, I switched to n8n. More flexible, more "dev-friendly". But after building systems for over 25 clients at Allowebs and managing dozens of complex projects at SaniNord, I've come to a conclusion that won't please No-Code fans:

For serious production, nothing beats code.

However, these tools have their place. But before you set your sights on one or the other, let me tell you how the reality on the ground often messes up the beautiful workflow diagrams.

The Mirage of Simplicity: The SaniNord Experience

When I was a commercial project manager at SaniNord, I managed 52 projects across 48 cities. Timing was tight, decisions were made every hour. I tried to implement Make and n8n to streamline everything. The result? A complete failure.

Why? Because the learning curve is treacherous. You think you're saving time, but when you're in the heat of the moment, you don't have three hours to debug a "JSON parse error" on an obscure node. At the time, I wanted to connect our tools to Progression Live to automate field reports. No luck: no API was open at that time.

That's when you realize the first limitation: you are a slave to the ecosystem. If the tool doesn't have a connector or if the API is closed, you're left out. Today, Progression Live has opened its API, but the problem remains the same: do you really want a version update at n8n or a pricing change at Make to break your critical flow in the middle of a busy day?

Make: The Tesla of Automation (with an Expensive Subscription)

Make is visually stunning. It's intuitive, it's clean. But it's a gilded cage.

1. Operation-based pricing: This is the biggest drawback. The more you succeed, the more you pay. If you have a massive volume of data, the bill quickly becomes indecent compared to a small Node.js script that runs for a few cents on a VPS.
2. Rigidity: Trying to do complex logic, nested loops, or advanced data manipulation in Make is like trying to paint a miniature with boxing gloves. You end up creating unreadable "gas factories".

n8n: Freedom (and Getting Your Hands Dirty)

When I migrated from Integromat to n8n, I liked the "Open Source" aspect. You can self-host it, you have complete control over your data. For a dev, being able to inject JavaScript snippets directly into a node is a breath of fresh air.

But be careful: self-hosting has a hidden cost. That of maintenance. I've seen workflows stop dead after an n8n update because a node had changed its structure. In production, this kind of unexpected event is unacceptable when aiming for, as at Allowebs, 99.5% availability.

The Verdict: When to Use What?

So, n8n or Make? If you're not a developer and you want to automate your CRM or social networks, go to Make. The barrier to entry is lower and the interface will save you time... at first.

If you're a technical tinkerer who wants to keep control of your costs and privacy, take n8n. It's the perfect tool for personal processes or quick MVPs.

But for your production systems? Code them.

That's what I did for ConstructoAI and Subvention.app. Why?

• Zero limitations: If I want to integrate a specific ML library or make a convoluted API call, I do it in 3 lines of TypeScript.
• Real scalability: A well-coded script on Vercel or a Node.js server won't flinch if you go from 10 to 10,000 requests.
• Learning: Every technical challenge overcome by coding makes you better. Debugging a bubble on Make doesn't teach you anything about software architecture.

Automation shouldn't be a crutch that makes you dependent on a platform. It's a lever. And for the lever to be solid, you sometimes have to let go of the mouse and pick up the keyboard again.

References

1. Make Pricing & Features — Details on the operation-based billing model.
2. n8n Self-hosted vs Cloud — Comparison of deployment options.
3. Progression Live API Documentation — To see how far it's come since my years at SaniNord.
4. The Rise of No-Code/Low-Code Paradox — In-depth article on why no-code often ends up requiring more code.