Trigger, action, output
Any automation can be described in one line: when this happens, do that, produce this. Writing that sentence first forces you to decide what actually starts the flow and what counts as success — the two questions that cause most rebuilds later.
The builder returns that one-line spec plus the categories of tools that can run it, so you can evaluate platforms against requirements instead of features.
Plan before you build
Rebuilding a half-finished flow in a different platform is the most common waste of time in small-business automation. A written spec survives a platform migration; a half-built zap does not.
Keep the spec in your documentation. When the flow breaks in six months, the one-liner tells you immediately what it was supposed to do.
触发、动作、产出
任何自动化都能用一句话描述：当这件事发生，就做那件事，产出这个东西。先写下这句话，会逼你确定究竟是什么启动了流程、什么算成功——这两问题正是日后反复重建的主要原因。
生成器返回这一行式规格，以及能执行它的工具类别，让你按需求而不是按功能列表去评估平台。
先规划，再搭建
在小企业自动化里，最浪费时间的行为是：半成品流程在一个平台搭到一半，又换到另一个平台重建。写下来的规格能经受平台迁移，半成品不能。
把规格留在你的文档里。半年后流程坏了，这一行字会立刻告诉你它本来该做什么。