Automation
OpenClaw provides several automation mechanisms, each suited to different use cases. This page helps you choose the right one.Quick decision guide
Mechanisms at a glance
| Mechanism | What it does | Runs in | Creates task record |
|---|---|---|---|
| Heartbeat | Periodic main-session turn — batches multiple checks | Main session | No |
| Cron | Scheduled jobs with precise timing | Main or isolated session | Yes (all types) |
| Background Tasks | Tracks detached work (cron, ACP, subagents, CLI) | N/A (ledger) | N/A |
| Hooks | Event-driven scripts triggered by agent lifecycle events | Hook runner | No |
| Standing Orders | Persistent instructions injected into the system prompt | Main session | No |
| Webhooks | Receive inbound HTTP events and route to the agent | Gateway HTTP | No |
Specialized automation
| Mechanism | What it does |
|---|---|
| Gmail PubSub | Real-time Gmail notifications via Google PubSub |
| Polling | Periodic data source checks (RSS, APIs, etc.) |
| Auth Monitoring | Credential health and expiry alerts |
How they work together
The most effective setups combine multiple mechanisms:- Heartbeat handles routine monitoring (inbox, calendar, notifications) in one batched turn every 30 minutes.
- Cron handles precise schedules (daily reports, weekly reviews) and one-shot reminders.
- Hooks react to specific events (tool calls, session resets, compaction) with custom scripts.
- Standing Orders give the agent persistent context (“always check the project board before replying”).
- Background Tasks automatically track all detached work so you can inspect and audit it.
Related
- Cron vs Heartbeat — detailed comparison guide
- Troubleshooting — debugging automation issues
- Configuration Reference — all config keys