How to Migrate from Zapier to n8n in 2026 (Step-by-Step Guide)

Zapier bills you per task — one successful action step — while n8n bills per whole-workflow execution, no matter how many steps that run contains. That single difference in billing model is why so many automation builders re-examine their stack in 2026, especially once a workflow grows past half a dozen steps. Be clear on one thing before you start: there is no official one-click Zapier-to-n8n importer. This is a manual rebuild, and self-hosted n8n Community Edition costs $0 in software. If you have already compared the platforms in our n8n vs Zapier vs Make breakdown, this guide is the next step — the actual migration.

How This Guide Was Built

This guide was assembled from official vendor documentation and pricing pages only — no hands-on migration was run for it, and every figure that appears is quoted from the source linked beside it. The primary sources are Zapier pricing, Make pricing, n8n pricing, the n8n community license, and the n8n Docker install docs. Where a vendor states a claim about its own product, that is labelled as a vendor-published figure rather than an independent measurement.

Prerequisites

The prerequisites are a Zapier inventory, a chosen n8n hosting path, a credentials list, and a manual-rebuild mindset. n8n has no official one-click Zapier importer, so every workflow is rebuilt on the n8n canvas using your Zapier setup as a blueprint, and every connected service must be re-authorized inside n8n (n8n pricing). Before you open n8n, gather four things:

A Zapier inventory. Every Zap name, its trigger, its action steps, its monthly run count, and its real task usage.
A hosting decision. n8n Cloud Starter (managed) versus self-hosted Community Edition via Docker.
A credentials list. Every service you will need to re-authorize in n8n’s central store.
A manual-rebuild expectation. Nothing transfers itself; every node is placed by hand.

If you have never opened the n8n canvas, read our n8n getting started guide first, so nodes, the credentials store, and the editor are familiar before you rebuild anything.

Step 1: Export and Inventory Your Zaps

Step 1 is to document every Zapier workflow before opening n8n, because there is no portable automated migration file. n8n imports n8n workflow JSON; it does not read Zapier .zap files, and no mainstream platform imports them natively (n8n workflows). Treat your inventory as documentation, not as a migration file. A spreadsheet with five columns is enough:

Zap name	Trigger	Action steps	Monthly runs	Zapier tasks

Then apply the formula every step-based platform uses:

Zapier tasks = monthly runs × action steps

One nuance matters when you fill in the last column. Per Zapier’s task usage documentation, a task is one successful action step — triggers cost zero tasks, and built-in tools such as Filter, Formatter, Paths, Delay and Looping cost zero tasks themselves. Actions that run inside a loop are still billed, so a loop over ten records that performs two actions each is twenty tasks per run, not zero. Get this number right; it is the number you are comparing against n8n.

Step 2: Choose Your n8n Hosting Path

Step 2 is to choose n8n Cloud for a managed start or self-hosted Community Edition for zero software cost and no execution ceiling. n8n Cloud Starter is $20/month billed annually with 2,500 executions; Community Edition is $0 in software cost plus a small VPS, typically $5–12/month (n8n pricing, DigitalOcean pricing, Hetzner cloud). Two paths, and the choice is mostly about maintenance appetite:

n8n Cloud Starter — $20/month billed annually, 2,500 executions. Managed hosting; no server to patch, no volume to back up yourself.
n8n Community Edition, self-hosted — $0 in software cost, unlimited workflows and steps, no execution cap. You pay for infrastructure instead, typically $5–12/month on a small VPS.

One licensing detail is worth reading carefully. Community Edition permits free use, modification, and redistribution for your own internal business purposes or non-commercial personal use under the Sustainable Use License — it is fair-code, not OSI open source (n8n community license). Hosting n8n as a product or service to third parties requires a separate commercial agreement. The code itself lives at n8n on GitHub, and the recommended production install path is Docker or Docker Compose. If containers, volumes, and TLS are new concepts, start on Cloud and move later — the n8n getting started guide covers the editor basics.

Step 3: Map Zapier Building Blocks to n8n Nodes

Step 3 is to translate each Zapier construct to an equivalent n8n node: triggers map to trigger nodes, actions to action nodes, Filter to IF, Paths to Switch, Formatter to Edit Fields or Code, and Sub-Zap to Execute Sub-workflow. The mapping is structural rather than automatic — n8n exposes one node per capability, while Zapier collapses similar logic behind named steps.

Zapier construct	n8n equivalent	Source
Zap trigger	Trigger node	n8n workflows
Action step	Action node	n8n workflows
Filter	IF node	n8n docs
Paths	Switch node or IF branches	n8n docs
Formatter	Edit Fields (Set) node or Code node	n8n docs
Delay	Wait node	n8n docs
Code by Zapier	Code node	n8n docs
Sub-Zap	Execute Sub-workflow node	n8n docs
Webhooks	Webhook node + Respond to Webhook	n8n docs
Zapier Tables / Storage	n8n Data tables or external store	n8n workflows

Anything without a native n8n node is covered by the HTTP Request node, which calls the same REST API your Zapier app was calling behind the scenes.

Step 4: Re-authenticate and Rebuild Your Workflows

Step 4 is to rebuild each workflow node by node and re-authorize every connected service through n8n’s central Credentials store. Zapier OAuth connections cannot be ported, and must be re-authenticated inside n8n (n8n credentials). The practical rhythm that keeps this sane:

Create the credential first, then place the node. Most “node won’t run” errors trace back to a missing or mis-scoped credential.
Build the trigger, run one test event, and confirm the payload shape before adding actions. Zapier abstracted field names; n8n shows you raw JSON.
Add one action at a time and test each. A twelve-node workflow that fails is far harder to debug than a three-node one that fails.
If you self-host, OAuth callbacks need to know your public address — set WEBHOOK_URL and N8N_HOST correctly (n8n environment variables).

Paste your Step 1 inventory table next to the canvas. Checking off rows is what tells you the migration is finished rather than merely working.

Step 5: Configure Polling, Errors, and Hidden Execution Costs

Step 5 is to replace Zapier’s platform-managed polling-and-retry model with explicit n8n patterns: prefer webhook triggers, add IF guards before expensive steps, and wire your own error handling. n8n Cloud bills per workflow execution, so any workflow that runs on a schedule — including a run that finds no new data — consumes one execution each time it fires (n8n pricing). That is the cost trap: before you accept a five-minute polling schedule, ask whether the app offers a webhook. If it does, use the Webhook node and stop paying for empty checks.

When polling is unavoidable, put a cheap IF node immediately after the trigger so downstream steps only fire on real data, and stretch the schedule as far as your business can tolerate. For failures, n8n gives you explicit wiring — an Error Trigger workflow, Continue On Error on individual nodes, and per-node retry behaviour — documented in the n8n error handling guide, instead of an opaque platform-managed retry queue.

Zapier vs n8n Cost Math at 10 Steps and 1,000 Runs

The cost math at ten steps and 1,000 monthly runs is where the billing models diverge: Zapier charges 10,000 tasks, Make charges 10,000 credits, and n8n charges only 1,000 executions, because n8n bills per whole workflow run rather than per step (n8n pricing). The table below uses each vendor’s published list prices, quoted as published on the dates this guide was assembled.

Platform	Unit billed	10-step workflow, 1,000 runs	Entry tier (from)	Source
Zapier Professional	Task	10,000 tasks	$19.99/mo	Zapier pricing
Make Core	Credit	10,000 credits	$12/mo	Make pricing
n8n Cloud Starter	Workflow execution	1,000 executions	$20/mo (annual)	n8n pricing
n8n self-hosted Community	None	0 billed executions	$0 + VPS ($5–12/mo)	n8n community license

Zapier cost ≈ monthly runs × action steps = tasks
Make cost ≈ monthly runs × modules = credits
n8n cost ≈ monthly runs = executions

Two honest caveats. First, on Zapier, 10,000 tasks in a month may exceed a lower plan’s allowance, and over-limit usage is metered per task at a higher rate than in-plan (metered tasks in Zapier). Second, on Make, one credit equals one module action (Make pricing), so a ten-module scenario at 1,000 runs is 10,000 credits. The widely-quoted figure that roughly 100,000 tasks/month can cost more than $500/month on step-based platforms versus about $50/month on n8n Pro is a vendor-published comparison, not an independent audit (n8n execution advantage).

Expected Output

The expected output is a rebuilt n8n workflow that matches your Zap’s trigger and action count, runs once per event as a single execution, and produces the same business result without per-step billing. Your success checklist:

The rebuilt workflow produces the same trigger outcome and the same downstream actions as the original Zap.
One workflow run equals one execution, regardless of node count.
Every service is authorized in the n8n Credentials store, not hardcoded.
The workflow exports cleanly as n8n JSON, so you own a portable copy.

Troubleshooting

Troubleshooting centers on four issues: OAuth redirect misconfiguration, missing volume backup, timezone drift on schedules, and scheduled workloads consuming executions even when nothing changed.

OAuth redirect failures after self-hosting. The provider is still pointing at localhost. Set WEBHOOK_URL (and N8N_HOST) to your public domain and re-create the credential (n8n environment variables).
Workflows vanished after a container restart. The n8n_data volume was not persisted. Mount a named volume so the SQLite database survives container removal (n8n Docker docs).
Schedules firing at the wrong hour. Set both GENERIC_TIMEZONE and TZ to your region (n8n environment variables).
Cloud executions disappearing on empty runs. Convert to webhook triggers or add early IF guards.
Everything broke after a redeploy. The encryption key changed, so stored credentials are unreadable. Back it up alongside the volume.

Next Steps

Next steps are to back up the n8n volume and encryption key, keep Zapier active until your rebuilt workflow matches output for at least one full billing cycle, then retire Zaps gradually (n8n Docker docs). Run both systems in parallel: Zapier keeps the business running while n8n proves itself on real data. Once a workflow has matched output for a full billing cycle, turn off the corresponding Zap and watch your task count fall.

With the migration stable, the obvious next move is to build things Zapier made awkward — starting with our walkthrough on how to build an AI agent in n8n.

FAQ

Is there an official Zapier-to-n8n importer?

No. As of 2026, n8n has no one-click Zapier importer, so every workflow must be rebuilt manually on the n8n canvas using your Zapier setup as a blueprint. n8n imports n8n workflow JSON, not Zapier .zap files (n8n workflows).

Is n8n actually free if I self-host it?

Self-hosted n8n Community Edition is $0 for unlimited workflows and steps for internal business use, but you still pay for your VPS, typically $5–12/month. It is not OSI open source; it uses a fair-code Sustainable Use License (n8n community license).

Does n8n charge per step like Zapier?

No. n8n bills per workflow execution, not per step or node. A 25-node workflow that runs once consumes one execution; a 10-step Zap at 1,000 runs consumes 10,000 Zapier tasks but only 1,000 n8n executions (n8n pricing).

Will scheduled runs consume my n8n Cloud executions?

A scheduled workflow consumes one execution every time it fires on n8n Cloud, whether or not it finds new data. Prefer webhook triggers, or add an early IF guard and stretch the schedule to cut empty runs (n8n pricing).

The Bottom Line

The bottom line is a concrete decision rule: migrate if your Zapier bill is driven by multi-step, high-volume Zaps on a paid plan, and stay if you are on a simple low-volume setup that values zero maintenance over cost. Run the numbers on your own inventory first.

Migrate if you are: running multi-step Zaps on Professional or Team and paying per task, comfortable with either n8n Cloud or a Docker container you maintain, and you want source-visible workflows, per-execution billing, and a portable JSON backup of your automation.

Stay on Zapier if you are: on the Free plan with simple, low-volume Zaps, or a team that values zero maintenance and instant native OAuth over cost savings, or an organization that needs a vendor SLA and official support without running a self-hosted instance.

ToolBrain — tool reviews, LLM comparisons, and AI workflow guides
NiteAgent — AI agent development, frameworks, and production patterns

Cross-links automatically generated from NoCode Insider.