THINKING — 03

Make vs n8n: A Builder's Comparison for Business Automation

What Make Is

Make — formerly Integromat — is a visual automation platform built around what it calls a scenario builder: a canvas where modules connect with drawn lines and data flows visually from one step to the next. It is, genuinely, beautiful to look at. The interface is clean, the connections are animated, and the overall experience has been polished over more than a decade of development. Make launched as Integromat in 2012, was rebranded and acquired by Celonis in 2020, and today it sits at the top of the "approachable automation" category.

Make's pricing is operation-based, which is the key thing to understand before committing to it. Every module execution inside a scenario counts as one operation. Their Core plan starts at $9/month for 10,000 operations. The Pro plan is $16/month for 10,000 operations with more features and faster scheduling. That sounds generous until you build a five-step workflow that runs 500 times a day — that's 2,500 operations daily, or 75,000 operations a month. Operations burn fast in multi-step workflows, and that's by design.

What n8n Is

n8n is an open-source workflow automation tool. Its node-based interface is more technical than Make's — you see JSON data flowing between nodes, configuration is explicit rather than guided, and when you need something the UI doesn't cover, you write JavaScript directly in a code node. There's less hand-holding. There's also significantly more ceiling.

Pricing is where n8n becomes interesting. Self-hosted n8n costs nothing after your server, which typically runs $6–10/month on a basic VPS. n8n Cloud starts at $20/month with execution limits, but the self-hosted path removes all operation counting entirely. Run ten million executions a month. It doesn't matter. The server doesn't care.

The Philosophical Difference

This is the real comparison, and it has almost nothing to do with features. Make is a SaaS product designed for non-developers: beautiful UI, opinionated workflow, extensive pre-built integrations, polished onboarding experience. The design philosophy is that automation should be accessible to anyone with a spreadsheet-level comfort with software. n8n is an open platform designed for flexibility: technical, extensible, self-hostable, and willing to expose raw complexity when that's what the problem demands.

If you are a non-developer who wants to automate business processes without hiring someone, Make is probably a better day-one experience. The learning curve is gentler. The error messages are friendlier. The integration library is large and well-documented. You can build a working automation in an afternoon without touching a line of code.

If you are building automation systems that need to scale, integrate with AI, handle sensitive data, or execute complex conditional logic, n8n has more room to grow. The ceiling is essentially the ceiling of what code can do — which is not a ceiling at all.

Side-by-Side Comparison

Where Make Wins

Make earns its reputation in specific contexts. It is not a worse tool — it is a different tool with a different ideal user. The scenarios where Make outperforms n8n are real and worth acknowledging:

• Data transformation and mapping between complex schemas. Make's visual mapper for matching fields between different data structures is genuinely exceptional. Seeing the data flow helps catch mistakes that are invisible in code.
• Google Workspace heavy workflows. Sheets, Docs, Gmail, and Drive integrations are deeply polished. If your business runs on Google, Make's native integrations feel native.
• Non-technical teams who will maintain workflows themselves. If the person building the automation is also the person who will debug it at 9pm when something breaks, the lower cognitive load of Make's interface is a real advantage.
• Quick iteration by non-developers. A Make scenario can be built, tested, and deployed faster than an n8n workflow for someone who is new to automation.
• Businesses where the operator is also the automation builder. Solo founders and small teams who want to connect five tools and move on with their day often find Make's guardrails helpful rather than limiting.

Where n8n Wins

n8n's advantages compound as complexity increases. The more sophisticated the workflow, the more n8n's architectural flexibility matters. It wins decisively in these areas:

• AI agent workflows. n8n has native LangChain integration, vector store nodes, and built-in support for Claude, OpenAI, and other models. Building an AI agent in n8n is a first-class use case, not a workaround.
• High volume workloads. No operation counting when self-hosted. If you're processing thousands of records daily, n8n's economics are dramatically better.
• Security-conscious businesses. Legal, healthcare, and financial services teams often cannot have sensitive data leaving their infrastructure. Self-hosted n8n keeps everything inside your perimeter.
• Complex conditional logic with custom code branches. When the business logic is genuinely complex, being able to write 20 lines of JavaScript to handle an edge case is the difference between a workflow that works and one that doesn't.
• Webhook-heavy architectures. n8n handles high-frequency webhook ingestion cleanly and efficiently at scale.
• When you hit Make's ceiling. Every Make builder eventually hits something Make simply cannot do. In n8n, the ceiling is effectively whatever JavaScript can accomplish — which is essentially everything.

Can You Run Both?

Yes — and some businesses do, deliberately. Make for the marketing team's simpler automations, where the people running campaigns also need to be able to update the workflows without calling someone. n8n for the backend systems: lead routing, AI agents, data pipelines, integrations with internal tools.

This is not a sign of indecision or poor architecture. It is pragmatic tool selection. Using the right tool for the context is exactly what good systems design looks like. The marketing coordinator who runs Make does not need to understand JSON data flows. The developer building the CRM integration does not need the visual canvas — they need the code node.

The cost structure can also make this rational: Make's low-tier plans are reasonable for low-volume, simple workflows, and n8n self-hosted eliminates the per-operation cost for high-volume backend processes entirely.

The Honest Verdict

Make is the better tool if your priority is ease-of-use for non-technical builders. The onboarding experience is better. The visual feedback is helpful. The integrations are polished. For a business owner who wants automation without depth, Make delivers that promise well.

n8n is the better tool if you are building AI-integrated, high-volume, or security-sensitive automation systems. The technical floor is higher, but the ceiling is incomparably higher too. When you need to build something genuinely sophisticated — an AI agent that routes leads based on enriched data, a pipeline that processes thousands of records against a vector database, a webhook architecture that handles real-time events at scale — n8n is where you want to be.

Most businesses we work with start curious about Make and end up running n8n. Not because Make is bad — Make is excellent at what it does — but because the ceiling matters more than it seemed at the start. Growth tends to reveal complexity. Complexity tends to reveal the limits of opinionated tools. When those limits appear, the cost of switching platforms is real. Choosing based on where you want to be in eighteen months, not where you are today, is usually the right frame.

If you are genuinely unsure which fits your situation, the question to ask is: who will maintain these workflows in six months, and what will the volume look like? The answers to those two questions will tell you almost everything.