Move workflows from one platform to another
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
What counts as done
Each source workflow has a target workflow that validates, with a checklist of credentials to reconnect and code steps changed, and a side-by-side run gives the same writes with no events missed at cutover.
How agents ask for it: move my Pipedream workflows to n8n before the shutdown
, convert this Zapier zap to Make
, port these n8n workflows into code
Does the job, with a limit 13
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| Activepieces API + MCP C Activepieces Inc. | No importer for n8n, Zapier or Pipedream exports is documented; an agent rebuilds each flow with ap_build_flow and code steps in JS or TS. Duplicated or imported flows lose connections, which need reconnecting. source |
| Microsoft Copilot Studio MCP D Microsoft Corporation | get_definition reads a workflow and create saves a new draft, so an agent can re-author from another platform's export, but no importer is documented and connections are rebuilt with setup_connection. source |
| Kestra C Kestra Technologies SAS | flows/import and flows/export/by-ids move Kestra YAML, and scripts run in many languages, but there is no importer for n8n, Zapier or Pipedream exports, so an agent rewrites each one. source |
| Kognitos C Kognitos, Inc. | :export and automations:import move Kognitos ZIP bundles with connection and trigger re-wiring by mapping, but nothing imports another platform's export; an agent re-describes each workflow to the builder. source |
| Make API + MCP B Celonis, Inc. | Blueprints export as JSON and Create scenario takes one, with versions kept 60 days, but nothing imports n8n, Zapier or Pipedream exports and connections are recreated by hand. source |
| n8n API + MCP D n8n GmbH | Workflows export and import as JSON and .n8np packages, but nothing imports a Pipedream export, tokens don't travel and about 7 in 10 code steps need rewriting (acc-41); Cloud's Code node allows only crypto and moment and no HTTP. source |
| Node-RED B OpenJS Foundation | Flows move as JSON through GET and POST /flow, but nothing imports another platform's export, and there is no run log for a side-by-side comparison. source |
| Pipedream API + MCP BB Pipedream, LLC | As a source, project export gives one JSON per workflow with a manifest that names omitted secrets, but nothing imports it (acc-41), tokens don't export and most code steps reading account tokens need rewriting (acc-46). source |
| Microsoft Power Automate C Microsoft Corporation | Solution flows export and import through ExportSolution, but nothing imports another platform's export, and flows under My flows must first be moved into a solution. source |
| Prismatic C Prismatic Software Inc. | importIntegration takes a YAML definition and prism_integrations_convert turns low-code into code-native, but nothing imports another platform's export; an agent rewrites each workflow in TypeScript or YAML. source |
| Tray.ai API + MCP C Tray.ai, Inc. | An agent can rebuild each workflow through Headless from a description or another platform's export, with validation, but no importer for n8n, Zapier or Pipedream exports appears in the docs index. source |
| Windmill API + MCP D Windmill Labs, Inc. | Scripts in many languages ease porting code steps, but no importer for n8n, Zapier or Pipedream exports was found; an agent rebuilds each flow as drafts and deploys. source |
| Workato API + MCP C Workato, Inc. | Recipe versions are readable and recipes can be copied, but no importer for another platform's export was found; an agent rebuilds each recipe through AIRO. source |
Doesn't do this job 5
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Bind AI F 1Fort Inc. | No workflow definitions to export or import. source |
| Gumloop C AgentHub Inc. (doing business as Gumloop) | No importer for another platform's workflow JSON, and the target is a prompt-driven agent, so a step-by-step workflow has no equivalent that validates step for step. source |
| Cooper (Mandl) F Cooper AI Tech, Inc. | No workflow export or import. source |
| Motive Agents F Motive Technologies, Inc. | No Agent definition export or import. source |
| Paragon ActionKit + MCP D Forge Technology, Inc. (d/b/a Paragon) | No importer for other platforms' exports; Paragon workflows are per-integration embedded logic, and Paragraph exports only Paragon's own projects. source |
What stops agents finishing
- no importer for the source export
- tokens and run history are not exported
- target's code step cannot import packages or call HTTP (n8n Cloud)
Around it
Before: workflow-automation.debug-failed-run. After: workflow-automation.build-workflow, workflow-automation.connect-app-accounts.
Where this comes from
Weight 7 of 100 in Workflow automation: 4 of 48 accounts (Pipedream Workflows shutdown threads, n8n-to-code moves); driven by one event
The same as data: /api/v1/use-cases/workflow-automation.migrate-workflows.json, or the MCP tool get_use_case with id workflow-automation.migrate-workflows. Other jobs in this category: /api/v1/niches?category=workflow-automation.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.