Usage
GET /jobs jobs defined for the productGET /runs run historyGET /agents connected agents and their stateGET /workflow/queue queued workGET /workflow/queue/:id one queued itemRuns carry their outcome and their logs, so “why did last night’s job fail” is a query rather than an archaeology exercise across agent hosts.
Triggers
Section titled “Triggers”A job runs when something fires it.
Scheduled
Section titled “Scheduled”A cron expression. The common case, and the one to reach for when the work is genuinely periodic rather than reactive.
Webhook
Section titled “Webhook”An inbound HTTP call fires the job, with the request body as input. Use this for third-party callbacks — payment confirmations, delivery notifications — where the other side pushes.
Database
Section titled “Database”A change in a watched table fires the job. This removes the polling loop most teams write by hand: a job that should run “when a row lands” does not need a one-minute cron and a watermark column, with the lag and the missed-row edge cases that come with them.
Git poll
Section titled “Git poll”A new commit on a watched repository fires the job. The basis for content or configuration pipelines that follow a repo.
A message in a connected workspace fires the job — the “run this from chat” pattern, without building a bot.
Runs and retries
Section titled “Runs and retries”Every firing produces a run with a status, timing, output and logs. A failed run can be retried by id.
Retry re-dispatches the same job with the same input rather than re-deriving it. That matters when the trigger was a one-off webhook you cannot replay — re-deriving would mean the input is simply gone.
Agents
Section titled “Agents”Jobs execute on agents: long-lived worker processes that connect and receive work. The orchestrator distributes runs across whatever is connected, so scaling throughput is running more agents rather than reconfiguring anything.
An agent that disconnects mid-run leaves the run recoverable rather than lost; the queue holds work until an agent can take it.
- Operations — capacity, failure modes and what to watch