A Zapier to n8n migration is a rebuild, not an import: n8n has no Zap importer. List every Zap with its trigger, actions and monthly tasks, map each step to an n8n node with the cheat sheet below, rebuild the lowest-risk Zap first, and run both tools side by side before switching the Zap off. Three Zapier features have no direct n8n equivalent: Digest, Email Parser and the long tail of app connections.
A Zapier to n8n migration is a rebuild, not an import: there is no Zap importer, so you list your Zaps, map each step to its n8n node, rebuild them one at a time and run both tools in parallel before you switch anything off. Most steps have a one-to-one equivalent; three Zapier features do not, and they are the ones to plan around.
Updated 11 October 2026 and checked against Zapier's pricing page, its built-in tools directory and help articles on exporting Zaps and replaying runs, n8n's docs on export and import, executions, publishing and the expression reference, the n8n pricing page, and the node list in the source of n8n 2.42.6. Node names and expressions were checked against those sources, not executed.
This guide assumes the decision is made. If you are still weighing it, read n8n vs Zapier first, because plenty of teams are better off staying. It is part of our n8n hub, and it replaces a short 2025 version of this page that cited third-party time estimates and a converter tool we could not verify.
How a Zapier to n8n migration works
Every migration that goes well follows the same six stages. The order matters more than the speed: the parallel run is what turns a rebuild into a safe switch.
- 01Inventory
Every Zap: trigger, actions, filters, paths, apps and tasks a month.
- 02Map
Each step to an n8n node. Flag anything with no equivalent.
- 03Set up n8n
Cloud or self-hosted, credentials for each app, an error workflow.
- 04Rebuild
One Zap at a time, lowest risk first, tested node by node.
- 05Parallel run
Zap and workflow side by side, with n8n writing to a test target.
- 06Cut over
Point n8n at the real targets, turn the Zap off, keep it for rollback.
Why move at all is usually the bill. Zapier counts a task for every successful action, so a Zap with four actions uses four tasks a run. n8n counts one execution for the whole run. The same Zap, rebuilt, uses a quarter of the units, and on a self-hosted instance there is no unit at all.
Illustrative volume. For scale: Zapier Professional starts at 750 tasks for $19.99 a month billed annually, and n8n Cloud Starter includes 2,500 executions for €20. Source: counting rules and plan allowances from zapier.com/pricing and n8n.io/pricing, checked October 2026
Step 1: inventory your Zaps before you migrate Zapier to n8n
You cannot plan a rebuild from memory. Zaps written two years ago by someone who has left are exactly the ones that break in a migration.
- On a Team or Enterprise account, export them. Zapier's help center says these plans can download all Zaps as a JSON file from Settings, under Security and data, in the Data management section. n8n cannot open that file, but it is a complete list of steps and apps.
- On Free or Professional, there is no export. Open each Zap and write it down. A spreadsheet with one row per Zap is enough.
- The trigger app and event, and whether it is instant or polled
- Each action in order, with the app it calls
- Filter, Paths, Formatter, Delay, Looping, Digest and Storage steps
- Any Code by Zapier step, with the code copied out
- Tasks used last month, from Zap history
- Who owns it and who notices when it stops
- Whether each app has an n8n node, or only an API
- A risk grade: could it run twice or miss a day without harm?
Sort the list by risk, then by tasks. The low-risk, high-task Zaps go first: they prove the method and cut the bill fastest. Anything that touches money, customers or legal notices goes last.
Step 2: translate the concepts
Most confusion in the first week comes from words that almost mean the same thing. This is the dictionary.
| In Zapier | In n8n | What to know |
|---|---|---|
| Zap | Workflow | One workflow can hold several triggers and many branches |
| Trigger | Trigger node | App triggers, Webhook, Schedule Trigger, n8n Form Trigger |
| Action | Node | Each node runs once for every item it receives |
| Task | Execution | Zapier counts each successful action; n8n counts one per full run |
| Zap history | Executions | Every run keeps the input and output of each node |
| Turning a Zap on | Publish | Edits save as a draft automatically; nothing goes live until you publish |
| App connection | Credential | Created once, reused by every node for that app |
| Mapping a field | Expression | Drag the field in, or type {{ $json.email }} |
| Autoreplay | Retry On Fail, Retry execution | Retries are set per node; a failed run is retried from the Executions list |
| Error email | Error workflow | A separate workflow that starts with the Error Trigger and alerts you |
| Update time (polling) | Poll Times on the trigger | You set it per trigger; polls that find nothing are not counted |
Two rows deserve a warning. Publish: since n8n 2.0 a workflow that runs perfectly when you select Execute workflow still does nothing on its own until you publish it, and edits you make afterwards stay in draft until you publish again. Items: if a trigger returns ten rows, every node after it runs ten times within the same execution. That is why Looping by Zapier usually maps to nothing.
Zapier n8n equivalent nodes: the 30-step cheat sheet
Thirty Zap steps that turn up in most accounts, with the node that replaces each. The left column uses Zapier's names for its built-in tools; the middle column uses the node names in n8n 2.42.6. This is a selection of common building blocks, not a usage ranking.
| Zapier step | n8n node | Notes |
|---|---|---|
| Webhooks by Zapier: catch a hook | Webhook | Test and production URLs differ. Update the sender once you publish |
| Webhooks by Zapier: send a request | HTTP Request | Import cURL fills in the fields from an API doc example |
| Schedule by Zapier | Schedule Trigger | Check the workflow timezone. Every firing is one execution |
| Filter by Zapier | Filter, or If | Filter drops items; If gives you a true and a false branch |
| Paths by Zapier | Switch | One output per rule, plus an optional fallback |
| Formatter by Zapier: text and numbers | Edit Fields (Set) with expressions | See the expression table below |
| Formatter by Zapier: dates | Date & Time, or an expression | Dates are Luxon objects: $now, $today, .format(), .plus() |
| Delay by Zapier | Wait | For an interval, until a set time, or until a webhook call |
| Looping by Zapier | Usually nothing | Nodes already run once per item. Use Loop Over Items only for batches |
| Code by Zapier | Code | JavaScript, and Python where task runners are set up |
| Sub-Zap by Zapier | Execute Sub-workflow | Sub-workflow runs do not count toward the Cloud quota |
| Storage by Zapier | Data table | Insert, get, update, upsert and delete rows from the Data Table node |
| Zapier Tables | Data table | Or keep the data where it lives and use Google Sheets or Airtable |
| Zapier Forms | n8n Form Trigger | A hosted form whose submission starts the workflow |
| Email by Zapier, SMTP by Zapier | Send Email | Needs an SMTP credential of your own |
| IMAP by Zapier | Email Trigger (IMAP) | Reads a mailbox you control |
| RSS by Zapier | RSS Feed Trigger | Polls the feed on the schedule you set |
| AI by Zapier | Basic LLM Chain, or AI Agent | Connect a chat model sub-node; tokens are billed by the model provider |
| Human in the Loop | Slack: Send and Wait for Response | The run pauses until someone answers in the channel |
| Gmail | Gmail Trigger, Gmail | The trigger polls. Sign in with Google on Cloud; your own OAuth app when self-hosted |
| Google Sheets | Google Sheets Trigger, Google Sheets | Appending a row is one node, not a task |
| Google Calendar | Google Calendar Trigger, Google Calendar | Same Google credential rules as Gmail |
| Slack | Slack Trigger, Slack | Posting a message needs a Slack credential with the right scopes |
| Notion | Notion Trigger, Notion | Share the database with your integration first |
| Airtable | Airtable Trigger, Airtable | Uses a personal access token or OAuth |
| HubSpot | HubSpot Trigger, HubSpot | Contacts, companies, deals and tickets |
| Typeform | Typeform Trigger | Starts on each new submission |
| Stripe | Stripe Trigger, Stripe | The trigger registers the webhook for the events you pick |
| Calendly | Calendly Trigger | Starts when an invitee books or cancels |
| Facebook Lead Ads | Facebook Lead Ads Trigger | Starts on each new lead from a form |
For an app that is not in the table, search the nodes panel in the n8n editor. If nothing comes up, the HTTP Request node is the general answer: paste a curl example from the app's API documentation into Import cURL and n8n fills in the method, URL, headers and body. Our n8n webhook guide covers the receiving side.
Formatter steps as n8n expressions
In Zapier, cleaning up a field is a separate Formatter step. In n8n it is an expression typed into the field that needs the value, or collected in one Edit Fields (Set) node near the start of the workflow. Everything inside the double braces is JavaScript with n8n's helper methods added.
| Formatter job | n8n expression |
|---|---|
| Capitalise a name | {{ $json.name.toTitleCase() }} |
| Clean an email address | {{ $json.email.trim().toLowerCase() }} |
| First name from a full name | {{ $json.full_name.split(' ').first() }} |
| Pull an email out of text | {{ $json.message.extractEmail() }} |
| Find and replace | {{ $json.title.replace('Draft: ', '') }} |
| Default when a field is empty | {{ $ifEmpty($json.company, 'Unknown') }} |
| Text to number, rounded | {{ $json.total.toNumber().round(2) }} |
| Reformat a date | {{ $json.created_at.toDateTime().format('yyyy-MM-dd') }} |
| A date three days from now | {{ $now.plus(3, 'days').toISO() }} |
| Lookup with two outcomes | {{ $if($json.plan == 'pro', 'Priority', 'Standard') }} |
The method names come from n8n's expression reference. $json is the current item, $now is the current time as a Luxon DateTime, and $if and $ifEmpty are built-in helpers. When an expression grows past one line, move it into a Code node.
The three things with no direct n8n equivalent
These are the Zaps to find in your inventory before you promise anyone a date.
| Zapier feature | What it does | What to build in n8n |
|---|---|---|
| Digest by Zapier | Collects entries from many runs and releases them as one summary | Insert each entry into a Data table. A second workflow on a Schedule Trigger reads the rows, combines them with Aggregate, sends the summary and deletes the rows |
| Email Parser by Zapier | A hosted @robot.zapier.com mailbox that extracts data from forwarded emails | Forward to a mailbox you own and read it with Email Trigger (IMAP) or the Gmail Trigger. Extract fields with expressions, or with the Information Extractor node and a chat model |
| The long tail of app connections | Zapier lists 9,000+ apps, each with a hosted sign-in | Check the app for an n8n node first. If there is none, call its API from the HTTP Request node with a key you create, or look for a community node |
The third row is the one that ends migrations. Zapier's pricing page lists more than 9,000 apps; the core package of n8n 2.42.6 registers 444 nodes and triggers. For mainstream tools that gap is invisible. For a niche booking system or an industry CRM with no public API, there may be no route at all, and the honest answer is to leave that Zap on Zapier.
Step 3: set up n8n before you rebuild anything
Decide where n8n runs first, because it changes how credentials work. n8n Cloud is the closer match to Zapier: nothing to install, managed sign-in for Google nodes, and plans from €20 a month billed annually for 2,500 executions (checked October 2026). The self-hosted Community Edition has no licence fee or execution cap, and you own the server. Our Cloud vs self-hosted guide and the n8n pricing guide cover the choice.
- Start the 14-day Cloud trial or install the Community Edition. The trial includes 1,000 executions and needs no card.
- Set the timezone. Schedules fire in the workflow or instance timezone, not the one in your Zapier profile.
- Create credentials for every app on your inventory. n8n tests each one when you save it.
- Build the error workflow now. One workflow that starts with the Error Trigger and sends you a message. Our Error Trigger guide has one ready to import. In n8n 2.x it must be published to run.
If you are new to the editor itself, spend an hour with the n8n tutorial before you rebuild a real Zap.
Step 4: rebuild one Zap, start to finish
Take a typical Zap: a form submission arrives, a filter drops entries without a work email, the name is tidied up, a row is added to a sheet and a message goes to Slack. In Zapier that is a trigger and four steps, two of them free. In n8n it is five nodes and one execution.
- 1Add the trigger and capture one real event
Webhook or the app trigger. Expected result: sample data in the output panel. Pin it so later steps reuse it.
- 2Add the Filter node
Condition on the email field. Expected result: the test item passes, and a junk address is dropped.
- 3Add Edit Fields (Set)
One field per Formatter step, each with an expression. Expected result: clean values in the output.
- 4Add the app nodes
Google Sheets, then Slack, each with its credential. Run each node once and check the sheet and the channel.
- 5Set retries and the error workflow
Turn on Retry On Fail for nodes that call outside APIs. Select your error workflow in the workflow settings.
- 6Run the whole workflow, then publish
Expected result: one green execution in the list. Publishing turns on the production webhook URL or the schedule.
Resist improving the logic while you rebuild. Copy the Zap's behaviour first, prove it matches, then use what n8n makes cheap: merging three small Zaps into one workflow, or adding a branch that would have cost tasks before.
Step 5: the parallel-run checklist
Never switch a Zap off on the day its replacement is published. Run both, compare, then cut over in one sitting.
- Leave the Zap on. Point the n8n workflow at a test target: a copy of the sheet, a private channel
- Feed both the same events: send the form or app to both webhooks, or let both poll
- Compare outputs field by field for one full business cycle, including a weekend
- Open the n8n Executions list daily and look for failures and for events the Zap caught that n8n missed
- Force one failure and confirm the error workflow alerts you
- Check the n8n execution count against the plan you intend to buy
- Switch the n8n nodes to the real targets and turn the Zap off in the same sitting
- Update every webhook sender to the n8n production URL
- Keep the Zap, switched off, for 30 days as a rollback
- Downgrade the Zapier plan only after the last Zap is off
- Zap and workflow both write to the live CRM
- Zap switched off before the first real n8n run
- Webhook sender still pointing at the n8n test URL
- No error workflow, so failures are silent
- All Zaps moved in one weekend
- n8n writes to a test target until outputs match
- A full week of matching runs before cut-over
- Production URL in every sender, checked with one event
- A forced failure proves the alert arrives
- Lowest-risk Zap first, money and customers last
Mistakes that break a migration
- Forgetting to publish. A workflow that passes every manual test does nothing until it is published.
- Leaving a webhook on the test URL. The test URL only works while the editor is listening. Outside services need the production URL.
- Polling every minute on a small Cloud plan. A Schedule Trigger counts every firing. Use an app trigger that polls, which counts only when it finds new data, or pick a wider interval with our cron expression guide.
- Sending one message per item. Ten rows into a Slack node means ten messages. Put an Aggregate node in front when you want one.
- Assuming every app has a node. Check the inventory against the nodes panel before you commit to a date.
- Pasting API keys into node fields. Keys belong in credentials, which n8n stores encrypted.
Once the Zaps are across, the question changes from what it costs to what it could become. If one of those workflows is doing something customers would pay for, the AI SaaS Builder program covers building it as a product. It has no Zapier or n8n lessons; it covers Supabase for data and auth, the Claude API for the AI feature, deployment on Vercel and Stripe billing.
If n8n turns out to be the wrong destination
A migration inventory sometimes shows that the target is wrong. If non-technical colleagues have to maintain the result, Make vs n8n explains when Make's per-step credits are still a better deal than Zapier's tasks. If the appeal was an open licence, Activepieces vs Zapier covers the MIT-licensed option. And n8n alternatives compares twelve tools by the reason people leave.
Zapier to n8n migration: FAQ
Can I import my Zaps into n8n?
No. n8n's documentation lists several ways to bring a workflow in, all of them for n8n's own format, and no Zap importer. Zapier can export Zaps as JSON on Team and Enterprise accounts, which is useful as an inventory but is not a file n8n can open. Plan to rebuild each Zap: the trigger becomes a trigger node, each action becomes a node, and field mappings become expressions.
How long does a Zapier to n8n migration take?
It depends on the number of Zaps and how many use apps without an n8n node, and no vendor publishes a figure. A two-step Zap between well-known apps is mostly a matter of creating two credentials. A Zap with paths, a Digest step or a niche app takes longer. Rebuild one simple Zap first and time it, then multiply by your inventory rather than trusting a rule of thumb.
What is the n8n equivalent of Zapier Paths and Filter?
Filter by Zapier maps to the Filter node, which drops items that fail a condition, or to the If node when you want a true branch and a false branch. Paths by Zapier maps to the Switch node, which has one output per rule and an optional fallback. Neither changes your bill: n8n counts one execution per run, however many branches it takes.
Is n8n cheaper than Zapier after migrating?
Usually, for Zaps with several actions. Zapier counts a task for every successful action, while n8n counts one execution for the whole run. Checked October 2026, Zapier Professional starts at $19.99 a month billed annually for 750 tasks and n8n Cloud Starter is €20 a month billed annually for 2,500 executions. For one-action Zaps the units are equal, so the saving is small.
Do I need to self-host n8n to leave Zapier?
No. n8n Cloud is hosted for you and is the closer match to how Zapier feels, with managed sign-in for Google nodes. Self-hosting the free Community Edition removes the execution cap, but you take on the server, updates, backups and your own OAuth apps for services such as Google. Many teams migrate to Cloud first and decide about self-hosting once the workflows are stable.
What does Zapier have that n8n does not?
Three things have no direct equivalent in n8n 2.42.6. Digest by Zapier, which collects entries and releases them as one summary. Email Parser by Zapier, with its hosted @robot.zapier.com mailboxes. And Zapier's catalogue of more than 9,000 app connections, against 444 nodes and triggers in n8n's core package. Each has a workaround, but each is something you build.
Free · no card needed
Start with the free Starter Kit.
A unit economics calculator from AI SaaS Builder, plus four more working files.
Zaps moved over? Build what the workflows point to.
When an automation starts doing work customers would pay for, AI SaaS Builder, included in All Access, covers turning it into a product: Supabase for data and auth, the Claude API for the AI step, Claude Code and MCP to build faster, Vercel to deploy and Stripe to charge. It has no Zapier or n8n lessons. The other three programs, weekly coaching and the community come with the same subscription.
Stuck on one Zap that will not map?
Post the trigger, the steps and the app in the free Discord. Someone has usually rebuilt the same one, or can tell you it is the Zap to leave on Zapier.