Automations

Automations are OpenClaw’s built-in scheduler. The scheduler persists jobs, wakes the agent at the right time, and can deliver output to a chat channel, a webhook, or nowhere.

Manage automations with the openclaw automations CLI; openclaw cron remains an alias for the same commands.

Note: the official docs split this topic into child pages; this page is the navigation entry. Topics without a local English page link to the official source. Checked against the official repository fixed commit (2026-11-06 checkout).

Quick start

  1. Add a one-shot reminder:
openclaw automations create "2027-02-01T16:00:00Z" \
  --name "Reminder" \
  --session main \
  --system-event "Reminder: check the automations docs draft" \
  --wake now \
  --delete-after-run
  1. Check your jobs:
openclaw automations list
openclaw automations get <job-id>
openclaw automations show <job-id>
  1. See run history:
openclaw automations runs <job-id>

Topic map

Runtime model and promotion

How automations work — Runtime model, run lifecycle, and job promotion: isolated-run hardening, run reconciliation, promoting a repeated job into an automation.

Schedules and triggers

Automation schedules (official) — Schedule kinds, cron rules, pacing, and condition watchers: schedule types, heartbeat task migration, monitoring policies, stream sources, dynamic cadence (pacing), the /loop chat shortcut, day-of-month/day-of-week OR logic, and event triggers (condition watchers).

For the cron-vs-heartbeat decision, see Cron vs Heartbeat (historical comparison: heartbeat has been folded into ordinary automation jobs, so the either/or framing no longer applies).

Payloads and execution

Automation payloads — Payload kinds, agent-turn flags, and session execution styles: --message/--model/--fallbacks/--thinking/--light-context/--tools, command and script payloads, execution styles (main vs current vs isolated vs custom), what “fresh session” means for isolated jobs, the unattended run contract, and subagent/Discord delivery.

Delivery

Automation delivery (official) — Delivery modes, failure notifications, and output language.

Management and configuration

Manage automations (official) — CLI examples, management commands, run history, and config keys: one-shot reminders, recurring isolated jobs, model and thinking overrides, webhook output, command output, conversational management, retry behavior, maintenance, and legacy store migration.

Inbound webhooks

Webhooks — webhook entries for wakeups and isolated agent runs. The full Gateway HTTP hooks (POST /hooks/wake, POST /hooks/agent, mapped hooks, auth, and troubleshooting) are on the official webhooks page.

Gmail triggers

Gmail PubSub — Gmail inbox triggers via Google Pub/Sub; the recommended restricted Gmail reader setup and verification boundary are on the official Gmail page.

Troubleshooting

Automation troubleshooting — scheduling/delivery checklist. The official command ladder, “automations not firing”, “job fired but no delivery”, and timezone gotchas are on the official troubleshooting page.

Where the old single-page sections went

This page was previously a single long page. Its heading anchors are preserved where the content still lives here; the rest map to the child pages above:

  • “Cron jobs (Gateway scheduler)” / “TL;DR” / “Beginner-friendly overview” — covered by the intro above.
  • “Quick start (actionable)” — Quick start above.
  • “Concepts” / “Jobs” / “Schedules” — official how-it-works and schedules pages.
  • “Main vs isolated execution” / “Main session jobs (system events)” / “Isolated jobs (dedicated cron sessions)” / “Payload shapes (what runs)” / “Model and thinking overrides” — local payloads page (execution styles, agent-turn flags).
  • “Announce delivery flow” / “Webhook delivery flow” / “Delivery (channel + target)” / “Telegram delivery targets (topics / forum threads)” — official delivery page.
  • “Tool-call equivalents (Gateway cron tool)” / “JSON schema for tool calls” / “cron.add params” / “cron.update params” / “cron.run and cron.remove params” — official payloads and managing-jobs pages (the modern CLI is openclaw automations).
  • “Where cron jobs are stored” / “Storage & history” / “Configuration” / “CLI quickstart” / “Gateway API surface” — official managing-jobs page.
  • “Troubleshooting” / ““Nothing runs”” / “Telegram delivered to the wrong place” — local troubleshooting page and the official troubleshooting page above.

Related pages