Why I Chose n8n Over Make, Zapier, and Custom Code: 48 Workflows Later

I've built 48 automation workflows over the past year. Some simple email notifications, others complex multi-step processes that sync data across five different tools. After trying Zapier's premium plans, wrestling with Make's visual complexity, and building custom scripts that broke every few months, I settled on n8n.

Here's the breakdown of what I learned, the good and bad of each platform, and why n8n won for my use case.

The Problem: Automation Platforms All Suck in Different Ways

Every SaaS founder hits this wall. You need to connect your tools, but each automation platform has fatal flaws:

Zapier costs $240/month for anything useful. Their "premium" connectors are behind paywalls, and complex logic requires multiple Zaps that eat through your task limits.

Make (formerly Integromat) looks powerful but becomes spaghetti code in visual form. One workflow with 8 steps spans across three screens. Good luck debugging that at 2 AM.

Custom code gives you control but requires maintenance. API changes, authentication updates, rate limiting issues. I spent more time fixing automations than building features.

I needed something that could handle complexity without the visual mess, integrate with niche tools, and not cost me $3,000 per year.

Why I Picked n8n

n8n is open-source workflow automation. You can self-host it or use their cloud service. Here's what sold me:

Cost Structure That Actually Makes Sense

Self-hosted n8n is completely free. Their cloud plan starts at $20/month for 2,500 workflow executions. Compare that to Zapier's $19.99 for 750 tasks or Make's $9 for 1,000 operations.

I'm running 48 workflows on their $50/month plan (10,000 executions). The same load on Zapier would cost me $599/month minimum.

Real Code When You Need It

This is the killer feature. n8n has a "Code" node where you can write JavaScript directly in your workflow. No external functions, no webhook workarounds. Just return [{json: {result: data}}]; and you're done.

Need to transform complex JSON? Parse a weird API response? Handle edge cases? Drop in 10 lines of JavaScript instead of chaining 15 visual nodes.

Decent Visual Flow

Unlike Make's spaghetti, n8n workflows stay readable. The canvas flows left-to-right, nodes connect cleanly, and you can collapse complex sections.

I can open a 20-node workflow I built six months ago and understand it immediately. Try that with Make.

What I've Built: 48 Workflows Breakdown

Here's what my n8n instance handles:

• Lead scoring: Webhook from landing page → enrich with Clearbit → score in Airtable → send to Slack if hot
• Customer onboarding: New Stripe customer → create account in app → send welcome email sequence → add to support Notion
• Content syndication: New blog post → format for Twitter → post to LinkedIn → update RSS feed
• Financial reporting: Daily Stripe data → merge with expenses → update Google Sheets → weekly summary email
• Support automation: GitHub issue → check severity → assign team member → post to Discord

The complexity ranges from 3-node simple notifications to 25-node data pipelines. All running reliably.

The Good Parts

Integration Library Is Solid

400+ integrations covering the major tools. Stripe, Slack, Airtable, Google Sheets, Notion, GitHub, HubSpot, Salesforce. If you use mainstream SaaS tools, you're covered.

The HTTP Request node handles everything else. I've connected it to obscure APIs that have zero native support anywhere else.

Self-Hosting Actually Works

I ran self-hosted n8n for six months before switching to cloud. Docker deployment took 15 minutes. Database backups are straightforward. Updates don't break workflows.

For teams that want control over their automation infrastructure, this is huge. Zapier and Make are black boxes.

Error Handling That Makes Sense

When a workflow fails, n8n shows you exactly which node broke and why. The error log includes the input data, the API response, and stack traces for code nodes.

Zapier's error messages are vague. Make's visual debugging is confusing. n8n just shows you the JSON.

Version Control for Workflows

You can export workflows as JSON files and store them in git. I keep all my workflows in a private repo. When I update a critical automation, I commit the changes with notes.

This saved me twice when I accidentally broke complex workflows. One git revert and I'm back to the working version.

The Frustrating Parts

Node Library Has Gaps

Popular tools are well-covered, but niche integrations are missing. I needed a direct Lemlist connector for email campaigns. Doesn't exist. Had to use HTTP requests and handle pagination manually.

The community builds custom nodes, but finding and trusting third-party integrations is a pain.

Cloud Performance Can Be Slow

Complex workflows with multiple API calls take 30-60 seconds on n8n cloud. The same automation on Make finishes in 15 seconds.

Not a dealbreaker for background processes, but frustrating for real-time workflows that users are waiting on.

Learning Curve for Non-Developers

If you've never seen JSON or written basic JavaScript, n8n will be intimidating. The visual interface helps, but you'll eventually need to understand data structures.

Zapier abstracts this away. n8n expects you to learn it.

Documentation Could Be Better

Node documentation is hit-or-miss. Some integrations have detailed examples, others just list the available fields. The community forum fills gaps, but I've spent hours figuring out simple things.

Direct Comparison: n8n vs the Alternatives

vs Zapier

Cost: n8n wins by 10x
Ease of use: Zapier wins
Power/flexibility: n8n wins
Integrations: Zapier wins (barely)
Reliability: Tie

Choose Zapier if you want simple automations and don't mind paying premium prices. Choose n8n if you need complex logic and want to save money.

vs Make

Visual design: Tie (both good, different styles)
Performance: Make wins
Cost: n8n wins
Debugging: n8n wins
Advanced features: Tie

Make is faster and has better visual debugging tools. n8n is cheaper and more readable for complex workflows.

vs Custom Code

Control: Custom code wins
Speed to deploy: n8n wins
Maintenance burden: n8n wins
Cost: Depends on your time value

Custom code is still the right choice for core product features. n8n is better for operational automations that change frequently.

When n8n Is the Wrong Choice

Don't use n8n if:

• You need real-time performance (under 5 seconds)
• Your team has zero technical skills
• You're only connecting 2-3 mainstream tools
• You need guaranteed 99.9% uptime (self-host instead)
• Your workflows are simple trigger-action pairs

Zapier or Make might be better fits for these cases.

My Setup After 48 Workflows

I'm on n8n cloud's $50/month plan. It handles 10,000 workflow executions, which covers all my automations with room to grow.

My workflows break down into categories:

• Marketing: 15 workflows (lead capture, content distribution, analytics)
• Sales: 8 workflows (CRM updates, proposal automation, follow-ups)
• Operations: 12 workflows (invoicing, expense tracking, reporting)
• Product: 13 workflows (user onboarding, feature usage tracking, support)

The complex ones use 8-15 nodes each. Simple notifications are 3-4 nodes. I've never hit performance issues that affected users.

Bottom Line

After 48 workflows and a year of usage, n8n hits the sweet spot between power and practicality. It's not perfect, but it solves the core problem: connecting your tools without going broke or spending all your time on maintenance.

If you're technical enough to write basic JavaScript and you need more than simple trigger-action automation, n8n is worth trying. Start with their cloud free tier and build a few workflows. You'll know within a week if it fits your brain.

The $600+ I'm saving per month compared to Zapier pays for itself. The time I'm not spending debugging Make's visual spaghetti is bonus.