Pipedream Alternative: Where to Move Your Workflows Before the March 2027 Shutdown

Pipedream Workflows shuts down on March 31, 2027. Pipedream is refocusing on Connect, its integration layer for AI agents, and Workflows is in maintenance mode: no new signups, no new features, and all Workflows data is deleted by April 30, 2027. If you're looking for a Pipedream alternative, the useful question is no longer "which tool is better?" but "where does this workflow belong?", because different workflows have different right answers.

This page helps you sort that out. If you've already decided to move webhook workflows to Webhook Relay, skip to the step-by-step Pipedream Workflows migration guide.

TL;DR

• The deadline. Workflows and String stop on March 31, 2027. Data, including credentials and OAuth tokens, is deleted by April 30, 2027. Pipedream Connect is not affected.
• Webhook-driven workflows (an event arrives, gets transformed, gets delivered) → Webhook Relay. Functions in JavaScript or Lua, a KV store and file store that replace Data Stores and File Stores, scheduled webhooks for timer triggers, and retried delivery, including into localhost and private networks.
• App-to-app orchestration (no webhook in the middle, mostly pre-built actions) → an automation platform such as n8n, Make or Zapier.
• AI agent tool access → Pipedream Connect keeps running; nothing to migrate.
• Export now. Pipedream's export tool writes your workflows as JSON, but leaves out Data Store contents, files and credentials, so pull those separately.

Pick an alternative by workflow type

Most Pipedream accounts mix several kinds of workflow. Classify each one before you pick a destination:

In practice, the workflows that matter most operationally tend to be webhook-shaped: payments, orders, deploys and alerts. Those are the ones with real deadlines attached, and the ones Webhook Relay is built for.

Pipedream Workflows vs Webhook Relay

Pipedream details reflect its shutdown notice and public docs as of October 2026; check pipedream.com for the current state.

What carries over cleanly

State: Data Stores → KV store

The biggest blocker for moving off Pipedream used to be state. Webhook Relay functions now have a KV store that mirrors this.dataStore. It's synchronous, so you drop the await:

// Pipedream:        await this.dataStore.set(event.id, true, { ttl: 604800 })
// Webhook Relay:
const kv = require("kv:events")   // created automatically on first run
if (kv.has(event.id)) {
  r.stopForwarding()              // duplicate: logged, not delivered
  return
}
kv.set(event.id, true, 7 * 24 * 3600)

Values are any JSON up to 256 KiB, with optional per-key TTL, so dedupe, counters, cursors and token caching all port directly. Stores are browsable and editable in the dashboard, much like Pipedream's Data Stores UI.

Files: File Stores → file store

The file store covers what Pipedream File Stores are mostly used for: writing a report or export, reading it in a later run, and handing out a pre-signed download or upload link. The one structural change is that there's no /tmp between steps. You read bytes with files.getBuffer() or pass a files.url() link instead of a local path.

Code steps → functions

A Pipedream workflow's chain of steps usually collapses into one Webhook Relay function attached to the input: parse, branch, reshape, set headers, and let the output deliver. Node steps port almost line for line. Python, Bash and Go steps need rewriting in JavaScript or Lua, which is a good job to hand to a coding agent along with the Webhook Relay Agent Skills.

Where Webhook Relay goes further than Pipedream did

Delivery into private networks

Pipedream runs in its cloud and delivers to public URLs only. Webhook Relay's relay agent makes an outbound connection and forwards webhooks anywhere it can reach:

relay forward --bucket payments http://localhost:8080/stripe
# or an internal host with no public IP
relay forward --bucket payments http://payments.internal:9000/hook

No inbound firewall rules, no public IP, and a Kubernetes operator for delivering straight into a cluster. This is a production capability, not just a local-dev convenience.

Fan-out, static IP and tunnels

One webhook can fan out to multiple destinations, deliveries can leave from a static outgoing IP for strict firewalls, and the same account gives you general-purpose localhost tunnels. Native Service Connections land events directly in AWS S3/SQS/SNS and GCP Pub/Sub/GCS.

Flat pricing

Pipedream billed in credits tied to compute time, which was hard to forecast for spiky webhook volume. Webhook Relay has a free plan and flat paid plans at $9.99/month (Basic) and $79.99/month (Business). See pricing.

Where Pipedream was stronger, and what to use instead

Being honest about scope saves you a wasted migration:

• The app directory. Thousands of pre-built actions are Pipedream's real strength. If a workflow is "when a row is added in Airtable, create a HubSpot contact," move it to n8n, Make or Zapier.
• Python and long-running compute. Webhook Relay functions are short JavaScript or Lua programs. Heavy Python jobs belong on Windmill, Lambda or Cloud Run, and a Webhook Relay function can still sit in front to receive, verify and fan out the triggering webhook.
• Browser automation. No equivalent here.

If you're unsure where a particular workflow should go, contact us with the workflow names. We'll look at the export with you and tell you honestly which parts fit Webhook Relay.

How to migrate

1. Export each Pipedream project (Settings → Export Workflows) and download the ZIP from the project's File Store.
2. Pull state separately. Data Store contents and File Store files are not in the export.
3. Classify each workflow with the table above.
4. Port webhook-shaped workflows to functions, mapping this.dataStore to the KV store and $.files to the file store. Let Claude Code or Codex do the mechanical part with npx skills add webhookrelay/skills.
5. Test each function against a sample request, then point the provider at the new input URL and switch off the Pipedream workflow.

The Pipedream Workflows migration guide covers each step in detail, including the export format, a method-by-method Data Store mapping, and a worked Stripe dedupe example.

Start free, read the functions docs, or compare plans.