Automation
Run Compozy agents on schedules, in response to runtime events, or from signed external HTTP requests.
- Audience
- Operators running durable agent work
- Focus
- Automation guidance shaped for scanability, day-two clarity, and operator context.
Automation is the unattended-run surface around three primitives: schedules that fire on a clock, triggers that react to runtime events, and webhooks that accept signed HTTP from outside the daemon. All three resolve to the same dispatcher and produce the same audit trail as interactive sessions. Consent-first suggestions help operators create scheduled Jobs without authoring the initial prompt and cron expression from scratch.
In this section
Automation suggestions
Review workspace-scoped Job proposals, create the useful ones, and durably dismiss the rest.
Jobs and scheduling
Use this page when you need cron, interval, or one-time scheduled agent runs with retry policy and run history.
Event triggers
Use this page when the next run should react to runtime events such as session stops or memory consolidation.
Webhook activation
Use this page to accept signed HTTP requests from external systems and route them as automation triggers.
Tool and CLI parity
Automation lifecycle is agent-manageable. The compozy__automation toolset and HTTP/UDS APIs expose
the complete Agent-or-Loop request union. The compozy automation CLI reaches the same validators and
writers for its supported flags; create and update flags currently author Agent targets, while
read and lifecycle verbs also operate on Loop-target definitions:
| Surface | Read tools | Mutation tools | CLI coverage |
|---|---|---|---|
| Suggestions | compozy__automation_suggestions_list | compozy__automation_suggestions_accept, compozy__automation_suggestions_dismiss | List, create the proposed Job, or dismiss |
| Jobs | compozy__automation_jobs_list, compozy__automation_jobs_get, compozy__automation_jobs_history | compozy__automation_jobs_create, compozy__automation_jobs_update, compozy__automation_jobs_delete, compozy__automation_jobs_trigger, compozy__automation_jobs_enable, compozy__automation_jobs_disable | Agent-target authoring; all reads and lifecycle |
| Triggers | compozy__automation_triggers_list, compozy__automation_triggers_get, compozy__automation_triggers_history | compozy__automation_triggers_create, compozy__automation_triggers_update, compozy__automation_triggers_delete, compozy__automation_triggers_enable, compozy__automation_triggers_disable | Agent-target authoring; all reads and lifecycle |
| Runs | compozy__automation_runs_list, compozy__automation_runs_get | — | compozy automation runs ... |
Mutations require approval, run through the same domain validators as CLI/HTTP, and reject raw
webhook secrets with deterministic codes including AUTOMATION_SCOPE_FORBIDDEN,
AUTOMATION_SECRET_INPUT_FORBIDDEN, AUTOMATION_VALIDATION_FAILED, and
AUTOMATION_APPROVAL_REQUIRED. Webhook secret material stays write-only on mutation surfaces and is
referenced through webhook_secret_ref.