Comparison · updated October 2026
Pipedream alternatives after the Workflows shutdown
Short answer. Pipedream Workflows shuts down on March 31, 2027. If most of your workflows are Node.js or Python code steps, n8n or Windmill are the closest fit, and both can run on your own server. If you'd rather keep calling the same Pipedream components, build on Pipedream Connect, which is not shutting down. No-code tools like Make or Zapier work best for simple, action-only workflows.
The options at a glance
| Option | Good for | Watch out for |
|---|---|---|
| n8n | Visual workflows with JavaScript and Python Code nodes, 400+ app nodes, AI agents. Self-host for free or use n8n Cloud. | Credentials have to be reconnected; npm modules only on self-hosted n8n. |
| Windmill | Code-first teams: scripts and flows in TypeScript, Python, Go, Bash and more. Open source, self-hostable. | Users moving from Pipedream mention no built-in equivalent of data stores and more manual OAuth setup. |
| Pipedream Connect | Keeping the same Pipedream components and managed auth, called from your own code or backend. | You write and host the orchestration yourself; it is an API, not a workflow builder. |
| Make / Zapier | Simple workflows built from pre-built actions, for non-developers. | Code steps are limited and pricing is per operation or task, which adds up at volume. |
| Plain code (Cloudflare Workers, Lambda, a small server) | A handful of workflows that are mostly code anyway. | You own retries, logs, schedules and secrets. |
Migration services
Several companies offer to move your workflows for you, each to its own platform: Trelium (free migration to Trelium), Rivulo (runs your steps on Pipedream Connect) and Glow have posted offers in Pipedream's community Slack. That is a good option if you want a managed service and are fine with moving to that vendor.
If you want to end up on an open tool you control, n8n is the destination with the most community, templates and hosting options. MigrateFlows is a free, open-source converter for exactly that path.
How to choose
- Mostly code steps, want to keep a visual view: n8n.
- Mostly code steps, prefer code-first and Git: Windmill.
- Many pre-built Pipedream actions you don't want to rebuild: Pipedream Connect, or a service built on it.
- Few, simple workflows and no developers: Make or Zapier.
- Hundreds of workflows and a hard deadline: convert in bulk first, then review the checklist of what needs manual work.
Whatever you pick, before March 31
- Export every project now. The export works one project at a time and skips workflows that were never deployed. See how to export your Pipedream workflows.
- Download your data stores and File Store files and copy your environment variables: the export doesn't include them.
- List which apps each workflow connects to, so you can reconnect those accounts in the new tool.
- Plan the webhook switch: every service that calls a Pipedream URL needs the new one.
Step-by-step plan for n8n: How to migrate Pipedream workflows to n8n.