Pipedream → n8n: what converts cleanly, what breaks, and a free report for your export

Pipedream Workflows stops running on March 31, 2027, and Pipedream deletes all workflow data, including connected accounts, by April 30. I’ve been converting Pipedream workflows to n8n: 395 public ones so far (GitHub Sync repos and Pipedream templates), all imported into n8n 2.42 with their code steps run in the Code node. Here’s what I learned.

Converts cleanly

  • HTTP trigger → Webhook node, $.respond() → Respond to Webhook. The URL changes, so every sender needs the new one.
  • Schedule → Schedule Trigger. “Every 90 minutes” needs a few cron rules, because one interval rule can’t express it.
  • Node.js code steps → Code node, with a small compatibility layer for steps.x.$return_value, $.export, $.flow.exit, props and data stores.
  • If/else and switch blocks → If and Switch with their branch steps. Parallel → branches + Merge. Loop → Loop Over Items.
  • Registry actions (Slack, Google Sheets, Airtable…) → the matching n8n node in most cases.

What bites

  • npm packages. On n8n Cloud the Code node loads only crypto and moment, and Python can’t import anything. HTTP calls can move to this.helpers.httpRequest(), which works inside the Code node. Otherwise self-host with NODE_FUNCTION_ALLOW_EXTERNAL.
  • Polling triggers (new row, new email): n8n hands you all new items in one execution, while Pipedream ran the workflow once per event. Code written for one event quietly handles only the first item. Fix: Loop Over Items + Execute Workflow per item.
  • Getting the export. Project → Settings → Export Workflows writes a ZIP to the project’s File Store, which Pipedream lists as an Advanced-plan feature. On Free or Basic, try the REST API (GET /v1/workflows/{id}) instead.
  • Secrets and accounts come out as <redacted> and an account ID. Plan to re-create credentials.
  • Data stores and File Store files aren’t in the export. Copy them before April 30.

The tool
I put all of this into Workflow Exit: https://workflowexit.com

  • The report is free and runs in your browser, so nothing is uploaded. Per workflow it shows what converts automatically, what needs a rewrite or manual work, the effort, and whether n8n Cloud or self-hosted fits.
  • The converter produces importable n8n JSON and a cutover checklist. The first workflow is free. Code steps that need npm packages are rewritten with AI.
  • For Free/Basic plans, a small local CLI pulls your workflows through the API. Your key stays on your machine.

The full mapping is in this guide: Migrate Pipedream to n8n: Step-by-Step Guide | Workflow Exit

Disclosure: I built it. If you have a Pipedream pattern that doesn’t convert, post it here. I’d like to see it.

Update with numbers: I ran the analyzer over 395 public Pipedream workflows (172 complete ones from GitHub Sync repos, 223 shared templates) and 746 code steps. What stood out:

- 88% of the complete workflows have at least one code step, and 69% of all steps are code.
- 61% of JavaScript steps import a package or call an API; 30% import something the n8n Cloud Code node can't load (anything beyond `crypto` and `moment`).
- 89% of Python steps import modules. n8n Cloud's Python can't import anything, so those need a JS rewrite or self-hosting with the Python task runner.
- 24% of JavaScript steps read a connected account's token in code (`this.app.$auth`). Code nodes can't read n8n credentials, so those calls move into an HTTP Request node with a credential.
- 17% of workflows use data stores, which the export doesn't include. Save the records before April 30, 2027.

Full breakdown and method: https://workflowexit.com/pipedream-migration-data

On the Free or Basic plan and can't find Export Workflows? It writes to the File Store, which those plans don't have. The REST API still returns the workflow definitions, and the open-source CLI pulls them for you: https://github.com/masonuhome/pipedream-to-n8n