Migrate from Activepieces to Heym
Move Activepieces flows to Heym. Paste an exported flow, watch AI Convert rebuild each piece on a live canvas, then run it on infrastructure you control.
Activepieces presents an open-source automation tool where flows chain triggers and action pieces together, with branches, loops, and a code piece for custom logic.
When it is worth moving a workflow
The move is usually about the AI half rather than the integration half. Once a flow needs an agent that picks its own tools, retrieval over internal documents, an approval checkpoint, and a trace of what the model actually saw, those stop being pieces you add and start being properties of the runtime.
If you are still deciding rather than moving, the Heym and Activepieces comparison covers the evaluation side with links to first-party documentation.
How the move works
- 1
Export from Activepieces
Open the flow in Activepieces and export it as JSON from the flow menu, then copy the file contents.
- 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 Activepieces 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 Activepieces | In Heym | What changes |
|---|---|---|
| Flow | Workflow | One flow becomes one workflow, with the step order preserved as canvas edges. |
| Trigger piece | Cron node, webhook trigger, or an app trigger node | A schedule becomes Cron, an inbound call becomes the workflow webhook trigger, and a supported app becomes its trigger node. |
| Action piece | Node | Each piece becomes the closest native node, or an HTTP node when the service has no dedicated one. |
| Router and branch | Switch and Condition nodes | Multi-way routing becomes a Switch; a two-way check becomes a Condition with true and false edges. |
| Loop on items | Loop node | Per-item iteration carries over, and independent items can run concurrently rather than in sequence. |
| Code piece | Code node | The code piece is TypeScript; the Heym Code node runs sandboxed Python, so this is rewritten rather than copied. |
| HTTP piece | HTTP node | Methods, headers, and body templating carry over with expressions rewritten into the Heym DSL. |
| Storage piece | Variable node or DataTable node | A value carried across a run becomes a Variable; records that outlive the run become a DataTable. |
| Delay piece | Wait node | Fixed delays and wait-until behavior both map onto the Wait node. |
| Connections | Credentials tab | App authorizations are recreated as encrypted credentials in your own instance; none of them transfer. |
| Interpolation such as {{ step.field }} | Expression DSL, for example $nodeName.field | References are rewritten to name the upstream node, and the same expression evaluates identically in preview and in a run. |
Check these before it goes live
- Recreate every connection in the Credentials tab.
- Read the converted code piece line by line. TypeScript became Python, which is the most likely place for a behavior difference.
- Update the webhook URL anywhere an external system calls into the flow.
- Check branches that assumed sequential execution, since independent paths now run at the same time.
- Run one test execution and compare the output against a recent run on the source side.
Activepieces migration FAQ
Can AI Convert read an Activepieces flow export?
Yes. Paste the exported flow JSON into AI Convert. Each trigger and action piece is mapped to the closest native Heym node and streamed onto a live canvas you can download and import.
What happens to a TypeScript code piece?
It is rewritten in Python, since the Heym Code node runs sandboxed Python in a Docker sandbox. Straightforward transformations convert cleanly; anything that reached into Activepieces-specific APIs needs a read-through first.
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.