How to migrate from Pipedream to FlowRunner
Migrate Pipedream workflows to FlowRunner before March 31, 2027: export each project, connect FlowRunner Prompt to Flow, convert one workflow at a time, then test and switch.
Pipedream Workflows shuts down on March 31, 2027, and everything in it, including your connected-account credentials, is deleted by April 30.
FlowRunner Prompt to Flow does the rebuilding. You give it one workflow from Pipedream’s export, or its GitHub Sync files, and it builds the same flow in your FlowRunner workspace, code steps included. What’s left for you is connecting accounts, filling in secrets, and testing.
This is the short version. For a piece-by-piece map, read the Pipedream shutdown guide. For three real workflows converted this way, read how to convert Pipedream workflows to FlowRunner.
1. Export your workflows from Pipedream
Open the project, select Settings, and click Export Workflows at the bottom. The archive builds in the background. When it’s ready, open File Store and download project_export-<project_id>.zip.
- What’s in it: a
manifest.jsonand one JSON file per workflow: the trigger, the steps in order with their settings, and each code step’s source, from the latest deployed version. Never-deployed workflows are skipped. - What’s left out: secrets (shown as
<redacted>), connected accounts (only an ID), environment variables, data store records, File Store files, event history, and the code of private components. - Limits: your plan must include File Stores. One export holds up to 500 workflows or 256 MB. If a project goes past that, the manifest shows
truncated: true, so move some workflows to another project and export that one. - Exporting again: delete the existing ZIP from File Store first, then click Export Workflows.
If the project was synced to GitHub, its workflow.yaml and code step files convert just as well. If neither route works, describe the workflow in the chat and attach a screenshot of each step.
While Pipedream still runs, copy your data store records somewhere safe and save a few real events from each workflow. You’ll test against them in step 5.
2. Connect FlowRunner Prompt to Flow to your AI tool
FlowRunner Prompt to Flow is an MCP server you add to the AI tool you already use. You connect it once and sign in with your FlowRunner account. The server URL is the same for every tool: https://app.flowrunner.ai/mcp.
Claude (web and desktop)
- In Claude, open Settings > Connectors.
- Click + Add, then Add custom connector.
- Enter
FlowRunneras the name andhttps://app.flowrunner.ai/mcpas the server URL. If Claude offers sign-in choices, pick Sign in now and Register automatically, and leave the client ID and secret empty. - Click Add, then Connect, and approve the FlowRunner sign-in page that opens.
- In a chat, click + > Connectors and check that FlowRunner is on.
On Claude's Team or Enterprise plan, an Owner adds FlowRunner once for everyone under Organization settings > Connectors, with the same URL. Each member then finds it under Settings > Connectors and clicks Connect.
Claude Code
-
In your project folder, add the server. Add
--scope userto use it in every project.claude mcp add --transport http flowrunner https://app.flowrunner.ai/mcp -
Sign in, and approve the FlowRunner sign-in page that opens in your browser.
claude mcp login flowrunner -
Check the connection with
claude mcp list. Theflowrunnerline ends in✔ Connected.
ChatGPT
- On the web, open ChatGPT Plugins. ChatGPT connects to MCP servers on chatgpt.com only.
- Click Add, then Add custom MCP server.
- Enter
FlowRunneras the name and, under Connection,https://app.flowrunner.ai/mcpas the server URL. - Choose OAuth, select I understand and want to continue, then Create as a plugin.
- Install the plugin and approve the FlowRunner sign-in page.
- In a chat, type
@and pick FlowRunner.
Whether you can add a custom MCP server depends on your ChatGPT plan and, in a Business, Enterprise or Edu workspace, on your admin's settings.
Codex
-
Add these lines to
~/.codex/config.toml, creating the file if it doesn't exist.[mcp_servers.flowrunner] url = "https://app.flowrunner.ai/mcp" -
Sign in, and approve the FlowRunner sign-in page that opens in your browser.
codex mcp login flowrunner -
Check the connection with
codex mcp list. Theflowrunnerrow showsOAuthin the Auth column.
Cursor
-
Create
~/.cursor/mcp.jsonto use FlowRunner in every project, or.cursor/mcp.jsonin a project folder for that project only. If the file already exists, add theflowrunnerentry inside itsmcpServers.{ "mcpServers": { "flowrunner": { "url": "https://app.flowrunner.ai/mcp" } } } -
Open Customize in the sidebar, then MCPs, and follow the sign-in prompt for
flowrunner.
VS Code (GitHub Copilot)
- Open the Command Palette, run MCP: Add Server, choose HTTP, enter
https://app.flowrunner.ai/mcp, and name itflowrunner. - Open Copilot Chat in agent mode and ask "List my FlowRunner workspaces". The first time, VS Code asks you to sign in: allow it and approve the FlowRunner sign-in page.
- Copilot lists your workspaces. FlowRunner is connected.
On the FlowRunner sign-in page, check the account under Logged in as, tick I recognize and trust this URL, and click Authorize. If you don't have a FlowRunner account yet, the Free plan needs no card, and every new account starts with 14 days of Professional. The setup guide in the docs has every tool step by step.
3. Convert one workflow at a time
Start a new chat for each workflow. Paste this request, then the workflow’s JSON file:
Rebuild this Pipedream workflow as a FlowRunner flow. The JSON comes from Pipedream’s Export Workflows and lists the trigger, each step in order with its settings, and the source of every code step. Secrets show as
and connected accounts as IDs only; environment variables and data stores aren’t in the file. Keep the same behavior. Put JavaScript steps in Custom Cloud Code, rewrite any Python, Go, or Bash step in JavaScript, and tell me which steps import npm packages. Before you build, tell me anything you can’t map one to one, and ask me about anything the file doesn’t say.
For GitHub Sync files, say the input is workflow.yaml plus one file per code step, and that GitHub Sync doesn’t record the trigger’s schedule or URL. If the workflow’s entry in manifest.json has a warnings list, paste that too. Answer the questions, and the flow appears in your workspace.
4. Finish what the export can’t carry
The builder ends each conversion with a short list. Expect some of these:
- Accounts, keys, and secrets. Connect each app once. Save what the export redacted or kept in environment variables in API Keys, and the flow reads it through a placeholder.
- npm packages and private components. These become a custom extension: one JavaScript module you deploy with the FlowRunner CLI, with
node_modulesshipped in the deploy.npx flowrunner init-claudeinstalls Claude Code agents that write it. Start from your own copy of the component source. - Schedules. Set them in the flow’s schedule if your files didn’t carry them.
- Webhook addresses. Callers of a Pipedream URL get the flow’s new External Callback address. A workflow that used
$.respondis called through the blocking Call Flow API, from a server, since the call carries your workspace key. - Approvals. A
$.flow.suspendstep becomes a human-in-the-loop step that reaches the person on email, Slack, WhatsApp, phone, or a Form. Tell the builder who approves and on which channel. - Forms and agent tools. If the flow needs a form, or an AI agent that calls another flow as its tool, the AI tells you which of these to add in the flow editor.
5. Test, then switch over
Run each new flow with the events you saved and compare the output with Pipedream’s. When they match, point the callers at FlowRunner, watch a few days of runs, then turn the Pipedream workflow off. Do it workflow by workflow, well before March 31.
How Pipedream maps to FlowRunner
| Pipedream | FlowRunner | What changes |
|---|---|---|
| Workflow | Flow | A flow can start with any block, not only a trigger. |
| HTTP / webhook trigger | External Callback | The same URL can also resume a run that’s waiting. |
| Schedule trigger | Flow schedule | Once, an interval, daily, weekly, monthly, or cron. |
| App event sources | Integration triggers | Every integration is on every plan. |
| Node.js code step | Custom Cloud Code | JavaScript with fetch, no npm. |
| Steps with npm packages, components | Custom extension | Your own blocks, versioned, with packages shipped alongside. |
| Python, Go, Bash steps | Custom Cloud Code | Rewritten in JavaScript. |
$.flow.suspend | Human-in-the-loop step | FlowRunner sends the request and waits for the answer. |
$.respond | Return Result with the blocking Call Flow API | The caller gets the answer in the same request. |
| Data stores | Shared Memory | Key and value state across runs. |
| Event history | Run history | Every run block by block, with inputs and outputs. |
Quick wins on day one
- One execution per run. A complete run counts once, however long it waits. No credit per 30 seconds of compute.
- Approvals that wait up to 30 days on Free, Starter, and Growth, and up to a year on Professional and above. Pipedream’s suspend auto-cancels after 24 hours by default.
- Unlimited workflows and users on every plan, where Pipedream’s Free plan allowed 3 active workflows.
- A free place to land. The Free plan is $0 with 100 executions a month and no card, and every new account starts with 14 days of Professional.
Want a hand with a bigger migration? Contact us.
Frequently asked questions
How do I export my workflows from Pipedream?
Open the project, select Settings, and click Export Workflows at the bottom. The archive builds in the background. When it's ready, open File Store and download project_export-<project_id>.zip. Your plan must include File Stores, and to export again you delete the old ZIP from File Store first.
What if a project has more than 500 workflows?
One export holds up to 500 workflows or 256 MB. If a project goes past that, the manifest shows truncated as true. Move some workflows to another project and export that one too.
Can FlowRunner convert my GitHub Sync files instead of the export?
Yes. FlowRunner Prompt to Flow reads workflow.yaml and the code step files the same way. GitHub Sync doesn't record a trigger's schedule or URL, so tell it those or set them afterwards.
What happens to my npm packages and custom components?
They become a custom extension: one JavaScript module deployed to your workspace with the FlowRunner CLI, with its node_modules shipped in the deploy. Running npx flowrunner init-claude installs Claude Code agents that write it for you. The export doesn't include private component code, so start from your own copy.
How long do I have?
Pipedream Workflows stops on March 31, 2027, and all its data is deleted by April 30, 2027. Convert and test while your workflows still run on Pipedream, so you can compare results side by side.
Ready to try it?
Start on the Free plan. No card required, and every new account gets 14 days of Professional.