Automations

Rule

Automations are the user-facing umbrella for agent-executed tasks that run on demand, in response to events or webhooks, or on a cron schedule. Schedule, Event, Manual, and Webhook are the persisted trigger types. Each automation is a markdown resource under jobs/ with YAML frontmatter describing when and how it fires, and a body containing natural-language instructions the agent follows.

Recurring Jobs is the legacy name and API for scheduled automations. manage-jobs, jobs/, and /agent#jobs remain stable compatibility surfaces. Use manage-automations for new personal or organization automations, including per-automation model overrides and MCP allowlists. Keep manage-jobs for existing schedule-only integrations and delivery metadata.

The Persisted Trigger Types

Type	Fires when	Trigger-specific fields
schedule	Cron expression matches (same as recurring jobs)	schedule (required), timezone
event	A matching event is emitted on the event bus	event (required), condition (optional)
manual	A user explicitly invokes run-now	None
webhook	A POST reaches its generated webhook endpoint	None

Event triggers can optionally include a condition -- a natural-language string evaluated by a model against the event payload before dispatch. If the condition does not match, the automation is skipped. Manual automations have no schedule, timezone, event, or condition; they never fire from the scheduler or event bus and run only through manage-automations action=run-now. Webhook automations run only when their generated endpoint is called. The endpoint path contains a secret token; share it only with the intended webhook provider.