Pipedream alternatives: picking a replacement by what your workflows actually do

Pipedream Workflows stops running on March 31, 2027, and its export gives you a JSON reference to rebuild from, not a file another platform can import. The best Pipedream alternatives depend on what each workflow does: a webhook gateway for receive-and-forward jobs, Trigger.dev or Inngest for code-heavy jobs, and n8n, Make or Zapier for visual automations.

By the end of this guide you'll know the exact deadlines, what the export leaves behind, and which replacement fits each kind of workflow, with prices checked on each vendor's own pricing page as of October 2026. That matters because every workflow you rebuild in the wrong tool is one you'll rebuild twice.

Pipedream Workflows shuts down on March 31, 2027

According to Pipedream's Workflows documentation, Workflows and String shut down on March 31, 2027. Workflows is in maintenance mode: existing workflows keep running normally until that date, no new features will ship, and Pipedream is no longer accepting signups or subscriptions.

The second date matters more. All Workflows data, including credentials and OAuth tokens for connected accounts, will be permanently deleted by April 30, 2027. Subscriptions stay active until March 31, 2027 and are then canceled automatically with a prorated refund.

Is Pipedream Connect affected by the shutdown?

No. Pipedream's notice says Pipedream Connect settings and credentials will not be affected. If you use Pipedream only to give your own app or AI agent access to third-party accounts through Connect, nothing in this shutdown forces a move. Everything below is for people running workflows.

The export is a blueprint, not a migration

The export tool documentation describes a ZIP per project, with one JSON file for each workflow plus a manifest.json listing them. Each file holds the workflow's name, settings, triggers, steps, control-flow branches and latest deployed version. Pipedream presents it as a reference for rebuilding on another platform; the page describes no import into anything, Pipedream included.

What the export leaves out is the list to plan around:

• Secret prop values are replaced with a redacted placeholder.
• Connected accounts keep only an ID; tokens and other credentials are removed.
• Environment variables are not exported, so you re-enter them on the new platform.
• Event history, data stores and File Store files are not exported and must be downloaded separately.
• Code for private multi-file components is not exported, so keep your own copy of that source.

There are mechanical limits too. One export holds up to 500 workflows or 256 MB, whichever comes first, and the ZIP is written to the project's File Store, so your plan must include File Stores. Larger projects have to be split before exporting.

How to export Pipedream workflows before shutdown

1. Open the project in the Pipedream dashboard and select Settings.
2. Click Export Workflows at the bottom of the settings panel.
3. Download the project_export ZIP from the File Store when it finishes.
4. Repeat for every project, since export works one project at a time.
5. Download data stores and File Store files separately, and write down every environment variable and connected account each workflow uses.

Do this now, not in March. Re-authorizing every connected account on the new platform is the slow part of any migration, and the export tells you which accounts you'll need but not their credentials.

Sort your workflows before you compare Pipedream alternatives

A single replacement for everything is the obvious goal, and it's a reasonable one if you have ten workflows of the same shape. Most Pipedream accounts mix three kinds of work, though, and each kind has a natural home:

Prices are list prices from each vendor's pricing page as of October 2026 and change often. The sections below give the source for each.

Pipedream alternative for webhooks: a gateway in front

If a workflow's job is to accept an HTTP request, reshape the payload and pass it on, you need delivery guarantees more than a canvas. Plan for the Pipedream HTTP endpoint your senders call to stop working at shutdown, which means every sender has to be repointed anyway.

Hookdeck's pricing page lists a free Developer plan with 10,000 events a month and 3 days of retention, a Team plan from $39 a month, and pay-as-you-go events at $3.00 per 100,000 up to 5 million a month, with retries included in the event price. Hookdeck publishes its own Pipedream migration guide, so read its comparisons as a vendor's.

If you'd rather write the handler yourself, Cloudflare Workers pricing gives 100,000 requests a day on the free plan, and the paid plan starts at $5 a month with 10 million requests included. AWS Lambda is the equivalent if your stack already lives on AWS.

Skip this route if the workflow does real work after receiving the event, such as calling three APIs and waiting on one of them. A bare function then makes you build retries and state yourself, which is what the next group exists for.

Code first alternative to Pipedream: Trigger.dev and Inngest

If you used Pipedream mainly for its code steps, Trigger.dev and Inngest keep the code-first model and add durable execution: each step's result is saved, so a failure retries from the failed step instead of starting over.

Trigger.dev

Trigger.dev runs TypeScript tasks. Its pricing page lists a free plan with $5 of monthly usage credit, 20 concurrent runs, 10 schedules and 1 day of log retention; Hobby is $10 a month and Pro $50 a month. Compute is billed per second by machine size, and time spent in waits longer than 5 seconds isn't billed. Each run also carries an invocation charge of $0.25 per 10,000 runs, which is worth modeling if you fire many tiny jobs. It is open source under Apache 2.0 and can be self-hosted.

Inngest

Inngest offers SDKs for TypeScript, Python and Go. Its pricing page lists a free plan with 50,000 executions a month and 24 hours of trace history, and Pro from $99 a month with 1 million executions. Each step counts as an execution, so a function with five steps uses six. The free plan has no metered overage: execution pauses at the quota until you upgrade, which is fine for testing and risky for production webhooks. Inngest says its engine is open source and can be self-hosted.

Pipedream vs Trigger.dev vs Inngest

The catch with both is the one that matters most after a Pipedream migration: you manage third-party credentials and OAuth flows yourself, where Pipedream stored them for you as connected accounts. If your Python steps matter, Inngest has a Python SDK and Trigger.dev's tasks are TypeScript. Skip both if nobody on the team wants to own a code repository for automations.

Visual alternatives: n8n, Make, Zapier and Activepieces

For workflows that connect SaaS apps with light logic, a visual builder is the closest match to how Pipedream's step editor felt, and each of these four bills on a different unit.

Is n8n a good replacement for Pipedream?

n8n is the closest fit for developers, because its canvas allows JavaScript and Python code nodes. The n8n pricing page bills per workflow execution regardless of how many steps run: Starter is 20€ a month billed annually for 2,500 executions, Pro 50€ for 10,000. A cloud trial needs no credit card and includes 1,000 executions. A self-hosted Community edition runs free without a license key. n8n describes itself as fair-code under its Sustainable Use License rather than open source, so read those terms before you build it into a product you sell.

Zapier

Zapier is the choice when non-developers will own the workflows. Its pricing page lists a free plan of 100 tasks a month limited to two-step Zaps, with webhooks only on paid plans; Pro starts at $19.99 a month billed annually for 750 tasks. Each successful action step uses a task, while triggers and built-in tools such as Filter and Formatter don't. Code by Zapier steps also use tasks, so moving Pipedream code steps there doesn't avoid the meter. Skip Zapier if your workflows handle high webhook volume, since per-task pricing grows with every step.

Make

Make bills in credits, and most actions cost one. Its pricing page lists 1,000 credits a month on the free plan. We couldn't find paid plan prices in the text of that page, so check it directly before you budget.

Activepieces

Activepieces charges one credit per run regardless of step count, according to its pricing page: Free includes 1,000 credits a month and Plus is $20 a month for 10,000. The self-hosted Community Edition is free and MIT-licensed, and its integrations are TypeScript npm packages, which suits a developer who wants a visual tool they can extend.

What is the best alternative to Pipedream?

There isn't one, and a vendor page that says otherwise is selling. If most of your workflows are webhook relays, a gateway plus a small function is cheaper and, in our view, simpler to run than a full automation suite. If they are multi-step code, Trigger.dev or Inngest keep the model you know. If they connect apps for a business team, n8n suits developers and Zapier suits everyone else.

The strongest case for one tool is maintenance: two platforms means two bills and two places to debug. That's a fair argument for teams with a handful of workflows, and for them n8n is the most flexible single landing spot because it mixes visual nodes and code. Teams with dozens of high-volume webhooks should still split them off.

Your next step before April 30, 2027

Export every project this week, then list each workflow with its trigger, connected accounts and environment variables, and tag it webhook, code or visual. That list decides your shortlist.

As of October 2026, Upfynd lists 297 products in Automation & No-Code and 194 in APIs & Integrations, each with pricing, screenshots and similar products on one page, so you can compare the tools above against the rest before you rebuild anything.