Migrate from Pipedream to Heym
Move Pipedream workflows to Heym. Paste the workflow or describe it, watch AI Convert rebuild each step on a live canvas, then run it on your own servers.
Pipedream presents a hosted integration platform where workflows chain triggers and steps, with code steps in Node.js or Python and a large registry of prebuilt actions.
When it is worth moving a workflow
Code-first automation runs into the same wall as every other kind once a model enters it: the interesting failures stop being exceptions and start being wrong answers. Teams move when they need the payload the model saw, the cost of the run, and an approval gate, without building that layer around their own code.
If you are still deciding rather than moving, the Heym and Pipedream comparison covers the evaluation side with links to first-party documentation.
How the move works
- 1
Export from Pipedream
Open the workflow in Pipedream and copy its steps and code, or describe what the workflow does in your own words. AI Convert accepts either.
- 2
Paste it into AI Convert
A safety check runs, then each construct is mapped to the closest native Heym node and streamed onto a live canvas while you watch.
- 3
Review, download, and import
Read the rebuilt workflow, download or copy it, import it into your own instance, and attach your credentials.
What each Pipedream concept becomes
A reviewer's guide to the rebuilt workflow. Constructs without an exact equivalent are mapped to the closest Heym primitive, which is why the result is worth reading before it handles real traffic.
| In Pipedream | In Heym | What changes |
|---|---|---|
| Workflow | Workflow | One workflow becomes one canvas, with the step order preserved as edges. |
| HTTP and schedule triggers | Workflow webhook trigger and Cron node | An inbound call becomes the workflow trigger itself, so the URL is new; a schedule becomes a cron expression with a timezone. |
| App trigger | Trigger node for that service | Supported services have dedicated trigger nodes; anything else becomes a scheduled HTTP poll. |
| Code step | Code node | Python steps convert directly; Node.js steps are rewritten, since the Heym Code node runs sandboxed Python. |
| Prebuilt action from the registry | Integration node or HTTP node | Each action becomes the closest native node, or an HTTP node when the service has no dedicated one. |
| Connected account | Credentials tab | Account authorizations are recreated as encrypted credentials in your own instance. |
| Data store | DataTable node | Records that persist between runs move to a DataTable in your own database. |
| steps.foo.$return_value | Expression DSL, for example $nodeName.field | Step references are rewritten to name the upstream node, usable in any string field on the canvas. |
| Flow control and delays | Condition, Switch, and Wait nodes | Early exits become explicit branches, which makes the stopped path something you can wire rather than a return statement. |
| Concurrency and queue settings | Parallel DAG execution and the run queue | Independent nodes run concurrently by default, and multiple runs execute in isolation from each other. |
| Invoking another workflow | Execute node | Sub-workflow composition is preserved, and an agent can also call another workflow as a tool. |
Check these before it goes live
- Read every converted code step. Node.js became Python, and this is where behavior differences hide.
- Recreate connected accounts in the Credentials tab.
- Update the trigger URL anywhere an external system posts into the workflow.
- Check any step that relied on running after another without a real data dependency, since independent nodes now run in parallel.
- Run one test execution and compare the output against a recent run on the source side.
Pipedream migration FAQ
Pipedream workflows are mostly code. Does that convert?
Python steps convert directly into the sandboxed Code node. Node.js steps are rewritten into Python, which works well for transformations and API calls but deserves a line-by-line read where the step used platform-specific helpers.
What replaces Pipedream data stores?
The DataTable node, backed by your own PostgreSQL. Records persist between runs the same way, with the difference that the data lives in a database you operate.
Do my credentials come across?
No, and that is deliberate. Exported workflow files hold no API keys or secrets, so AI Convert rebuilds the structure only and you attach your own credentials in the Heym Credentials tab afterwards. Nothing copies a secret between two systems on your behalf.
Is the converted workflow ready to run?
Treat it as a reviewed starting point rather than a finished port. Open it on the canvas, attach credentials, run one test execution, and adjust any node that was mapped to the closest Heym primitive rather than an exact equivalent.
Can I run the result on my own infrastructure?
Yes. Heym is source-available under an MIT license with a Commons Clause and runs on your own servers with Docker or Kubernetes, so migrated workflows, their credentials, and their model calls stay inside your environment.
Moving from something else
AI Convert reads exports from 12 tools, and it also accepts a plain description of the automation when there is no file to export.