Workflows
Build visual, multi-step pipelines when a recurring process needs clear structure rather than one long prompt.
Workflows are the visual side of repeatable work. They are useful when a process has distinct steps that deserve to be seen and reasoned about, such as triggering a task, branching on a condition, sending output to another system, or chaining several actions into a durable pipeline.
When a workflow is better than an automation
Automations are ideal when the task itself is the main unit of work. Workflows are better when the sequence matters. If you need a visual path from trigger to action to output, or if you want a team member to understand the process without reading prompt text, Workflow is the clearer choice.
What the overview is showing you
The KPI strip at the top gives you the size and health of the workflow layer. The cards underneath show which flows are active, which are still drafts, what triggers them, and when they last ran. Recent executions is the practical check. It tells you whether the flow is alive and whether it is finishing cleanly.
How to keep workflows understandable
The strongest workflows stay narrow. They do one operating job well and make the sequence obvious. If a flow starts becoming hard to explain aloud, split it. A compact workflow is easier to trust, easier to debug, and easier for another person to maintain later.