Skip to main content
An automation is the thing you can run through the API or SDK. It can be implemented by a workflow or by a Git-backed agent, but callers use one run surface: 
POST /api/v1/runs
Use automation targets when you start runs: 
workflows.<slug>
agents.<slug>
The prefix matters because workflow and agent slugs can overlap. You can also use stable ids returned by the API, such as wf_... for workflows.

​
Why the API says automation

The dashboard has workflows and agents because they are authored differently. The public API groups them as automations because they share the same runtime shape:
  • both can be listed with GET /api/v1/automations
  • both can be run with POST /api/v1/runs
  • both produce runs, files, traces, feedback, and evaluator scores
  • both can have datasets and experiments
Use workflow or agent docs when you are authoring behavior. Use automation docs when you are integrating with that behavior from code.