Customers building automations want to export an automation's full definition as a human-readable text file (YAML or JSON) instead of relying only on the visual builder. For intricate workflows, scanning a text file is far faster and more reliable for verifying logic than clicking through each node, and it lets users drop the definition into AI tools to review or help edit it. The automation definition already exists as structured data behind the scenes, so the gap is purely a usable export experience. At minimum this would be read-only export for review; a natural extension is round-trip support, where a user exports the file, edits it, and re-imports it to update the automation.