Workflows
Build automations that combine triggers, agents, and tools — visually, with versioning and approvals.
Workflows is in Beta. The UI and API may change. The sidebar entry is currently disabled for most workspaces — your account team enables it for pilot orgs.
Workflows are visual automations: a trigger fires, nodes run in order, data flows between them, and you can pause for approvals, branch on conditions, or loop over lists. Built for the work that's too involved for a single agent chat and too dynamic for a fixed report.
When to use a workflow vs. an agent
Agent chats are conversational, single-thread, and the agent picks tools turn-by-turn. Workflows are deterministic: the same trigger fires the same sequence of nodes every 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. Use an agent when the work is open-ended or you want a person in the loop the whole time.
Building blocks
- Trigger — what kicks the workflow off. Schedule, webhook, or Composio event.
- Nodes — units of work. Call an agent, hit an HTTP endpoint, transform data, wait, ask for approval, loop, or branch.
- Run — one execution of the workflow. Has a status, logs per node, and a permanent history.
- Version — every publish snapshots the workflow. Roll back or compare at any time.
Where to find it
/workflows opens the list. + New workflow lands on the template picker at /workflows/new. Picking a template — or starting blank — opens the editor at /workflows/{workflowId}.
What's next?
Building workflows
Create, edit, and publish workflows from the visual editor.
Triggers
Schedule, webhook, and Composio event triggers — and how to configure them.
Nodes
Every node type: agent calls, HTTP requests, transforms, approvals, loops, and branches.
Runs
Monitor executions, inspect per-node logs, and review run history.