Workflows
Compose agents into multi-step workflows — plan from a goal, run, monitor each step, and share.
A workflow is a multi-step pipeline of agents. Each step (node) dispatches to one agent in your workspace; the output of one step can feed the input of the next, so a single run can chain research, drafting, triage, or any sequence of agent tasks into one execution.
Workflows live in a workspace, next to the agents they orchestrate. You can build one by hand on the pipeline canvas, or describe a goal in plain language and let the platform plan the steps and wiring for you. Once saved, a workflow runs on demand from the console or on a recurring schedule, and every run is recorded as an execution with per-step status, outputs, and runtime events.
Key concepts
- Pipeline — the ordered set of nodes a workflow executes. Each node names the agent it calls and the message it sends.
- Input placeholders — a node's message can reference run-time values:
$userinput.<key>resolves from the inputs you provide when starting a run, and$<nodeId>.<key>resolves from an earlier step's output. - Execution — one run of a workflow. Executions record inputs, per-step status and output, errors, and the runtime events emitted by each agent.
- Schedule — an optional recurrence (hourly, daily, weekly, monthly). A scheduled workflow runs automatically; an unscheduled one runs manually.
In this section
Planning a workflow
Describe a goal, let the planner propose the pipeline, then edit and save it.
Running and monitoring
Start runs with inputs, follow per-step progress, and diagnose failures.
Agents in workflows
Which agents can participate, what happens when one is removed, and scheduled runs.
Sharing
Share a workflow with teammates by email and manage who has access.