Migrate from Zapier
If you have Zaps you’d like to run on Flowdrome, you don’t have to rebuild them from a blank canvas. The Studio’s Import button reads the Zap export file from your own Zapier account data export and reconstructs each Zap as a Flowdrome workflow — trigger first, steps wired in order, Filters and Paths included.
Honest scope, up front: this imports the structure of your Zaps — which apps, which actions, field mappings, filters, paths — onto Flowdrome’s native nodes. It does not run any Zapier code, and it never imports credentials. Expect a working skeleton you review and finish, not a perfect one-click clone.
1. Export your data from Zapier
In your Zapier account, go to Settings → Data Management and request a data export
(“Export my data”). The archive you receive contains your Zaps as JSON — a file with your zaps
and their steps. That file is what Flowdrome reads. It is your own configuration data, and it
contains no passwords, API keys, or connected-account secrets — Zapier keeps those
server-side, which is exactly why re-connecting accounts is step 3 below.
2. Import the file in Studio
Open the Builder and use Import (the same button that accepts Flowdrome and n8n files),
then pick the export JSON. The importer is deliberately liberal: it accepts the whole export,
a { "zaps": [...] } wrapper, or a single Zap object.
Recognizing a Zapier export opens the Migrate from Zapier wizard:
- Review — every Zap in the export with its mapping fidelity (how many steps map to native nodes, how many land as Unknown placeholders) and any import notes. Tick the Zaps you want.
- Import — each selected Zap becomes its own workflow, named after the Zap.
- Reconnect — the wizard ends with a checklist of every external service the imported workflows use. Exports never include credentials, so each account gets connected once in Admin → Credentials; it also lists any Unknown steps to convert by hand.
What maps to what
| Zapier step | Flowdrome node |
|---|---|
| Schedule by Zapier | Schedule trigger (cron/interval) |
| Webhooks by Zapier — Catch Hook | Webhook trigger |
| Webhooks by Zapier — POST / GET / PUT / Custom Request | HTTP Request |
| Slack — send message actions | Slack |
| Google Sheets | Google Sheets (append / update / read) |
| Gmail — send email | Gmail |
| Filter by Zapier | Filter (the chain continues from its true port) |
| Paths by Zapier | One labeled If gate per path, each branch wired off true |
| Formatter by Zapier — representable text transforms (uppercase, lowercase, trim, replace, default value) | Set with a {{ }} expression |
| Delay by Zapier — Delay For | Wait |
| Digest by Zapier | Digest |
| Code by Zapier — Run JavaScript | JavaScript (code preserved) |
| Trello, Asana, GitHub, Notion, Stripe, Jira, Todoist, Zendesk, Intercom, Mailchimp, and every other service in the Connectors recipe pack | API Call (utility.api) with the matched operation |
Zapier’s {{step__field}} references are translated into Flowdrome {{ }} expressions
({{123__subject}} becomes {{ $json.subject }}). References that reach further back than the
previous step may need a quick touch-up in the editor.
Two behaviors worth knowing:
- Polling triggers. Zapier app triggers (“New Spreadsheet Row”, “New Card”…) work by polling. The importer reproduces that mechanism: a Schedule trigger (15-minute interval, adjustable) feeding the mapped read node.
- Paths. In Zapier, every path whose filter matches will run — so paths import as parallel labeled If gates, not a first-match switch.
What lands as Unknown
Any step without a native equivalent becomes an inert Unknown node that preserves the original app, action, and parameters verbatim — nothing is silently dropped, and the chain stays wired around it. Convert stragglers by hand (often an HTTP Request or API Call node does the job), or leave them as documentation of what the Zap did. Only the first condition of a Filter’s first condition group is carried; add the rest in the editor.
3. Credentials are never imported
The export contains no secrets, and the importer additionally strips anything secret-shaped it finds in step parameters (noted on the node’s label and in the import summary). Re-connect every account in Admin → Credentials and reference them from the imported nodes — see Credentials & variables. Nodes that call external services will fail until their credential is attached; that’s expected on first run.
After the import
- Open each imported workflow and walk the chain left to right.
- Attach credentials, fix any
{{ }}references the translation flagged, and convert or delete Unknown placeholders. - Test with the trigger tester, then deploy to a host.
Flowdrome is not affiliated with, endorsed by, or sponsored by Zapier Inc. “Zapier” is a trademark of Zapier Inc., used here only to identify the export file this importer reads.