When does Pipedream Workflows shut down?

On March 31, 2027. Pipedream deletes all Workflows data by April 30, 2027, including the credentials and OAuth tokens of connected accounts. Pipedream Connect is not affected.

Do my *.m.pipedream.net webhook URLs keep working?

Until March 31, 2027. Point each provider at an AnyHook URL now, forward it to your Pipedream endpoint until the code has moved, and the provider never needs a new URL again.

Will my Node.js code steps run on AnyHook?

A step that uses fetch, axios or @pipedream/platform runs as written, including defineComponent, steps.trigger.event, $.export and $.flow.exit. Steps that need other npm packages, Python, connected accounts or $.respond need changes.

Can I move my workflows to n8n, Make or Zapier instead?

Yes. Put an AnyHook URL in front of their webhook URL: you keep a log of every event and its retries, and moving again later is a destination change rather than a new URL at every provider.

Moving off Pipedream

Updated October 15, 2026

Pipedream Workflows shuts down on March 31, 2027, and every …m.pipedream.net URL stops with it. If your workflows start from a webhook, a schedule or an email, AnyHook gives each one a URL you keep and runs your Node.js code steps as written. You change the URL at each provider once.

What Pipedream is shutting down

Workflows and String stop on March 31, 2027. Pipedream no longer takes new signups or subscriptions.
All Workflows data is deleted by April 30, 2027, including the credentials and OAuth tokens of connected accounts.
Pipedream Connect, its API, MCP servers and API proxy, carries on.
The export tool downloads the structure of your workflows as JSON, one project at a time.
requestbin.com now redirects to Pipedream's home page.

Source: Pipedream's announcement.

What moves to AnyHook

On Pipedream

On AnyHook

HTTP trigger: An app's URL, in.anyhook.net/you/app. It answers the sender in about a second, keeps every event, and retries delivery: 5 min → 30 min → 3 h → 18 h, then daily. Renaming the app does not change it.
Node.js code step: The app's code, run in a sandbox on every event. defineComponent, steps.trigger.event, $.export and $.flow.exit work as written; fetch, axios and @pipedream/platform are there.
Schedule trigger: A cron on the same code, UTC or any time zone. Each run arrives as an anyhook.schedule event.
Email trigger: Every app has an address, you.app@anyhook.net. Mail arrives as an email.received event with the sender, the subject and the raw message.
Environment variables: Secrets, read as env.NAME.
Event history and replay: The event log: each event with every delivery attempt, the code's logs as its response, and a replay button. Kept 3 days on Free, 1 year on Pro.

What does not move

AnyHook runs your code on events. It is not a workflow builder, so these need a rewrite or another home:

Pre-built actions and connected accounts. A step that reads this.slack.$auth needs the service's API key as a secret and a fetch to its API.
npm packages other than axios and @pipedream/platform, and Python steps. Not yet.
$.respond(). AnyHook answers the sender itself, so a workflow that must send its own HTTP response, a Slack slash command for one, needs a server that answers in time. Meta's verification handshake is answered for you.
Triggers that poll an app, such as a new row in a Google Sheet, and data stores.

For those, n8n, Make and Zapier have the integrations. An AnyHook URL can still sit in front of their webhook URLs, so the next move is a destination change too.

The move, one workflow at a time

Create an app and add your Pipedream endpoint as its destination. Nothing changes yet: Pipedream still runs the workflow, and AnyHook keeps each event on the way.
At each provider, replace the Pipedream URL with the app's URL. It is the last time you edit it there.
Paste the code step into the app's Code and add its secrets. It saves switched off. Run it on the latest stored event and read its logs. A test run does whatever the code does, so point it at a test channel or table first if it writes somewhere.
Turn the code on, wait a minute, then remove the Pipedream destination. A change takes up to a minute to reach every edge location, so events in that minute can run in both places.
Repeat before March 31, 2027. Moving again later, to n8n or a server of your own, is a destination change; the providers keep the URL.

With an agent

AnyHook's MCP server, https://anyhook.net/mcp, has the tools for this: anyhook_apps_create, anyhook_code_deploy and anyhook_code_test. Give Claude Code or Codex your Pipedream export and ask it to create one app per HTTP trigger, deploy each code step switched off, and test it on a stored event. You turn each one on. Connecting an agent.

What it costs

Free, $0: 1 app, 10,000 events a month, no code. Enough to hold one URL in front of Pipedream or n8n.
Pro, $20 a month: 10 apps, 50,000 events, 5,000 code runs of up to 105 s each.
Scale, $90 a month: 50 apps, 250,000 events, 25,000 code runs of up to 285 s each.

One app is one URL and its code, so 10 workflows with HTTP triggers fit Pro. Pricing.

Create your first app Read the docs

Questions

When does Pipedream Workflows shut down?: On March 31, 2027. Pipedream deletes all Workflows data by April 30, 2027, including the credentials and OAuth tokens of connected accounts. Pipedream Connect is not affected.
Do my *.m.pipedream.net webhook URLs keep working?: Until March 31, 2027. Point each provider at an AnyHook URL now, forward it to your Pipedream endpoint until the code has moved, and the provider never needs a new URL again.
Will my Node.js code steps run on AnyHook?: A step that uses fetch, axios or @pipedream/platform runs as written, including defineComponent, steps.trigger.event, $.export and $.flow.exit. Steps that need other npm packages, Python, connected accounts or $.respond need changes.
Can I move my workflows to n8n, Make or Zapier instead?: Yes. Put an AnyHook URL in front of their webhook URL: you keep a log of every event and its retries, and moving again later is a destination change rather than a new URL at every provider.