Migrate from Zapier to Heym
Move Zaps to Heym. Describe the Zap or paste its steps, watch AI Convert rebuild it as a workflow on a live canvas, then run it on infrastructure you control.
Zapier presents a hosted automation service built on trigger-and-action Zaps, with a large app catalog plus Paths, Filters, Formatter, and Code steps for logic.
When it is worth moving a workflow
Task-based pricing and an AI step are an awkward pair: an agent that loops over tool calls consumes a variable number of tasks for a single piece of work, so the bill stops tracking the value. Teams also move when a Zap grows past what trigger-and-action expresses, into branching, retrieval, review steps, and parallel work.
If you are still deciding rather than moving, the Heym and Zapier comparison covers the evaluation side with links to first-party documentation.
How the move works
- 1
Export from Zapier
Zapier has no single workflow export file, so open the Zap and copy its steps, or simply describe what the Zap 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 Zapier 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 Zapier | In Heym | What changes |
|---|---|---|
| Zap | Workflow | One Zap becomes one workflow, with the linear step order preserved as canvas edges. |
| Trigger step | Cron node, webhook trigger, or an app trigger node | Which one depends on the source: a schedule becomes Cron, an inbound call becomes the workflow webhook trigger, and a supported app becomes its trigger node. |
| Action step | Node | Each action becomes the closest native node, or an HTTP node when the service has no dedicated one. |
| Paths | Switch node | Each path becomes a labelled branch, and paths that do not depend on each other run in parallel. |
| Filter | Condition node | A filter that stops a Zap becomes an explicit true and false branch, so the stopped case is somewhere you can wire. |
| Formatter | Set node with expressions | Text, number, and date transforms become expressions in a Set field rather than a separate step. |
| Code by Zapier | Code node | Heym runs sandboxed Python in a Docker sandbox, so JavaScript is rewritten rather than copied. Review this node closely. |
| Webhooks by Zapier | HTTP node and the workflow webhook trigger | Outbound calls become HTTP nodes; inbound calls become the workflow trigger itself. |
| Storage by Zapier | Variable node or DataTable node | A value carried across a run becomes a Variable; records that persist between runs become a DataTable in your own database. |
| Looping by Zapier | Loop node | Per-item iteration carries over, and independent items can run concurrently. |
| Delay by Zapier | Wait node | Fixed and until-a-time delays both map onto the Wait node. |
| Sub-Zap | Execute node | A called Zap becomes a sub-workflow, which an agent can also invoke as a tool. |
Check these before it goes live
- Connect every app in the Credentials tab. Nothing about a Zap authorization transfers.
- Read the Code step line by line. It is Python now, and it is the most likely place for a behavior difference to hide.
- Give the trigger a new home. Anything that called a Zapier webhook needs the new workflow URL.
- Check Paths that assumed order. Independent branches run at the same time in Heym.
- Run one test execution and compare the output against a recent Zap run.
Zapier migration FAQ
Zapier has no workflow export. How do I migrate a Zap?
Describe it. AI Convert accepts a plain-language description of the automation in any language and builds the matching Heym workflow, which is the practical path for Zaps since there is no single file to export. Pasting the copied step list works too.
Does Heym charge per task?
No. Heym is self-hosted and source-available, so there is no per-task or per-execution charge. What a run costs you is the infrastructure it uses plus whatever the model providers charge, and the model half is tracked per execution in USD.
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.