Pipedream alternatives: where to move your workflows before March 31, 2027

For most Pipedream users, n8n is the closest replacement: it has webhook and schedule triggers, custom HTTP responses, If and Switch branching, a Wait node, hundreds of app nodes, and JavaScript and Python Code nodes, and it can be self-hosted for free. Pick self-hosted n8n if your code steps depend on npm packages, because n8n Cloud only allows crypto and moment. If your workflows are mostly code, Windmill, Trigger.dev or plain serverless functions may fit better.

Pipedream Workflows has accepted no new signups or subscriptions since September 30, 2026, stops running on March 31, 2027, and its data is deleted by April 30, 2027 (Pipedream notice). Here is how the main options compare for people coming from Pipedream specifically.

Comparison table

Prices are taken from each vendor's pricing page as of October 2026 and change often. Check the linked page before you decide.

Platform	Code steps	npm packages	Self-hosting	Pricing model (as of October 2026)
n8n Cloud	JavaScript and Python Code nodes	Only crypto and moment; Python can't import anything	No	Per workflow execution, unlimited steps. Starter 20€/month (2,500 executions) and Pro 50€/month (10,000), billed annually (pricing)
Self-hosted n8n	Same Code nodes	Any installed package via NODE_FUNCTION_ALLOW_EXTERNAL	Yes, free Community Edition	No execution fee. You pay for the server. Paid Business and Enterprise licenses add features
Activepieces	JavaScript/TypeScript code steps	Supported in code steps	Yes, free Community Edition	Credits. Free 1,000/month, Plus $20/month (10,000), Team $200/month (50,000) (pricing)
Windmill	Scripts in TypeScript, Python, Go, Bash and more	npm and PyPI imports	Yes, open source	Free open-source edition. Paid plans are priced by seats and compute units (pricing)
Trigger.dev	TypeScript tasks in your own repo	Any, from your package.json	Yes, Apache 2.0	Compute seconds plus a per-run fee. Free with $5 of usage, Hobby $10/month, Pro $50/month (pricing)
Make	Make Code app (JavaScript, Python) on paid plans	Built-in libraries only; custom libraries on Enterprise	No	Credits, most actions use 1. Free plan 1,000 credits/month (pricing)
Zapier	Code by Zapier (JavaScript, Python)	Public ESM npm and PyPI packages on paid plans	No	Tasks, one per completed action step. Free 100/month, Pro from $19.99/month billed annually for 750 (pricing)
Cloudflare Workers	JavaScript/TypeScript functions	Bundled at deploy	No	Free 100,000 requests/day; Paid $5/month minimum with 10 million requests (pricing)
AWS Lambda	Node.js, Python and other runtimes	Bundled in the deployment package	No	Free 1 million requests and 400,000 GB-seconds per month, then $0.20 per million requests plus compute (pricing)

What a Pipedream replacement needs to cover

Pipedream mixed two styles of work, and a good replacement has to handle both:

• Builder features: app triggers, prebuilt actions, managed OAuth for connected accounts, if/else and switch blocks, delays.
• Developer features: HTTP endpoints with custom responses ($.respond), code steps in Node.js or Python with any npm or PyPI package, a key-value data store, environment variables, and GitHub Sync.

Pricing also shaped how people built. Pipedream charged one credit per 30 seconds of compute per workflow segment, not per step (Pipedream pricing docs). A ten-step workflow that finished within 30 seconds in a single segment used one credit, the same as a two-step one. Platforms that bill per step or per action change that math.

n8n: the default choice for most Pipedream users

n8n maps closely to how Pipedream workflows are built:

• HTTP trigger becomes a Webhook node, and $.respond becomes a Respond to Webhook node.
• Schedules become a Schedule Trigger with intervals or cron.
• If/else, switch and delay become If, Switch and Wait nodes.
• Code steps become Code nodes. Pipedream helpers like steps and $.export need rewriting or a compatibility layer.
• Billing on n8n Cloud is per workflow execution with unlimited steps, which is close to Pipedream's "not per step" model.

The catch is npm on n8n Cloud. The Code node docs say you can't import external npm modules on Cloud; only crypto and moment are available. HTTP clients and date libraries are easy to replace with n8n built-ins, but SDKs and parsing libraries are not. Self-hosted n8n removes that limit. See what breaks in code steps on n8n Cloud and the Pipedream vs n8n comparison.

Two smaller points: n8n Variables, the closest thing to Pipedream environment variables, require n8n Cloud Pro or Enterprise or a self-hosted Business or Enterprise license. And n8n Code nodes cannot read credentials, so API calls that used a Pipedream connected account inside code usually move to an HTTP Request node with an n8n credential.

When n8n is not the right choice

Your workflows are really programs. If most steps are long code with many dependencies, tests and shared modules, a code-first platform is a better home. Trigger.dev runs TypeScript tasks from your own repository. Windmill runs scripts in several languages and adds flows, schedules and generated UIs on top.

You need simple app-to-app automations for non-developers. Zapier and Make have large app catalogs and are familiar to operations teams. Both bill per step-level unit, so a Pipedream workflow with many steps can cost noticeably more per run, and code support is narrower: Make limits custom libraries to Enterprise, and Zapier allows public ESM packages on paid plans but not CommonJS packages or native modules (Zapier help, Make help).

You have a handful of webhook handlers. If a workflow is one HTTP endpoint and some code, a Cloudflare Worker or AWS Lambda function is cheap and simple. You give up the visual builder, managed OAuth and app actions, so you write the API calls and store tokens yourself. Schedules are handled by Workers Cron Triggers or by an EventBridge schedule for Lambda.

You want an open-source builder that feels lighter than n8n. Activepieces has a builder aimed at less technical teammates, code steps that can use npm packages, and a free self-hosted Community Edition.

Platform notes

Self-hosted n8n

Free Community Edition, plus paid Business and Enterprise licenses. You run it with Docker or npm and own upgrades, backups and uptime. In return you can allow any npm module with NODE_FUNCTION_ALLOW_EXTERNAL (n8n docs) and install Python packages into the task runner image.

Activepieces

Open-source automation builder with a free Community Edition and hosted plans billed in credits. A reasonable choice if the people maintaining workflows after the migration are not developers.

Windmill

Open-source platform built around scripts. Good fit for Pipedream users whose workflows were mostly Node.js or Python code with dependencies.

Trigger.dev

Background jobs written as TypeScript in your own codebase, deployed with its CLI, open source under Apache 2.0. Good for long-running or retry-heavy jobs. Less suited to teams that want a visual editor.

Make and Zapier

Hosted only, with large app catalogs. Expect to rebuild each workflow by hand and to rethink code-heavy steps.

Cloudflare Workers and AWS Lambda

Infrastructure rather than automation platforms. The lowest cost per request at scale, but you build every integration yourself.

Other platforms that come up in migration discussions include Inngest, Temporal and Latenode. We have not compared them in detail here.

How to decide

If your Pipedream workflows are mostly...	Consider
Webhooks, schedules, app actions and short JavaScript	n8n Cloud
The above, plus code steps that need npm packages or Python libraries	Self-hosted n8n
Built and maintained by non-developers	Activepieces, Make or Zapier
Long scripts with dependencies and tests	Windmill or Trigger.dev
A few HTTP endpoints with custom logic	Cloudflare Workers or AWS Lambda

Workflow Exit converts Pipedream workflows to n8n only. The free migration report is still useful whatever you choose: it inventories triggers, actions, npm packages, secrets, connected accounts and data to save before April 30, 2027, and it recommends n8n Cloud or self-hosted n8n based on what your code actually imports. It runs in your browser.

If n8n is your pick, follow the migration guide, start by exporting your workflows, and see pricing for automated conversion. If you are still working out the deadline, the shutdown timeline has every date. The fastest way to know which option fits is to run the report on your own export.