n8n vs Zapier — when to pick which.

You have 5+ flows, need branching/loops/code, run more than 5K tasks/month, need self-hosting for HIPAA or data residency, or want to ship automation as a service to your own clients.

You have 1–3 flows, zero engineering capacity, your stack is mainstream SaaS (Gmail, Slack, Sheets, Stripe), task volume is under 2K/month, and you'd rather pay than maintain.

Scenario 1: "I have one marketing flow and zero engineering"

You're a solo founder or small marketing team. You want new HubSpot leads to land in a Google Sheet, trigger an internal Slack notification, and send a welcome email via your ESP. That's it. You don't want to think about hosting, you don't want to write code, you don't want to fix queue mode in six months when traffic doubles.

Zapier wins this cleanly. The UI is the friendliest in the category. The connector for HubSpot, Google Sheets, Slack, and your ESP is one click each. You'll build the flow in 25 minutes and forget it exists. The premium for not thinking about infrastructure is worth it at this scale. If you're processing under 750 tasks per month, the cost is trivial.

Scenario 2: "I have 12 internal ops flows and 1 dev"

You're a 20-person company. Ops, sales, support, and finance all want their own automations. Lead routing, invoice processing, support ticket enrichment, CRM hygiene, weekly reports. Task volume is around 30K/month across the lot. You have a developer who can help maintain but who has bigger product work to ship.

n8n wins this. Self-host on a small Hetzner VPS with Docker Compose, Postgres for state, Caddy for HTTPS, and let the developer set up workflow versioning in Git. At 30K tasks/month Zapier would cost roughly 10x what running your own VPS does. The sub-workflow primitive lets you build shared "send Slack alert" or "look up account in CRM" subroutines once and reuse them across 12 flows. By month six, the time saved on DRY refactors pays back the setup investment.

Scenario 3: "I need HIPAA compliance"

You're in healthcare, mental health, or any vertical where PHI flows through your automation. Patient names, appointment data, insurance numbers — anything that would land you in legal trouble if it leaked through an unaudited third party.

Both can do this but the path differs. Zapier Enterprise has HIPAA available with a signed BAA — fast to set up, expensive monthly, no infrastructure questions. n8n self-hosted on your own AWS VPC or HIPAA-compliant hosting (Aptible, OpsCompass) gives you full control of where PHI lives and how it's logged. The right choice depends on whether you're already on AWS — if yes, n8n self-hosted is cheaper and tighter. If you're a small clinic with no cloud team, Zapier Enterprise removes a whole category of risk.

Scenario 4: "I run an agency selling automation as a service"

You're an agency. You sell automation builds to clients ranging from solopreneurs to mid-market. You want a stack where you can ship fast, white-label nothing, and not have your margin eaten by per-task fees flowing through your reseller account.

n8n wins this convincingly. Self-host one n8n instance per client on a cheap Hetzner VPS, or run multi-tenant with isolated databases. Workflows export as JSON which means you can build a library of templated flows ("Stripe-to-Notion lead capture," "Calendly-to-CRM intake") and clone them across clients in minutes. Zapier's per-task billing makes reseller economics painful — every time a client's flows scale, your margin shrinks. GoHighLevel is another agency-friendly alternative if your clients want marketing-focused features.

Scenario 5: "I'm migrating off Zapier — should I"

You've been on Zapier for two years. You have 8–15 Zaps and your monthly bill has crept north of what feels reasonable. You're wondering if the migration tax is worth it.

Honest answer: only if you have at least 5 Zaps, more than 5K tasks/month, and a developer or technically-comfortable operator who can own the n8n instance. Below those thresholds, the migration tax (40–80 hours of rebuilding, testing, and re-credentialing) eats your savings for a year. Above those thresholds, the payback period is typically 3–4 months. Never bulk-migrate — one flow at a time, run both for 48 hours in parallel with a comparison spreadsheet, then disable Zapier. A typical 12-Zap migration takes us about 3 weeks at SkynetLabs.

1. You need a real durable event-driven system

Orchestrating long-running transactions, multi-step sagas, or anything needing strict exactly-once semantics at scale (financial reconciliation, multi-system order fulfillment with rollback)? n8n's queue mode and Zapier's retry logic are both insufficient. You want AWS Step Functions, Temporal, or Inngest — built for production-grade orchestration with proper retry policies, idempotency keys, and state durability.

2. The logic is trivial and you have engineers

If the “automation” is fetch from API A, transform, write to API B, on a cron — that's 40 lines of Python plus a cron job on the smallest VPS your host offers. Wrapping it in n8n or Zapier adds operational overhead for negative engineering value. A Python script with a logging library and a Slack-notify-on-failure handler is the right tool.

3. You're really doing marketing automation

If 80% of what you call “automation” is drip campaigns, lead nurturing, SMS sequences, and pipeline triggers tied to a CRM — Make is more visual-friendly, GoHighLevel bundles CRM + automation + SMS + email + booking, and HubSpot Operations Hub integrates more tightly with HubSpot CRM. n8n and Zapier can technically do these but you'll fight the tool. Pick the platform built for the use case.