How to migrate Pipedream workflows to n8n before the March 2027 shutdown

Description and use

Migrating Pipedream workflows to n8n involves exporting definitions, mapping triggers and steps, converting code, and recreating credentials.

Problem

Pipedream workflows will stop running on March 31 2027 and all data will be deleted by April 30 2027, requiring migration to n8n.

Outcome

All Pipedream workflows were successfully rebuilt in n8n, preserving trigger logic, step functionality, and code behavior, with credentials and secrets re‑configured.

Workflow

• Export or retrieve workflow definitions from Pipedream (export ZIP, GitHub sync, or REST API).
• Identify missing elements (redacted secrets, OAuth tokens, env vars, data stores, event history).
• Choose n8n deployment (Cloud or self‑hosted) based on code dependencies.
• Map Pipedream triggers to n8n nodes (Webhook, Schedule Trigger, app triggers).
• Adjust trigger differences: update webhook URLs, convert interval rules, handle polling batch items with Loop Over Items or Execute Workflow.
• Map Pipedream steps and branches to n8n nodes (app nodes, If/Switch, Wait, Merge).
• Convert Pipedream code steps to n8n Code nodes, translating syntax and handling exit logic.
• Create n8n credentials for connected accounts and re‑enter secrets or variables.
• Test migrated workflows with saved sample events.
• Publish and monitor migrated workflows.

Evidence

Pipedream Workflows and String stop running on March 31, 2027. All Workflows data, including connected accounts and their OAuth tokens, is deleted by April 30, 2027.

Source

Neither Pipedream nor n8n offers an importer, so moving to n8n means rebuilding each workflow in n8n's own format.

Source

Pipedream writes a ZIP to the project's File Store: a manifest.json plus one JSON file per workflow, with triggers, steps, code, props and branches.

Source

Webhook URLs change. Every service that calls your *.m.pipedream.net URL needs the new n8n production URL.

Source

Pipedream’s rule builder compares text without regard to case, and n8n's If node is case-sensitive unless you turn on its Ignore Case option.

Source