Pipedream vs n8n: a feature-by-feature comparison

Pipedream vs n8n used to be a choice between two automation platforms. Now that Pipedream Workflows shuts down on March 31, 2027, the real question is how well n8n covers what you built in Pipedream. Short answer: most features have a direct n8n equivalent. The differences that cost time are npm packages on n8n Cloud, the item-based data model in code, and credentials that must be created again.

Side-by-side

Feature	Pipedream Workflows	n8n
Status	Shuts down March 31, 2027	Active
Hosting	Cloud only	n8n Cloud or self-hosted
Self-hosting license	n/a	Sustainable Use License (fair-code), free Community Edition
Builder	Linear steps with branches	Node canvas
JavaScript	Node.js v20 code steps	Code node (JavaScript)
Python	Python 3.12 code steps	Code node (Python, native via task runners)
Go, Bash	Supported	Not in the Code node; rewrite in JavaScript or Python
npm packages	Any package, installed on import	Cloud: crypto and moment only. Self-hosted: allow-listed packages
Webhook trigger	HTTP trigger at *.m.pipedream.net	Webhook node at /webhook/<path> on your n8n domain
Custom HTTP response	$.respond() or Return HTTP response	Respond to Webhook node
Schedules	Interval or cron, any timezone	Schedule Trigger, interval or cron, workflow timezone
Branching	If/Else, Switch, Parallel, Filter	If, Switch, Merge, Filter, Loop Over Items
Delays	$.flow.delay, Delay action	Wait node
Key-value storage	Data stores	Data tables; workflow static data in JS code
Secrets	Environment variables (process.env)	Credentials; Variables ($vars) on paid plans
Errors	Email notifications, auto-retry on Advanced, $error source	Error Trigger workflow, Retry On Fail per node
Git	GitHub Sync	Source control environments (Business, Enterprise)
Pricing unit	Credits (compute time)	Executions (Cloud); free when self-hosted

Code

This is where the platforms differ most.

Pipedream runs a Node.js v20 component per step. You read earlier steps from steps, export values with $.export or return, and stop with $.flow.exit(). Any npm package installs on import, with versions pinned in the import string.

n8n's Code node works on items. It runs once for all items (the default) or once for each item. You read input with $input.all() or $('Node name') and return [{ json: {...} }]. On n8n Cloud you can load only crypto and moment, and Python can't import any library. On self-hosted n8n you allow packages on the task runner.

What this means for a migration: plain JavaScript moves easily; npm-heavy steps decide your hosting. Details: code steps to the n8n Code node, npm packages in n8n, Python steps.

Triggers

Pipedream's HTTP trigger gives each workflow a unique *.m.pipedream.net URL. n8n's Webhook node has a test URL and a production URL, and the production URL works only after you publish the workflow. The payload limit is 16 MB by default; Pipedream's HTTP body limit is 512 KB unless you use its large-upload option.

Schedules map one to one: interval or cron in both. In n8n, check the timezone. The Schedule Trigger uses the workflow timezone if set, otherwise the instance timezone, which defaults to America/New_York on self-hosted.

Email triggers differ: Pipedream gave each workflow its own address; in n8n you read a mailbox you own over IMAP.

Data and state

Pipedream data stores are a key-value store shared across workflows. n8n has two options:

• Data tables: built-in tables managed with the Data Table node, 200 MiB per instance by default, listed on every n8n Cloud plan and not excluded from the free Community Edition (docs). They can't be read directly from a Code node.
• Workflow static data: $getWorkflowStaticData() in JavaScript code. n8n calls it experimental, it isn't saved in test runs, and n8n recommends Data tables instead.

More: Pipedream data stores to n8n.

Secrets and credentials

Pipedream stores secrets as environment variables and app logins as connected accounts. n8n stores app logins and API keys as encrypted credentials attached to nodes. n8n Variables exist on Cloud Pro and Enterprise and on self-hosted Business and Enterprise. Neither platform moves credentials to the other; you create them again. See secrets to n8n credentials.

Error handling

Pipedream emails you on unhandled errors and can auto-retry on the Advanced plan. n8n lets you assign an error workflow that starts with an Error Trigger, plus Retry On Fail and On Error settings on each node. See Pipedream errors to n8n.

Pricing model

Pipedream Workflows billed credits: one credit per 30 seconds of compute at 256 MB, counted per workflow segment. n8n Cloud bills per workflow execution, regardless of how many steps it has (n8n pricing). Self-hosted n8n Community Edition has no execution fee; you pay for the server.

For workflows with long-running code, per-execution billing is often simpler to predict. For thousands of tiny webhook calls, compare your monthly execution count against the n8n plan limits.

Verdict

If your Pipedream workflows are webhooks, schedules, HTTP calls and JavaScript, n8n is a close match and the migration is mostly mechanical. If they depend on many npm packages, plan for self-hosted n8n or for rewriting those steps. Go and Bash steps need a rewrite.

To see where your own workflows land, drop your export into the free report. It runs in your browser and marks each workflow green, yellow or red. The report and 1 workflow are free. Full export: $3 per workflow, $19 minimum — coming soon. See pricing. The full walkthrough is in migrate Pipedream to n8n.

moveworkflows is not affiliated with Pipedream or n8n.