n8n vs Zapier vs custom code for process automation

Zapier is the fastest way to connect two SaaS tools when volumes are low and the logic is simple. n8n suits teams that want visual workflows but need self-hosting, more complex logic or a cost model that does not grow with every step. Custom code is the right choice when the process is business-critical, the rules are complex, or the volume and audit requirements outgrow both.

Most companies do not need to pick one forever. In our experience the best setups mix them: a no-code tool for small glue tasks, and code for the few processes the business actually depends on. This article compares the three on the criteria that decide the outcome, and ends with a framework you can apply to your own processes.

What each option actually is

Zapier

Zapier is a hosted no-code platform. You build "Zaps" from a trigger and a sequence of actions using a very large catalogue of prebuilt app connectors. There is nothing to install or run. It also offers Code by Zapier steps for small snippets when a connector does not do what you need.

n8n

n8n is a visual workflow tool you can either use as a hosted cloud service or run yourself on your own server. Its source code is public, but it is not open source in the OSI sense: it is released under the Sustainable Use License, which allows use and modification for your own internal business purposes, and restricts commercial redistribution. Some features sit in separately licensed enterprise files that need a paid licence key. For most companies automating their own processes, self-hosting the community version is permitted; if you plan to embed n8n in a product you sell, read the licence carefully first.

Make

Make is worth mentioning as a third hosted visual tool, often chosen for its more visual handling of branching and data mapping. It sits between Zapier and n8n in flexibility and, like Zapier, is a hosted service.

Custom code

Custom code means a small application you own: typically Python or Node.js scripts or services, scheduled jobs or serverless functions, a database for state and logs, and a simple dashboard for exceptions. You write the integrations against each system's API directly.

Ease of use and speed to first result

Zapier wins here. A non-technical person can connect a form to a CRM in an afternoon, and the connector catalogue covers most mainstream SaaS tools.

n8n has a steeper learning curve. It exposes more of the underlying data structures, and you will occasionally write JavaScript expressions or a Code node. A technical operations person can be productive quickly, but it is not quite a no-code tool for everyone. Self-hosting also means someone has to own updates, backups and uptime.

Custom code has the slowest start. Even a simple integration needs a developer, a deployment target and monitoring. The payoff comes later, when the process grows in complexity.

Cost model at volume

We will not quote prices, because they change often. The pricing models matter more, because they decide how cost grows as you scale.

• Zapier charges by tasks. According to Zapier's help centre, a task is a successful action step; triggers, filters and several utility steps do not count. A workflow with five action steps that runs 1,000 times uses roughly 5,000 tasks, so cost grows with both volume and the number of steps.
• Make bills in credits, where most actions, including reading, transforming and iterating over rows, consume one credit each, as described on Make's pricing page. Loops over large lists can use a lot of credits in one run.
• n8n Cloud is priced by workflow executions, where an execution is one full run of a workflow regardless of how many steps it has (n8n pricing). Self-hosting the community edition has no per-execution fee; you pay for the server and the time to run it.
• Custom code has no per-run fee at all. Cost is the build, the hosting and ongoing maintenance.

The practical consequence: a workflow that processes every line of every invoice, every few minutes, can become expensive on per-step pricing, while it costs almost nothing extra to run on self-hosted n8n or in code. Low-volume, high-value workflows rarely justify moving off a hosted tool. To compare properly, estimate monthly runs multiplied by steps per run for each candidate process, and see where it lands in each model. Our article on calculating automation ROI covers the cost side in more detail.

Data residency and GDPR

For European companies this is often the deciding factor.

Zapier states in its data privacy overview that it hosts customer data on AWS servers in the United States. That does not make it unusable under the GDPR, but transfers outside the EU and EEA fall under Chapter V of the GDPR, so you need a valid transfer mechanism, an up-to-date data processing agreement and a record of what personal data passes through each workflow.

Self-hosted n8n and custom code run wherever you put them, including an EU data centre or your own infrastructure. Personal data never leaves your environment unless a workflow sends it somewhere. For health, financial or HR data, we usually recommend one of these two.

Error handling, version control and lock-in

Error handling

All three handle the happy path well. The difference shows when things fail.

• Zapier can automatically replay failed steps a limited number of times and sends error notifications. It does not rerun steps that already succeeded.
• n8n lets you attach an error workflow that starts with an Error Trigger node and receives details of the failed execution, so you can alert, log or compensate.
• In custom code you design it yourself: retries with backoff, idempotency keys so a retry never creates a duplicate record, dead-letter queues, and an exceptions table a person can work through.

The hard part is not retrying. It is knowing what state the process was in when it failed, and making sure a retry does not post the same invoice twice. Code gives you full control over that; visual tools make it possible but harder to reason about as workflows grow.

Version control

Zapier keeps a version history with rollback on its paid plans, but there is no code review in the usual sense. n8n offers Git-based source control and environments on its Business and Enterprise plans; otherwise workflows can be exported as JSON. Custom code lives in Git from day one, with pull requests, automated tests and separate staging and production environments.

If a workflow changes how money moves or what a regulator sees, you want reviewed changes and tests. That is a strong argument for code.

Complex logic and vendor lock-in

Visual tools are excellent for linear flows: when X happens, do Y and Z. They become hard to maintain when you need fuzzy matching, tolerances, multi-step state, large data joins or rules that business users change often. We regularly see workflows with dozens of nodes and nested branches that only one person understands.

Lock-in comes in two forms:

• Platform lock-in: Zapier and Make workflows cannot run anywhere else. Moving means rebuilding.
• Knowledge lock-in: a large visual workflow that nobody documented is as hard to hand over as undocumented code.

n8n workflows can at least be exported and self-hosted, which reduces platform risk. Custom code is the most portable, provided it is documented and written in a mainstream language.

A decision framework

Score each process you want to automate against these questions:

1. Volume: how many runs per month, and how many steps per run?
2. Criticality: what happens if it silently fails for a day?
3. Logic: is it a straight line, or does it involve matching, tolerances and state?
4. Data: does it carry personal, health or financial data with residency requirements?
5. Change control: does a wrong change have audit or financial consequences?
6. Ownership: who will maintain it in two years?

Then apply these rules of thumb:

• Low volume, simple logic, non-sensitive data: Zapier or Make.
• Moderate or high volume, sensitive data, technical owner available: self-hosted n8n.
• Business-critical, complex rules, audit requirements or high volume: custom code.
• Unsure: start in a visual tool to learn the process, then rebuild the parts that hurt.

Hybrid approaches that work

The tools are not mutually exclusive. Patterns we recommend:

• Code for the core, no-code at the edges: the reconciliation engine is code, while notifications to Slack or a CRM update run through a visual tool.
• n8n as the orchestrator, code as services: n8n schedules and routes, and calls small custom APIs for the heavy logic.
• Prototype, then harden: build the first version in a visual tool, measure it, and move it to code once volume and requirements are clear.

For example, the reconciliation system we built for a medical and home supplies distributor runs as scheduled Python functions, because it needed matching logic across an ERP, carrier tracking APIs and SAP, plus a compliance log. You can read the details in the case study and in our guide to invoice reconciliation, build vs buy.

Frequently asked questions

Is n8n really free to self-host?

The community edition can be self-hosted without a subscription for your own internal business use, under the Sustainable Use License. You still pay for hosting and the time to maintain it, and some features such as Git-based source control require a paid plan.

Is Zapier GDPR compliant?

Zapier can be used under the GDPR, but data is hosted in the United States, so you need a valid transfer mechanism and a data processing agreement. Check which personal data flows through each Zap and whether that is acceptable for your organisation.

When should we move from Zapier to custom code?

Common triggers are rising task costs, workflows nobody can safely change, failures you only notice days later, and audit or compliance requirements. If a single workflow has become critical to how money or goods move, it usually deserves proper code, tests and monitoring.

Can we migrate Zapier workflows to n8n automatically?

Not in a reliable, general way. Treat a migration as a rebuild, and use it as a chance to document the process and remove steps that are no longer needed.

If you are weighing these options for a specific process, our business process automation service starts by mapping the process and recommending the simplest approach that will hold up. Book a call to talk it through, or request a quote if you already know what you need.