MyClawn n8n Workflows › Zapier to n8n
Zapier to n8n migration: each Zap rebuilt as a workflow you can import
n8n imports its own workflow files, not Zaps. So a migration is a rebuild, one Zap at a time. That is exactly the kind of work that can be described in a few lines and delivered as a file.
How Zap steps map to n8n nodes
| In Zapier | In n8n | Watch out for |
|---|---|---|
| Trigger (new row, new email, new order) | The app's trigger node, or a Schedule Trigger that polls | Some Zapier triggers have no trigger node in n8n; then a webhook from the app or a scheduled check is used |
| Webhooks by Zapier (catch hook) | Webhook node | The URL changes. Every system that sends to the old URL must be updated at cutover |
| Filter | If node | In n8n the "false" side can do something useful instead of just stopping |
| Paths | Switch node | One node, several outputs |
| Formatter | Set node with expressions, or a Code node | No one-to-one equivalent: each formatter step is rewritten |
| Delay | Wait node | |
| Looping | Usually nothing: n8n runs each node once per item | Many Zaps get shorter |
| Code by Zapier | Code node (JavaScript or Python) | Input and output shapes differ; the code is adapted |
| An app n8n has no node for | HTTP Request node calling the app's API | You need an API key for that app |
What to send for each Zap
One request per Zap. Open the Zap and write down, or paste, for each step:
- The app and the event ("Typeform: new entry", "Slack: send channel message").
- The fields that matter and where each value comes from.
- Every filter and path condition, in words.
- How often it runs and roughly how many times a month.
Paste that into the box and you see the n8n version drawn before you decide. The delivered file has the same logic, plus what Zapier did for you silently and n8n does not: retries are off by default on n8n nodes, so they are switched on where an API is called, and an error branch tells you when a run fails.
Type what should happen, in plain words, or paste a workflow that is broken. Starter $39/mo · Pro $129/mo. Refund within 14 days if it misses.
Draw my workflowCutover checklist
- Import the file and connect each account in n8n. Connections do not carry over from Zapier.
- Run the workflow once with the pinned test data. Then once with one real item.
- Check dates and times: n8n has a timezone setting per workflow and per instance; scheduled Zaps move to that timezone.
- Switch the Zap off and the workflow on at a quiet moment. For webhooks, update the sender to the new URL at the same time.
- Keep the Zap paused, not deleted, for a month.
Is it worth moving?
It depends on volume. Zapier bills by task; n8n bills by workflow execution, however many steps one run has. n8n Cloud's Starter plan lists 2.5K executions a month for 20 euros a month billed annually, and Pro 10K for 50 euros (n8n pricing page, Nov 13, 2026); self-hosted n8n is not billed per execution, but you run the server. If you have three simple Zaps and they cost you little, leave them. If one multi-step Zap eats most of your task quota, move that one first.
Questions
Can you convert my Zap export file?
Paste it if you have it; it helps as a description of the steps. It cannot be converted mechanically, because Zapier steps and n8n nodes do not match one to one. The workflow is rebuilt from it.
How many Zaps fit in a plan?
One Zap is one workflow. Starter covers 5 a month, Pro 20.
Do you also rebuild Make scenarios?
Yes, the same way: describe or paste the modules and filters of one scenario per request.
Type what should happen, in plain words, or paste a workflow that is broken. Starter $39/mo · Pro $129/mo. Refund within 14 days if it misses.
Draw my workflowMore about n8n Workflows
Sources (checked 2026-11-13): docs.n8n.io/build/manage-workflows/export-and-import · n8n.io/pricing/