n8n vs Make.com for Client Automation Work, After Building Both

A client's automation need was moderately complex — pull leads from a form, enrich them against two APIs, apply conditional routing logic, and write to a CRM with error handling for each step. Rather than argue about which tool was better in the abstract, we built the entire thing twice, once in n8n and once in Make.com, and compared the actual build experience and the actual running behavior.

Where n8n won

n8n's code node made the conditional routing logic dramatically easier to express precisely — when the branching got genuinely complex, dropping into a few lines of JavaScript was faster and more maintainable than trying to express the same logic through Make's visual router modules. Self-hosting also gave us full control over execution logs and retry behavior, which mattered for debugging the API enrichment step that occasionally timed out.

The moment logic gets complex enough to want a real conditional, having an actual code node beats fighting a visual builder into expressing the same thing indirectly.

Where Make.com won

• Error handling UI was more intuitive out of the box — Make's built-in error routes were easier to set up without custom logic than n8n's equivalent.
• The visual data mapping between modules was cleaner for non-technical team members to understand and audit later.
• Managed hosting meant zero infrastructure overhead, versus n8n's self-hosted setup needing someone to own uptime and updates.
• Make's connector library for mainstream SaaS tools was slightly more polished and better documented for common integrations.

What we actually recommend now, by project shape

For a client with in-house technical capacity who wants full control and complex conditional logic, n8n's code-node flexibility and self-hosting win. For a client without a technical owner who needs something a marketing ops person can maintain without touching code, Make's visual-first approach and managed hosting are the better fit, even with less raw flexibility. There's no universal winner here — the honest answer depends entirely on who's going to maintain it after we leave, which is the question most tool comparisons skip entirely.