Schedules
A schedule wakes an agent on a timer and opens work in a chosen session. It is one of three automation engines — the time → agent cell.
What a schedule does
From the Schedules window you attach a cadence to an agent and a destination conversation. When the clock fires, the server re-checks that the creator still has the right workspace role and still has access to private destinations, then opens the run.
Schedules are server-owned definitions. Clients read them; the dedicated routes validate writes. They appear in realtime once subscribed, scoped like other session-bound work.
How this differs from the other engines
| System | Trigger | Action |
|---|---|---|
| Schedules | Time | Wake an agent |
| Orbs (webhooks) | Inbound HTTP | Wake an agent |
| Automations | Workspace event | Deterministic internal action (message or task) |
None of these replace the others. Pick the trigger that matches the work.