Some work is too involved for a single agent chat and too dynamic for a fixed report. Workflows—now in beta—are visual, deterministic automations: a trigger fires, nodes run in order, and the same trigger produces the same sequence every time.
The building blocks
A trigger kicks things off—a schedule, a webhook, or a connected-app event. Nodes do the work: call an agent, hit an HTTP endpoint, transform data, wait, ask for approval, loop over a list, or branch on a condition. Each run has a status and per-node logs, and every publish snapshots a version you can roll back or compare.
Workflow or agent?
Use a agent when the work is open-ended and you want a person in the loop the whole time. Use a workflow when the steps are known and you need them to run on a schedule, on an external event, or with approval gates. Approvals mean speed and control are not traded off by default.
Workflows is in beta and currently enabled per workspace—your account team turns it on for pilot orgs. We say so plainly. Ask about a pilot.