WEWorkflow ExitFree report
Pipedream Workflows shut down March 31, 2027 · March 31, 2027

Move your Pipedream workflows to n8n

Upload your Pipedream export and get a free migration report in seconds. Then convert every workflow into an importable n8n workflow: triggers, branches, actions and code steps included.

The report runs in your browser. Your export is not uploaded.

September 30, 2026
Signups and new subscriptions closed
March 31, 2027
Workflows stop running
April 30, 2027
All workflow data and connected accounts deleted
Free

Migration report

  • 🟢🟡🔴 Each workflow rated: converts automatically, needs a rewrite, or needs manual work
  • Triggers, actions and code steps with their n8n equivalents
  • npm packages n8n Cloud can't load, env vars, redacted secrets
  • Data stores and files to save before April 30, 2027
  • Hours by hand vs. with the converter, and Cloud vs. self-hosted advice
From $49, one-time

Conversion to n8n

  • One importable n8n workflow JSON per Pipedream workflow, folders kept
  • Code steps keep working: steps, $.export, $.flow.exit, props, data stores, axios
  • AI rewrite for code that n8n Cloud can't run as-is
  • Cutover checklist: credentials, variables, webhook URLs
  • Bulk import script for the n8n API. First workflow free.

Three steps

  1. 01

    Export from Pipedream

    Project → Settings → Export Workflows, then download the ZIP from the project's File Store. On a Free or Basic plan, our local CLI pulls your workflows through Pipedream's API instead.

    Learn more
  2. 02

    Read the free report

    Drop the ZIP on the report page. See what converts, what needs attention and how long it will take.

    Learn more
  3. 03

    Convert and import

    Pay once for your workflow count, download the n8n files and import them into n8n Cloud or your own server.

    Learn more

What maps to what

Deterministic conversion first, AI only where it's needed. The converter is tested on 395 real Pipedream workflows (public GitHub Sync repos and Pipedream templates), all imported into n8n, with their code steps run in n8n's own sandbox.

Pipedreamn8nHow
HTTP / Webhook triggerWebhook (+ Respond to Webhook for $.respond)Automatic
Schedule (cron or interval)Schedule TriggerAutomatic
Node.js code stepCode node with Pipedream compatibility layerAutomatic
steps.x.$return_value, $.export$('x').first().json…Automatic
@pipedream/platform axiosthis.helpers.httpRequestAutomatic
Data store ($.service.db, data_store props)Workflow static dataAutomatic
If/Else, Switch, Parallel, Loop, Filter, Delay, EndIf, Switch, Merge, Loop Over Items, Wait, stopAutomatic
Polling app triggers (Sheets, Gmail, Airtable…)n8n trigger node, one run per new record like PipedreamMostly automatic
Registry actions (Slack, Sheets, OpenAI…)Native n8n nodes where mapped, else HTTP RequestMostly automatic
npm packages n8n Cloud can't loadAI rewrite, or self-hosted n8nAI rewrite
Python code stepsAI port to a JavaScript Code nodeAI rewrite
Secrets and connected accountsn8n credentials and Variables (checklist)Checklist
Pipedream code step
export default defineComponent({
  async run({ steps, $ }) {
    const { email } = steps.trigger.event.body;
    $.export("domain", email.split("@")[1]);
    if (!email) return $.flow.exit("no email");
    return { email };
  },
});
Runs unchanged in an n8n Code node
// Pipedream compatibility layer (generated)
const steps = /* reads $('trigger'), $('step')… */;
const $pd = { export, flow: { exit }, respond… };
// Original code, untouched
const __component = { async run({ steps, $ }) { … } };
// Output: [{ json: { domain, $return_value } }]

Later steps read it as $('step').first().json.$return_value, and prop expressions are rewritten the same way.

Pricing

One-time payment per migration. No subscription.

Report
$0

Full migration report, in your browser. Plus your first workflow converted.

  • ✓ Unlimited workflows analyzed
  • ✓ Effort estimate and blockers
  • ✓ Cloud vs self-hosted advice
  • ✓ 1 workflow converted
Get the free report
Starter
$49 one-time

For a single project or a side business.

  • ✓ Up to 25 workflows
  • ✓ AI rewrite of code steps
  • ✓ Cutover checklist
  • ✓ Bulk import script
  • ✓ Re-run conversions for 60 days
Start with your export
TeamPopular
$149 one-time

For teams with several projects.

  • ✓ Up to 100 workflows
  • ✓ AI rewrite of code steps
  • ✓ Cutover checklist
  • ✓ Bulk import script
  • ✓ Re-run conversions for 60 days
Start with your export
Agency
$399 one-time

For agencies migrating several clients.

  • ✓ Up to 500 workflows
  • ✓ AI rewrite of code steps
  • ✓ Cutover checklist
  • ✓ Bulk import script
  • ✓ Re-run conversions for 60 days
  • ✓ Multiple projects
Start with your export

Questions

When does Pipedream Workflows shut down?+

Pipedream Workflows and String stop running on March 31, 2027. New signups and subscriptions closed on September 30, 2026. All Workflows data, including connected accounts and OAuth tokens, is deleted by April 30, 2027. Pipedream Connect is not affected.

Is there an official way to import Pipedream workflows into n8n?+

No. As of October 2026 neither Pipedream nor n8n offers an importer. Pipedream's export tool gives you a ZIP of workflow JSON files that describe triggers, steps, code and props, and Workflow Exit turns those files into importable n8n workflows.

Is the migration report really free?+

Yes. The report runs entirely in your browser: your export is parsed and analyzed locally and is not uploaded. It shows which workflows convert automatically, what needs a rewrite, which npm packages n8n Cloud can't load, and what you must re-enter by hand.

What does the paid conversion produce?+

A ZIP with one importable n8n workflow JSON file per Pipedream workflow, a cutover checklist (credentials, variables for redacted secrets, webhook URLs to update), the migration report, and a script that imports everything through the n8n public API.

Do Pipedream code steps work in n8n?+

Node.js code steps are converted into n8n Code nodes with a compatibility layer that rebuilds steps, $.export, $.flow.exit, props, data stores and @pipedream/platform axios. Steps that import npm packages n8n Cloud can't load are rewritten with AI or flagged for self-hosted n8n.

Should I move to n8n Cloud or self-hosted n8n?+

n8n Cloud allows only the crypto and moment modules in Code nodes and no Python imports. If your code steps depend on other npm or Python packages, self-hosted n8n is the safer target. The free report recommends one based on your actual code.

What about secrets and connected accounts?+

Pipedream's export replaces secret values with <redacted> and includes only an ID for connected accounts. You re-create credentials in n8n. The checklist lists every app and secret per workflow so nothing is missed.

My plan can't use Export Workflows. What can I do?+

The official export is written to the project's File Store, which Pipedream lists as an Advanced-plan feature. You can also upload a GitHub Sync repository or workflow JSON fetched from the Pipedream REST API. See the export guide for each option.

See what your migration involves in under a minute.

Drop your Pipedream export on the report page. Free, no signup, nothing uploaded.

Get the free migration report