Switching from n8n to Zapier — when the rebuild is worth it

Expect a rebuild, not a file drop. n8n saves workflows in JSON. From the editor menu you can Download the current workflow, Import from File, or Import from URL. That path moves a workflow inside n8n. Exported workflow JSON includes credential names and IDs. HTTP Request nodes may contain authentication headers when imported from cURL. Remove or anonymize that before you share the file. None of it creates a Zap.

n8n packages are a different n8n-to-n8n file. A package is a .n8np archive, in Preview, available from n8n 2.27.0. You export it with the n8n CLI or API, not from the editor. It can carry workflows, folders, and projects. A credential file in the package holds ID, name, and type only. Credential secrets never travel. On import, n8n matches a credential that already exists on the target instance, or creates an empty placeholder for you to fill in. Executions and execution history do not travel. Data table rows do not travel. n8n says a package is not a full backup. That placeholder is on another n8n instance. It is not a Zap, and it is not a Zapier Table.

A Zap is a trigger plus one or more actions. Zapier’s import-and-export article covers backing up and sharing Zap workflows with other Zapier accounts as JSON, from Settings, then Security and data. The article title names Team or Enterprise. Import is not available during a free Zapier trial. After import, the article tells you to turn the Zap workflows on and test app connections. If a connection is no longer active, reconnect it. Imported Zaps land in a folder named Imported Zap workflows plus the date. That path moves a Zap inside Zapier. It does not read an n8n JSON file or an .n8np package.

So the expectation is: one workflow becomes one Zap you build. The trigger node becomes the trigger step. Each later node becomes an action, or a step you rebuild by hand. Fields are mapped again. A call through the Execute Sub-workflow node still counts as one execution for the parent workflow. On Zapier, each action inside a sub-Zap, the Call a Sub-Zap step, and the Return From a Sub-Zap step each count as a task when they succeed. Do not assume that sub-workflow becomes one step. The two JSON files are not interchangeable.

A Cloud trial download is the same limit. If you do not upgrade by the end of the trial, n8n deletes the workspace. You have 90 days to download workflows. That file is n8n JSON. It is not a Zapier import.

Source: n8n — export and import · n8n — packages · n8n — understand executions · n8n — try free then choose a plan · Zapier — what is a Zap · Zapier — import and export Zap workflows · Zapier — how task usage is measured · accessed 2026-10-13

The n8n export does not fill a Zapier connection. Names and IDs in the workflow JSON are not secrets. A package credential file holds ID, name, and type only. Credential secrets never travel. The empty placeholder, when import creates one, is on the target n8n instance. It is not a Zapier app connection. HTTP Request nodes can still carry authentication headers if the workflow was imported from cURL — clean those before you share the file, and do not paste them into a Zap as if the export had carried a login.

Zapier’s connection export never includes credentials, API keys, or other sensitive authentication data. It is a CSV of metadata: connection id, app, title, owner email, status, and similar fields. The page lists Enterprise under available plans, and the before-you-begin note says the account owner on any plan, or a super admin on Team or Enterprise, can start it. Either way, the file is an audit list. It is not an n8n credential, and it does not fill a new Zap.

On Zapier you connect the account in the Zap, from the App connections page. You can test a connection, reconnect an expired one, or replace it with a different account. After a Zap JSON import, the import article tells you to test app connections and reconnect any that are no longer active. That reconnect is still a Zapier connection. It is not a filled n8n credential.

Plan the overlap around that fact. Name who will create each Zapier connection and who still owns the n8n credential until the workflow is unpublished. A workflow that still runs is not a Zapier app connection.

Source: n8n — export and import · n8n — packages · Zapier — export app connections · Zapier — manage your app connections · Zapier — import and export Zap workflows · accessed 2026-10-13

An n8n trigger does not become a Zap trigger by file. The Webhook node has a test URL and a production URL. n8n registers the production URL when you publish the workflow. The path is randomly generated by default. That URL does not move. A Catch Hook trigger gives you a unique URL. You copy it from the Zap’s Test tab and paste it into the sending app. The trigger article says that URL only changes if the Zap is transferred to another user, because the URL contains the owner’s Zapier ID. If the Zap is turned off or deleted, Zapier returns a 404 for incoming requests after a system update delay of up to several hours, during which the URL can still return 200. If senders POST to the n8n production URL, point them at the new Zapier URL before you rely on the new job. Do not leave both URLs writing the same row.

The pricing page lists Connections via webhooks on Professional, Team, and Enterprise, and leaves that row off Free. The trigger-from-webhooks article’s plan badges match that row: Free is ineligible, and Professional, Team, and Enterprise are eligible.

A schedule is set again on the Zap. An n8n Schedule Trigger counts one execution every time it fires. Schedule by Zapier is set in the Zap editor. You can run the Zap every month, week, day, or hour, or on a custom frequency. Using that tool does not count toward task usage. Zapier does not guarantee the Zap will trigger at the precise minute you set. The timezone is the one on the Zapier account, not the n8n schedule. The n8n export does not carry a live sender over, and a Zapier JSON file does not read the n8n URL.

The rest of what sticks — history, one-tool steps, permissions, leftover quota — is on What does not migrate. This page does not reprint that list.

Source: n8n — webhook node · n8n — understand executions · Zapier — trigger Zap workflows from webhooks · Zapier — pricing · Zapier — schedule Zap workflows · accessed 2026-10-13

The parallel-run period is one critical job, not the whole account. Keep that workflow published so production runs continue. Rebuild it as one Zap. Create the Zapier connections. If the job has a webhook, re-point the sender for the window you are comparing, and do not let both copies write the same live row. Compare the writes for the same trigger window — the row, the message, and what happens when a required field is missing. Then unpublish that workflow. Leave the workflow intact until the Zap has handled a real run, so you can turn the Zap off and leave the workflow published if the writes do not match.

A manual click of Execute Workflow is not that proof. Only production executions count toward the n8n quota: runs started by triggers, schedules, or polling. Manual executions do not count. On Zapier, a Zap only processes new data created after it is published. Test records are sample data used while building and may differ from the data the Zap receives during live runs. Compare a production window, not only an editor test.

Do not move every workflow on the same day. n8n and Zapier do not publish a required number of days for that overlap. This page does not invent a required number of days. The checklist — which job, what to compare, how to go back — is Parallel-run one job before you switch.

Execution history does not shorten that period. n8n packages do not carry executions or execution history. That list stays on n8n. Zapier can export up to 5,000 Zap runs at a time, as CSV or JSON, emailed to the Zapier account (article updated 29 May 2026). That file is Zap history. It is not an n8n workflow, and it does not become the old execution list.

Source: n8n — understand executions · n8n — packages · Zapier — what is a Zap · Zapier — export your Zap history · accessed 2026-10-13

An execution is a single run of a workflow. Pricing is based on monthly workflow executions. The docs page says only production executions count toward the quota. Step count does not add a second execution. A call to another workflow with Execute Sub-workflow still counts as one execution for the parent. A task is any successful action that runs in Zapier. Only successful actions count (help article updated 21 August 2026). Triggers do not count. Filter and Paths steps do not count. In Zapier’s own example, a Zap that uploads a file and sends a message uses two tasks each time both actions succeed. Ten runs use 20 tasks. One execution is not one task. Leftover n8n executions do not become Zapier tasks.

An n8n Schedule Trigger counts one execution every time it fires, regardless of outcome. Schedule by Zapier does not count toward task usage. Do not treat those two schedules as the same unit.

If a Zapier plan does not include pay-per-task billing, or you have turned it off, Zapier holds new Zap runs once the plan reaches its task limit, until the billing cycle resets. The pricing page lists pay-per-task billing on Professional, Team, and Enterprise, and not on Free. This page does not copy a per-task rate.

Name the same job in both units before you treat a switch as a smaller bill. The dictionary is Tasks vs credits vs executions. The n8n plan-and-execution map is n8n pricing explained. The Zapier plan-and-task map is Zapier pricing explained. This page does not claim you will save. It publishes no annual savings. It does not invent a monthly dollar.

Source: n8n — understand executions · n8n — pricing · Zapier — how task usage is measured · Zapier — schedule Zap workflows · Zapier — pricing · accessed 2026-10-13

Primary vendor pages. Access date for every citation on this page: 2026-10-13. Plan names stay as published. Dollar bills stay off this page.

• n8n — export and import · accessed 2026-10-13
• n8n — packages · accessed 2026-10-13
• n8n — understand executions · accessed 2026-10-13
• n8n — webhook node · accessed 2026-10-13
• n8n — try free then choose a plan · accessed 2026-10-13
• n8n — choose how to use n8n · accessed 2026-10-13
• n8n — pricing · accessed 2026-10-13
• Zapier — what is a Zap · accessed 2026-10-13
• Zapier — import and export Zap workflows · accessed 2026-10-13
• Zapier — export app connections · accessed 2026-10-13
• Zapier — export your Zap history · accessed 2026-10-13
• Zapier — how task usage is measured · accessed 2026-10-13
• Zapier — manage your app connections · accessed 2026-10-13
• Zapier — trigger Zap workflows from webhooks · accessed 2026-10-13
• Zapier — schedule Zap workflows · accessed 2026-10-13
• Zapier — pricing · accessed 2026-10-13