Pipedream Workflows is shutting down: moving your workflows to Foliot

Pipedream is closing its Workflows product. If you run workflows there, you need a new home before the end of March 2027. This page sets out the dates, which kinds of Pipedream workflows move easily to Foliot, which don't, and how to move one step by step. If Foliot isn't a fit for yours, it says so.

What's happening, and when

From Pipedream's own notice (checked October 15, 2026):

• Workflows (and String) are in maintenance mode: no new sign-ups or subscriptions, and no new features. Existing workflows keep running until then.
• March 31, 2027: Workflows shut down, and subscriptions are cancelled with a prorated refund.
• By April 30, 2027: all Workflows data is permanently deleted, including the credentials for connected accounts.
• Pipedream offers an export tool that downloads each project's workflows as JSON. Pipedream Connect, its product for developers building AI agents, isn't affected.

Export your workflows now, even if you move later: the JSON is the easiest record of what each step did.

At a glance

Foliot is counted in runs: one run each time a workflow's trigger fires, however many steps. The free plan includes 500 runs a month; Pro is $12 a month for 10,000.

Workflows that move well to Foliot

• Webhook in, something out. An HTTP trigger that receives JSON and then writes to Google Sheets, posts to Slack, sends an email, or calls another API.
• Scheduled API calls. “Every hour, call this endpoint”, “every morning, fetch numbers and post them to Slack”, with a check on the response.
• Light code. Code steps that reshape data: pick fields, format dates, build a message. In Foliot, the HTTP request step makes the call and a Code step does the reshaping.
• Simple conditions and loops. “Only continue if…”, two paths, or one action per item of a list (up to 100 items).

Workflows that don't

Be realistic about these; another tool will serve them better:

• Code that needs npm packages, Python, Go or Bash, or code that makes its own network calls. Foliot's Code step is JavaScript only, with no network and no packages.
• Workflows triggered by app events (a new email, a new row, a new issue) unless that app can send a webhook instead.
• HTTP endpoints that must reply with custom data. Foliot's webhook answers straight away (202 when the request is accepted) with no custom response body, and runs the workflow in the background.
• Schedules more often than every minute, or long-running code (Foliot stops code after 5 seconds).
• Workflows that keep state between runs in a data store. Foliot has no data store.

Moving a workflow, step by step

1. Export the project from Pipedream and open the JSON next to the workflow, so you can see each step's settings and code.
2. Pick the trigger. An HTTP trigger becomes When a webhook is received (POST, JSON, form or text body up to 256 KB). A schedule becomes On a schedule: every N minutes or hours, daily, or on chosen weekdays, in your timezone.
3. Send one test event. With the Foliot workflow off, send a sample request so its fields appear in the data picker.
4. Rebuild the steps. Prebuilt Slack, Google Sheets and email actions become Post to Slack, Add row to Google Sheets and Send email. Other actions become an HTTP request to that app's API, with its key stored once as an “API credentials” connection. A code step that calls an API and transforms the result becomes an HTTP request followed by a Code step.
5. Add the logic. Early exits become Filter; if/else becomes Branch; loops become For each; waits become Delay.
6. Test each step with Test this step, point the sender at the new webhook URL, turn the Foliot workflow on, and turn the Pipedream one off.

Reconnect accounts in Foliot rather than copying secrets around: Google through Google's own sign-in, Slack through an incoming webhook URL, other APIs through a new API key.