Zapier Only Lets Team and Enterprise Plans Export Their Zaps. Here's How to Get Yours Out Anyway.

While I was writing our guide to moving Zaps to FlowRunner, I went to Zapier’s help center to get the export clicks right. The first thing on the page was a line I didn’t expect: Zap export is for Team and Enterprise accounts only.

You can build as many Zaps as your plan allows on Free or Professional. You just can’t download them.

What Zapier’s help center says

Zapier’s article is titled “Import and export Zap workflows in your Team or Enterprise account”. Under “Available on plans” it marks Free and Professional as unavailable and Team and Enterprise as available. I checked it again on November 2, 2026. Here’s what it says:

• The plans. Export and import work on Team and Enterprise. Free and Professional can’t use them.
• The clicks. On a plan that has it, you go to Settings > Security and data > Data management and click the download icon next to Download my Zap workflows.
• Whose Zaps. Unless you’re the account owner or a super admin, you can only export Zaps you own. The owner or a super admin can export everyone’s Zaps with Download private and shared Zap workflows, and Zapier emails that file to the account email.
• The format. JSON only.
• Trials. “Import is not available during your free Zapier trial.”
• After import. You test your app connections and reconnect any that are inactive.

(Zapier’s help article has the full text.)

What that means on Professional

Say you’re on Professional, paying $29.99 a month on monthly billing ($19.99 on annual), and you’ve built a few dozen Zaps over a couple of years. They hold real knowledge about how your business runs: which fields map where, which filters keep the junk out, which steps you added after something broke.

Now you want a backup, or you want to try something else. Zapier’s own export isn’t on your plan. To get the JSON file, you’d move up to Team, which Zapier’s pricing page lists at $103.50 a month on monthly billing ($69 on annual). Otherwise you write the Zaps down yourself.

The same goes for Free. Your Zaps run, but there’s no file of them you can keep.

How other platforms handle it

I looked at how the platforms people usually compare handle the same thing.

• FlowRunner. Exporting a single flow as a JSON file works on every plan, Free included. It’s on the flow’s Version Admin tab, under Start Export, and the file imports again as a new flow or a new version, in the same workspace or another one (the docs have the steps). Bulk workspace export and API export are available from the Growth plan up.
• Make. Each scenario exports as a JSON blueprint from the three-dot menu in the Scenario Builder. Make’s help page names no plan limit for it.
• n8n. The editor’s workflow menu has Download, which saves the workflow as JSON. n8n’s docs make it available on every plan, Cloud and self-hosted.

So on the other three, the thing you built comes out as a file on any plan. On Zapier, it comes out from Team up.

I’ll say what I think plainly. You can build all your Zaps on a cheaper plan, and getting your own work out as a file costs you the Team plan, so to me it looks like a bait and switch. That’s my opinion. Zapier doesn’t say why export sits on Team and Enterprise, and I don’t know their reasons.

I’d rather you could leave FlowRunner whenever you want, and single-flow export on every plan is how that works.

How to get your Zaps out anyway

If you’re on Free or Professional, you don’t need the export file to move a Zap. You need a full record of what each step does, and the Zap editor already shows you that.

There are two ways to capture it:

• Screenshots. Open the Zap in the editor and take a screenshot of each step, starting with the trigger, with its settings panel open so the app, the event, and the fields show.
• Copied settings. Write each step out as text: the app, the event, and every field with its value or mapping. A plain list is enough, like “Step 3: Google Sheets, Create Spreadsheet Row. Sheet: Invoices. Amount: Step 2 total.”

Either one is also a decent backup on its own, even if you stay on Zapier.

To turn that record into a working flow, connect FlowRunner Prompt to Flow to the AI tool you already use (Claude, ChatGPT, Claude Code, Codex, or Cursor), attach the screenshots or paste the notes, and ask it to rebuild the Zap. It builds the same flow in your FlowRunner workspace. Before it builds, it tells you what it can’t map one to one and asks about anything your screenshots don’t show, like a Filter rule or which Path runs when.

What’s left for you is the part no export carries anyway. You connect your app accounts once in FlowRunner, fill in any API keys, point webhooks at the flow’s new address, and test it against a few real runs you saved from Zap history.

How to move from Zapier to FlowRunner has the whole process, with a request to paste for screenshots, one for copied settings, and one for the JSON file if you’re on Team or Enterprise. If you’re still deciding, FlowRunner vs Zapier covers where each platform fits.

If you have a lot of Zaps and want a hand, get in touch.