n8n vs Zapier vs Custom Code: Picking Your Automation Stack

Every company now runs on automations — and most are running them on the wrong layer. We have built and inherited automation stacks across all three tiers: Zapier accounts with 80 zaps nobody fully understands, self-hosted n8n instances processing tens of thousands of executions a month, and custom queue-backed services doing work no visual tool could survive. Each layer is genuinely right for a band of problems, and the expensive mistakes happen at the boundaries — staying on a no-code tool two years too long, or writing custom infrastructure for a workflow that fires six times a day. Here is the selection framework we actually use, with the numbers.

The Honest One-Paragraph Version

Zapier wins on time-to-first-automation and breadth of pre-built integrations; it gets expensive and opaque at volume. n8n wins on control, cost at scale, and the ability to drop into code mid-workflow; it demands more technical skill and (self-hosted) real ops ownership. Custom code wins when the workflow is the product, when volume gets serious, or when failure genuinely costs money; it loses on iteration speed and requires engineers for every change. Most companies past 20 people should be running two of these tiers deliberately. Almost nobody should be running all three tiers for the same class of problem.

The Selection Criteria That Actually Discriminate

1. Volume — do the math before choosing

This is the criterion with actual arithmetic. Zapier prices per task, and every step in a zap consumes tasks. A modest workflow — trigger, filter, format, two actions — burns 4–5 tasks per run. At 200 runs a day, that is roughly 27,000 tasks a month, which lands you in Zapier tiers costing several hundred dollars monthly, climbing steeply from there. The same workload on a self-hosted n8n instance runs on a $20–40/month VPS with unlimited executions, plus the ops attention it demands. Our rule of thumb: below ~5,000 executions a month, tool cost is noise and you should optimise for convenience; above ~30,000, per-task pricing becomes a line item your CFO asks about, and the n8n/custom conversation is overdue.

2. Error handling — the criterion everyone discovers too late

Automations fail. APIs rate-limit, webhooks arrive twice, a CRM field gets renamed. The question is not whether your stack fails but whether you find out before your customers do. Zapier's error handling is serviceable but shallow: retries and email alerts, with limited mid-flow branching on failure. n8n gives you error workflows (a dedicated flow triggered by any failure), per-node retry configuration, and manual re-execution of a failed run with its original data — that last one is genuinely valuable at 2 a.m. Custom code gives you whatever you build: dead-letter queues, idempotency keys, exponential backoff, alerting into PagerDuty. The deciding question we ask clients: if this workflow silently failed for 48 hours, what would it cost? If the answer is 'mild annoyance', any tier is fine. If the answer is 'lost orders' or 'compliance incident', you need at minimum n8n-with-error-workflows, and probably code.

3. Self-hosting and data control

If workflows carry PHI, financial records, or EU data with strict residency requirements, a self-hosted n8n instance inside your own VPC changes the compliance conversation entirely — the data never transits a third party's infrastructure. Zapier offers enterprise assurances, but 'the data never leaves our network' is a sentence only self-hosting lets you say. This single factor decides the tool for most of our healthcare and fintech clients before any other criterion gets discussed. The honest cost: self-hosting means you own updates, backups, queue-mode scaling, and uptime. Budget a few hours a month of real ops attention, or use n8n's hosted cloud and accept the middle ground.

4. Who maintains it — the political criterion

Zapier's superpower is that operations and marketing people genuinely build and fix their own automations. n8n sits in between: technical operators and developers are comfortable; most non-technical staff are not, especially once a Code node appears. Custom code means every change enters an engineering backlog behind feature work — which is precisely how a two-field change ends up taking three weeks. Match the tier to the team that will actually own the workflow, not the team that builds v1.

Concrete Examples From Our Own Stack

• Lead routing (Zapier-class problem): form submission → enrich → score → route to CRM with Slack notification. Fires 30 times a day, failure costs a slightly delayed follow-up, marketing owns the scoring rules and edits them monthly. Putting this in code would be malpractice — every rule tweak would need a deploy.
• AI content pipeline (n8n-class problem): our own weekly blog automation is an 18-node n8n workflow — scheduled trigger, four content sources fetched in parallel, scoring, two LLM stages with different models, validation, duplicate-check against the live API, publish. It needs branching, custom scoring code, retry logic, and API-key management, and it changes every few weeks. Too complex for Zapier's linear model, nowhere near worth a custom service — this is the n8n sweet spot, and it has run for months at a hosting cost of effectively zero.
• Document processing (code-class problem): a client pipeline ingesting thousands of PDFs daily — OCR, LLM extraction, validation against business rules, ERP writeback. At that volume with money on the line, we built a queue-backed service (BullMQ on Node, Postgres, S3) with idempotency keys, dead-letter queues, and per-stage metrics. An early n8n prototype validated the flow in week one — then we graduated it, because a visual canvas is the wrong place to manage 40 concurrent workers and exactly-once semantics.

That last example encodes our favourite pattern: prototype on the visual tier, graduate deliberately. n8n is a superb way to discover what a workflow should be before hardening it in code.

The Graduation Signals: When to Move to Code

1. You are fighting the tool. Workarounds for loops, state, or branching that would be five lines in a real language. When a third of your nodes are Code nodes, the canvas is costing you, not helping.
2. Volume or concurrency walls. Sustained thousands of executions daily, or long-running steps colliding with platform timeouts — Zapier's per-step limits and even n8n's single-instance defaults have ceilings you will feel.
3. Correctness requirements sharpen. Exactly-once processing, transactional writes across systems, audit trails, idempotency under retries. Visual tools can approximate these; code guarantees them.
4. The workflow becomes product. When customers see its output directly or it sits in the revenue path, it deserves tests, code review, CI, staged rollouts — the whole software discipline that visual tools structurally lack.
5. Change frequency drops, criticality rises. The inverse also matters: a stable, critical workflow gains little from a visual canvas whose main virtue is easy editing. Stability plus criticality equals code.

The 2026 Wrinkle: AI Steps Change the Math

One criterion that barely existed three years ago now shows up in most automation decisions: LLM calls inside workflows. This shifts the calculus in two specific ways. First, cost profiles invert — when a single workflow step costs 2–10 cents in model tokens, the platform's per-task fee stops being the dominant line item, which weakens the cost argument for migrating off Zapier at moderate volumes. Second, and pulling the other direction, AI steps need things visual platforms handle unevenly: prompt versioning, output validation, fallback models when a provider has an incident, and evaluation before prompt changes ship. n8n handles the mechanics well — its LLM nodes plus a validation Code node cover most patterns, and our own content pipeline swaps models per stage — but once you need eval suites and staged prompt rollouts, you have crossed into code territory regardless of volume, because the risk is no longer 'the workflow errored' but 'the workflow succeeded and produced confidently wrong output at scale.' Silent quality failure is a new failure class, and it does not appear in any platform's error logs. Our current practice: AI workflows whose output a human reviews can live on n8n indefinitely; AI workflows whose output flows directly to customers get promoted to code with an eval gate, at any volume.

What We Recommend, By Company Shape

• Under ~20 people, no dedicated engineers for internal tooling: Zapier (or Make) for everything. Your constraint is attention, not task pricing. Revisit at the first three-digit monthly invoice.
• Growing team with technical operators, data sensitivity, or 10K+ executions monthly: self-hosted or cloud n8n as the default tier, Zapier retained only for the marketing-owned periphery. This is the configuration we run internally and deploy most often for clients.
• Anything customer-facing, revenue-bearing, or heavy-volume: custom services with proper queues — prototyped on n8n first if the shape is uncertain.

And a closing opinion that saves money: audit the stack twice a year. Automation sprawl is real — zaps nobody remembers, workflows patching processes that no longer exist. The best automation stack is not the cleverest one; it is the one where someone can tell you, for every workflow, what it does, what it costs, and who fixes it at 2 a.m.

If you want help designing this stack — or an honest audit of the one that grew organically — our AI and automation team builds and operates all three tiers in production.

Ready to put these insights into practice? The team at Fajarix builds exactly these solutions. Book a free consultation to discuss your project.