J
James Hurst (ddxweb)
## Feature Request: Workflow Export/Import as JSON (Beyond Snapshots)
The Gap:
Snapshots can copy workflows between subaccounts, which is great for full account cloning. But snapshots are all-or-nothing — you cannot export a single workflow as a standalone, editable file. There is no way to:
  • Open a workflow as structured data and programmatically modify it
  • Version control individual workflows in git
  • Diff two versions of a workflow to see what changed
  • Let AI read and edit workflow logic, copy, timing, or conditions
What JSON Export Would Add on Top of Snapshots:
Export any individual workflow as a human-readable JSON file containing triggers, actions, filters, connections, and copy. Not a binary blob or opaque snapshot — actual structured data you can read and manipulate.
Why This Matters Now — The AI Angle:
If a workflow is JSON, AI can work with it directly:
  • "Change the follow-up SMS from 24 hours to 48 hours"
  • "Add a condition: only fire if the contact has a phone number"
  • "Translate all the copy to Spanish"
  • "Build me a 5-step lead nurture sequence from this description"
This is not possible with snapshots. Snapshots move workflows, but JSON makes workflows
programmable
. N8N does this with blueprints — export, import, version control, share, and modify workflows as files. The visual builder is great for designing workflows. JSON export is what makes them scalable.
Summary:
Snapshots solve deployment. JSON export solves iteration, version control, AI editing, and template sharing at the individual workflow level. They complement each other.