Introduction to workflows

What a workflow is

A workflow represents a process as connected steps. It can choose what happens next, run an authorized tool, request approval, delegate a task, or produce a response.

Workflows belong to the workspace and can be assigned to one or more agents, allowing a process to be reused without duplicating its design.

When to use a workflow

Use a workflow when a process requires an explicit, observable sequence, such as routing a request, reading or updating external data, waiting for human approval, running independent branches, delegating a step, or reusing another published workflow.

Use agent instructions for general response behavior. Use an agent team when the main requirement is combining several specialists into one answer.

Available nodes

The designer provides Start, Condition, Tool, Response, Wait, Human approval, Parallel branches, Agent, Subworkflow, and End nodes.

Every workflow needs exactly one start and at least one end. Connections define the path and conditions select the next branch.

Activation modes

A workflow can run automatically from a configured intent, manually, from another workflow, or from an hourly, daily, or weekly schedule.

Priority and minimum confidence help select the correct process when an agent has several assigned workflows.

Drafts and publishing

Changes are saved as a draft. Before publishing, Studio validates the structure, connections, and selected resources. Published versions remain identifiable so executions can be traced consistently.

Saving is not publishing. Test and validate the draft before making a version available to conversations or schedules.

Observability

Studio records each execution and step, including status, origin, agent, channel, duration, usage, and errors. Aggregate metrics show volume, success rate, and response times.

This information helps distinguish a design issue from a failed external tool or a pending approval.