Skip to main content
POST
Launches one run of a scheduled agent right now. Returns the created session ID. Required scope: sessions:write — the caller must also be an organization admin or owner. This executes the identical code path Cloud Scheduler triggers: same template resolution, same Slack target, same orchestrator call. That is the point — a broken agent fails here, synchronously, with the reason in the response, rather than silently at its scheduled hour.
Disabled agents run too. Validating an agent before turning its schedule on is the main reason to use this endpoint, so enabled is not checked. The response echoes the agent’s enabled state so you know which you triggered.
The run stamps last_run_at and last_session_id exactly like a scheduled tick. It is recorded with a manual trigger for telemetry, but is otherwise indistinguishable from a scheduled run.

Path Parameters

string
required
The scheduled agent ID.

Headers

string
required
Bearer token. Example: Bearer runtm_xxx
string
required
Organization ID.

Response

string
The agent that was run.
string
Session created by this run. Follow it with Get Session or Prompt History.
boolean
The agent’s schedule state. A manual run works either way.
string
Always manual for this endpoint.
string
When the run was triggered.

Errors