Subject: Feature request: close the JSON round-trip for Zap editing
Hi Zapier team,
Please log this as a feature request for the product team.
You already ship JSON export. What's missing is the round trip — exporting a single Zap, editing that JSON, and pushing it back to the same Zap which causes the Zap to get updated.
I have a dozen large Zaps, several of them 30+ steps with Paths, Python steps, and long AI prompts. I export the JSON, have Claude read the whole workflow and write a corrected version, and it's far faster and more accurate than working through the editor. Then I hit a wall: the only way back in is retyping it by hand, which is where the errors come from. Copilot doesn't close the gap — it's fine for adding a leaf step or mapping a field, but it won't insert a Paths node mid-chain or move steps between branches, which is exactly the work that takes longest.
What would help, in priority order:
1. Per-Zap import that updates an existing Zap, with a diff preview before it commits
2. A documented export schema — the current one is undocumented and has quirks that make it unsafe to edit blind
3. An API for the Zap editor
The commercial case is simple. Right now the ceiling on how complex a Zap someone builds is their patience with the editor, not what's actually possible. AI can already write a complex Zap correctly in one pass; the only thing standing between that and your platform is a file upload. Close it and people build far more, on bigger plans, instead of abandoning the hard ones halfway through.
Happy to share our exports as real-world examples, or to test this in early access.
Thanks.
