Workflows are reusable automations that agents can run on demand or from a trigger. Autopilots apply that workflow model to work that should keep operating from its configured trigger.
Workflows
Use a workflow when a process has a known sequence. A workflow can:
- receive validated input;
- run agent and tool steps;
- pass data from one step to the next;
- branch on a condition;
- pause for approval;
- record each run and step outcome.
Start by running a workflow manually. Add a schedule or event trigger only after the inputs, outputs, and review points are correct.
Autopilots
Use an autopilot for recurring or event-driven work that should remain active after setup. Treat it as an operating automation, not a one-off shortcut: review its trigger, connected tools, and recent runs regularly.
How both execute
A manual start and an Autopilot trigger enter the same workflow definition. The same approval and run-history model applies either way.
flowchart LR
Manual["Manual start"] --> Definition["Workflow definition"]
Trigger["Autopilot trigger"] --> Definition
Definition --> Steps["Agent and tool steps"]
Steps --> Review{"Approval required?"}
Review -- "Yes" --> Approval["Human review"]
Approval --> History["Run history"]
Review -- "No" --> History
Which should you choose?
Both use the same run history, so you can inspect what happened and respond to a pending approval from the run detail.
Move from manual to ongoing
Prove the process manually
Run the workflow with representative inputs and verify each output.
Confirm review boundaries
Check the connected tools, approval steps, and failure path before adding a trigger.
Configure the trigger
Use an Autopilot when the process and its trigger are stable enough to keep operating.
Review recent runs
Inspect outcomes and waiting approvals regularly, especially after changing the definition or a connection.