I Replaced Zapier with n8n for 12 Clients — Here's What Actually Happened

I've been migrating small business clients from Zapier to self-hosted n8n over the past year. The cost difference is dramatic — but it wasn't all sunshine. Here's the honest breakdown of what worked, what broke, and what I'd do differently.

Why I Even Considered the Switch

The trigger was simple: I kept seeing clients paying $200-500+/month for Zapier to run 8-15 basic workflows. Lead capture, CRM sync, appointment reminders, weekly reports. Nothing that actually needs a premium SaaS platform.

When I started mapping out what these workflows actually do — webhook trigger, transform data, HTTP request — I realized n8n on a $20/month VPS could handle all of it. The math was too obvious to ignore.

The Migration: 3 Patterns That Kept Repeating

After migrating multiple clients across industries (real estate, clinics, e-commerce, law firms), I noticed three patterns:

Pattern 1: The "Simple" Workflows Were Actually Simple

About 60% of workflows were straightforward: webhook trigger → transform data → HTTP request to CRM/WhatsApp. These migrated in under 30 minutes each.

// n8n webhook → WhatsApp notification (simplified)
{
  "nodes": [
    {
      "name": "Webhook",
      "type": "n8n-nodes-base.webhook",
      "parameters": {
        "path": "new-lead",
        "httpMethod": "POST"
      }
    },
    {
      "name": "Send WhatsApp",
      "type": "n8n-nodes-base.httpRequest",
      "parameters": {
        "url": "https://waha-api.example.com/api/sendText",
        "method": "POST",
        "body": {
          "chatId": "={{$json.phone}}@c.us",
          "text": "New lead: {{$json.name}} - {{$json.email}}"
        }
      }
    }
  ]
}

Pattern 2: Zapier Multi-Step Workflows Became Single n8n Workflows

In Zapier, complex logic requires multiple Zaps chained together. In n8n, one workflow handles everything with IF/Switch nodes.

Example — lead routing:

• Lead comes in from form
• IF budget > ₪10K → assign to senior agent + send premium template
• ELSE IF returning customer → assign to their previous agent
• ELSE → round-robin assignment + standard template
• ALL paths → log to Google Sheets + notify on WhatsApp

In Zapier, this needs multiple Zaps. In n8n: 1 workflow, no extra cost.

Pattern 3: Error Handling is Where n8n Destroys Zapier

Zapier's error handling is binary: retry or stop. n8n gives you:

• Error triggers that catch failures and route them
• Retry with backoff on specific nodes
• Dead letter queues for manual review
• Custom error notifications via WhatsApp/email

// n8n error workflow — notify on WhatsApp when any workflow fails
{
  "name": "Error Handler",
  "type": "n8n-nodes-base.errorTrigger",
  "position": [250, 300]
}
// → Format error message → Send WhatsApp alert to admin

Error workflows alone are a game changer — instead of discovering failures hours later, you get instant WhatsApp alerts.

The Honest Downsides

I'd be lying if I said the migration was painless. Here's what actually went wrong:

1. Initial Setup Complexity

Zapier: sign up, connect apps, done. n8n self-hosted: VPS setup, Docker, SSL, reverse proxy, backups. For non-technical users, this is a dealbreaker.

My solution: I handle all infrastructure. Client never touches a terminal. They get a URL, log in, and see their workflows.

2. Some Integrations Don't Exist

Zapier has 6,000+ integrations. n8n has ~400 built-in + community nodes. For some clients, I needed custom HTTP nodes for Israeli CRMs (Priority, Rivhit) that had native Zapier integrations.

Time cost: ~2 hours per custom integration. But once built, reusable across all clients.

3. Updates Require Management

Zapier auto-updates. Self-hosted n8n needs manual updates (or a cron job). I've set up automated updates with health checks — but it's still my responsibility, not Zapier's.

The Cost Difference

The exact savings depend on the client's Zapier plan and usage. But here's the general pattern I've seen:

• Zapier costs scale linearly — every new workflow, every additional task, every premium integration adds to the bill
• n8n self-hosted has a flat cost — one VPS handles multiple clients, and adding workflows costs nothing extra
• The biggest hidden saving is that clients start automating more when the marginal cost is zero. On Zapier, they'd think twice before adding a new workflow

For context, Hetzner VPS hosting for n8n starts around $20/month and can handle dozens of workflows across multiple clients.

Who Should NOT Switch to n8n

Let me be clear: n8n isn't for everyone.

Stay on Zapier if:

• You're non-technical and don't have someone to manage infrastructure
• You use 30+ different SaaS tools (Zapier's integration catalog is unbeatable)
• Uptime SLA is critical and you can't manage your own infrastructure
• Your budget is under $50/month (Zapier's free tier might suffice)

Switch to n8n if:

• You're spending $200+/month on Zapier/Make
• You need complex logic (branching, loops, error handling)
• You work with APIs not in Zapier's catalog
• Data privacy matters (self-hosted = your data stays on your servers)
• You have someone technical to manage it (or hire someone like me)

The Tool I Actually Recommend for Most Israeli SMBs

For my Israeli clients specifically, the sweet spot is usually:

1. n8n self-hosted for the automation engine ($20/month VPS)
2. WAHA for WhatsApp API (self-hosted, ~$0 vs Twilio's per-message pricing)
3. Supabase for database (free tier covers most SMBs)
4. Monday/HubSpot for CRM (what the team actually sees)

Total infrastructure cost: $20-40/month vs $500-2,000/month for the equivalent SaaS stack.

---

What's your automation stack? Still on Zapier, moved to Make, or went self-hosted? I'm genuinely curious what the cost difference looked like for your setup.

I'm Achiya, an automation consultant based in Israel specializing in WhatsApp bots and business workflow automation. If you're considering the switch, feel free to reach out. Try n8n — the platform that made all of this possible.