Jobs

The Jobs block runs background work on a fleet of agents. A job is defined once and fired by a trigger; the block handles dispatch, retry, run history and the queue in between.

Triggers

A job runs when something fires it. Five trigger kinds:

Trigger	Fires on
Scheduled	A cron expression
Webhook	An inbound HTTP call
Database	A change in a watched table
Git poll	A new commit on a watched repository
Chat	A message in a connected workspace

Database and git-poll triggers are the ones worth knowing about, because they remove 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.

Agents

Jobs execute on agents — long-lived worker processes that connect to the service and receive work. The orchestrator distributes runs across whatever is connected, so scaling throughput is running more agents rather than reconfiguring anything.

GET /agents        connected agents and their state

An agent that disconnects mid-run leaves the run recoverable rather than lost; the queue holds work until an agent can take it.

Next

• Usage — the API and how to drive it
• Operations — configuration, running it, and what to watch