How to import your converted workflows into n8n

Your download is a ZIP with everything you need to move into n8n. This page shows how to import it into n8n Cloud or your own n8n server and what to do before you switch your Pipedream workflows off.

What's in the ZIP

File	What it is
n8n/	One importable n8n workflow JSON per Pipedream workflow, in the same folders as in Pipedream
CHECKLIST.md	Per workflow: credentials to create, secrets to re-enter, webhook URLs to update, cutover steps
REPORT.md	The migration report
README.md	A short version of this page
import-to-n8n.mjs	A script that imports every workflow through the n8n API

Option 1: import one workflow in the editor

1. Open n8n and create a new workflow.
2. Open the ⋯ menu in the top right corner and choose Import from File.
3. Pick a JSON file from the n8n/ folder.
4. Save the workflow.

You can also copy the JSON and paste it straight onto an empty canvas. The editor import leaves out workflow settings such as the timezone and the error workflow. If you need them, use option 2.

Option 2: import everything with the API script

You need Node.js 18 or newer on your computer.

1. In n8n, open Settings → n8n API and create an API key.
2. Unzip the download and open a terminal in its folder.
3. Run the script with your n8n address and the key.

On macOS or Linux:

N8N_URL=https://your-n8n.example.com N8N_API_KEY=your_key node import-to-n8n.mjs

In Windows PowerShell:

$env:N8N_URL="https://your-n8n.example.com"; $env:N8N_API_KEY="your_key"; node import-to-n8n.mjs

The script imports each workflow and prints how many succeeded. The n8n API is available on n8n Cloud Starter, Pro and Enterprise and on every self-hosted edition, but not on the Cloud free trial.

On a self-hosted server you can also use n8n's own command line: n8n import:workflow --separate --input=./n8n, run once for each sub-folder.

After the import

Imported workflows arrive unpublished, so nothing runs until you're ready. Work through CHECKLIST.md workflow by workflow:

1. Credentials. Create an n8n credential for each app the workflow uses and select it on the matching nodes. Pipedream doesn't export tokens, so every account has to be connected again.
2. Secrets. Re-enter values that the export replaced with <redacted>, in credentials or as n8n Variables (Variables are available on n8n Cloud Pro and Enterprise and on self-hosted Business and Enterprise).
3. Test. Run the workflow with a sample event, for example one you saved from Pipedream's event history, and compare the result.
4. Publish. Publish the workflow so its trigger starts working. Workflows that start from an app trigger, such as a new spreadsheet row, call themselves once per new item, so publish them before you test the trigger.
5. Switch webhooks. Copy the production URL from each Webhook node and update every service that called your old Pipedream URL.
6. Turn Pipedream off. Watch the n8n Executions list for a few days, then disable the Pipedream workflow. Copy data store records out before April 30, 2027: by then Pipedream deletes all Workflows data.

Need more help?

The migration guide covers each step of the move in detail, and the code steps guide explains what changes in code on n8n Cloud. If something in your import doesn't work, email hello@workflowexit.com with the workflow name.