Workflows

Build repeatable agent workflows without widening access.

Design a workflow directly when the process is clear, then start it from a manual request, schedule, or event. Mix agent steps, deterministic JavaScript, waits, branches, human input, and exact-call approvals while keeping each tool's access rules.

Create a workflow Read workflow docs

Workflow model

A workflow is a saved graph, not just a trigger.

Each run follows explicit steps and branches. A step can execute deterministic JavaScript, start or poll an agent, return a durable wait, or pause for a person. Triggers decide when the graph starts; grants and approvals still decide what its tool calls may do.

Start

Captured trigger input

Manual, schedule, or matching event.

Deterministic step

Run limited JavaScript

Transform, call a granted tool, or select a declared branch.

Open-ended step

Start and poll an agent

Persist the agent run id and resume from its result.

Continue

Route to the next step

Pass saved output into a declared branch.

Pause

Wait for time, a person, or approval

Persist the pause, then resume the graph with evidence.

Saved definition

Inspect the workflow before it runs.

The workflow view keeps the graph, exact starting signal, and each capability's resource scope and approval requirement together before you start a run.

Incident response workflow showing three connected steps, its incident.created trigger, and three repository-scoped tools, including one that requires approval — The saved view shows the workflow itself, its exact trigger, and the tools its steps may use.