Pipedream Workflows is switching off.
Yours don't have to.
Rivulo runs on Pipedream Connect, the same managed auth and app components your workflows use today, so the switch is mostly wiring. We rebuild each workflow, you reconnect your accounts in one sitting, and we run both side by side until the outputs match. You don't rebuild anything.
- 01Export your projectTwo clicks in Pipedream. Send us the ZIP.
- 02We rebuild it, freeNo migration fee. Run side by side until outputs match.
- 03Retire the old versionsWe keep the new ones running and fix what breaks.
Is Pipedream shutting down? Only Workflows.
Pipedream is shutting down its Workflows product on 31 March 2027 and deleting Workflows data on 30 April 2027. Pipedream Connect, its integration API, is not affected. Rivulo migrates Workflows projects from the export ZIP onto our platform, which runs on Pipedream Connect, so your steps keep calling the same components.
- 31 Mar 2027
- Every Pipedream workflow stops running, including legacy v1 workflows.
- 30 Apr 2027
- Pipedream deletes Workflows data. Export and download anything you need before then.
- Not affected
- Pipedream Connect: the Connect API, MCP servers and API proxy.
- How to export
- Project → Settings → Export Workflows. The ZIP lands in the project's File Store. One project at a time, up to 500 workflows or 256 MB each.
Check what's in your Pipedream export
See exactly what you're moving, before you talk to anyone.
Drop the project_export-<id>.zip from your Pipedream File Store. You get every workflow, the apps you'll need to reconnect, the code steps, and how each one lands on Rivulo.
| Workflow | Trigger | Steps | Route on Rivulo |
|---|
This is a first read of the structure. We confirm the detail on the call.
Book a call with thisWhat's actually in a Pipedream export
- Every step is a "CodeCell"Registry actions too. The action shows up as
uses.key, e.g.sharepoint-upload-file, withregistry: true. - Never-deployed workflows have no fileThey're listed in
manifest.jsonasskipped_never_deployed. A project can export as just the manifest. - Connected accounts are named, not redactedA prop like
sharepoint: {authProvisionId}tells you which app each step signs in to. - Not everything is redactedPicked site and folder IDs with their labels, and code-step test data, come through as-is.
- Triggers can be missingThe
triggersarray can be empty, so check how each workflow was started.
"schema": "workflow.json/2026.01", "triggers": [], "steps": [{ "namespace": "create_csv_file", "type": "CodeCell", "lang": "nodejs20.x", "uses": { "registry": false, "code": "…" } }, { "namespace": "upload_excel_to_sharepoint", "type": "CodeCell", "uses": { "key": "sharepoint-upload-file", "registry": true }, "props": { "sharepoint": { "authProvisionId": "apn_…" }, "folderId": "<redacted>", "siteId": { "__lv": { "label": "Communication site" } } } }]
What carries across from Pipedream, and what doesn't
We handle, you do nothing
Rivulo- Registry actions and app triggersSame Pipedream components, run through Connect.
- SchedulesExported in full, timezone included.
- Node.js code stepsPorted and tested against real payloads.
- Python, Go and Bash stepsRewritten, outputs checked against the original.
- If/else, switch, delaysRebuilt from the branch layout in the export.
Needs you, once
One call- Reconnect your accountsPipedream Connect's own sign-in screens, the ones you know.
- Confirm redacted settingsThe export keeps field names, so we know what's missing.
- Swap webhook URLsWe list every sender, or update them ourselves with access.
- Download data stores and filesNot in the export. Grab them before 30 Apr 2027.
How the migration works: five steps, two of them yours
- 01
Export
Download the ZIP from each project's File Store.
You · minutes - 02
We map and build
Every workflow gets a route. First batch live within a week.
Rivulo - 03
Reconnect
One screen share to sign in to your apps.
You · one call - 04
Side by side
Both run on the same events until outputs match.
Rivulo - 05
Retire the old ones
We monitor every run and fix what breaks.
Rivulo · ongoing
No export button? Legacy v1 and never-deployed workflows don't export. Share your screen and walk us through them instead, plus anything that never made it into Pipedream.
Book a walkthroughPipedream Workflows alternatives, compared
| Rivulo (done for you) | Rebuild on n8n | Rebuild on Windmill | |
|---|---|---|---|
| Who rebuilds it | We do, from your export | You, node by node | You, as scripts and flows |
| Pipedream actions | Same components, via Pipedream Connect | n8n nodes or HTTP requests | Scripts calling each API |
| Node.js code steps | Ported and tested by us | Code nodes, adapted by you | TypeScript scripts, adapted by you |
| Your accounts | One call, Pipedream's sign-in screens | Re-added as n8n credentials | Re-added as Windmill resources |
| When an API changes | We fix it | You fix it | You fix it |
| Migration cost | None, we do it free | Your team's time to rebuild | Your team's time to rebuild |
| Ongoing cost | Based on number of workflows | Plan or hosting, plus upkeep | Plan or hosting, plus upkeep |
| Best for | Workflows the business runs on | A few simple workflows | Code-first developer teams |
For a few simple workflows, rebuilding yourself is probably right. For dozens that run the business, the rebuild is the easy part. Owning them afterwards is the cost.
Book a migration callMoving is free. Running it is our job.
Rivulo is a done-for-you automation service. We design, build, run and maintain every workflow, and fix it when an app changes. There's no migration fee. Your price is based on how many workflows we run, and you keep the documentation and credentials.
Before you send the ZIP
Anything else, ask us on a call. It's 30 minutes and you leave with a plan.
Book a callIs Pipedream shutting down?
Only its Workflows product. Workflows stops on 31 March 2027 and its data is deleted on 30 April 2027. Pipedream Connect is not affected, according to Pipedream's announcement.
Is there a cost to migrate?
No. There's no migration fee. We rebuild, reconnect and test your workflows for free, then your price is based on how many workflows we run for you.
Are you part of Pipedream?
No. Rivulo is an independent UK company. We build on Pipedream Connect, which Pipedream has said is unaffected by the Workflows shutdown, and that's why so much of your workflow carries across.
What happens to my webhook URLs?
They change. Every HTTP trigger gets a new Rivulo endpoint, and the migration plan lists each one next to the workflow it belongs to. If the sending system is one we have access to, we update it ourselves.
I have 180 workflows. Is that realistic before March?
Yes, if we start soon. We move them in batches, the ones that would hurt most if they stopped go first, and each batch runs side by side before anything is turned off on Pipedream.
We're an agency running workflows for clients.
Each client project exports separately, which suits us fine. Talk to us about how you'd like it set up: under your clients' accounts, or managed by you with us doing the build and maintenance.
Why not just move to n8n or Windmill myself?
You can, and for a handful of simple workflows you probably should. The cost is the same one you've just been hit with: you rebuild everything, then you maintain it, and you're exposed if that platform changes direction too. With us, the building and the maintaining are our job. See the side-by-side comparison.
What if Rivulo disappears?
Fair question, given the week you've had. You keep the documentation for every workflow, and the credentials stay in your own accounts. If you leave, you leave with a written spec of everything that runs.
Is my export safe on this page?
The checker runs in your browser and doesn't send the file anywhere. Pipedream strips passwords, tokens and most settings from the export, though some settings and test data in code steps come through as-is, so treat the ZIP like any internal document.
Hand over your Pipedream export this week
A 30-minute call. Bring the ZIP, or the summary from the checker, and you'll leave with a migration plan and a date. First batch live within a week, and there's no migration fee.