Automation
Anything scheduled, hooked, or sandbox-wrapped. The decision tree for “where does this go” lives in cron-patterns.md - start there.
Recipes in this chapter
Cron Job Patterns
How to schedule automated tasks in OpenClaw, pin the right model and thinking level on each job, decide between agent turns and command payloads, and avoid the pitfalls that waste tokens and break…
Updated 2026-10-17Cron Patterns
The scheduling stack I actually run: systemd timers for OS plumbing, crontab lines that fire reviewed Brigade runbooks, OpenClaw cron for agent tasks, and a small n8n for watchdogs. Pick the wrong…
Updated 2026-10-17Hooks
Hooks enforce policy at boundaries and shape behavior at seams. Pick the wrong layer and you'll scrub private DMs, fight your orchestrator's hook contract, or watch async work disappear into a…
Multi-Channel Setup
How OpenClaw handles multiple messaging platforms simultaneously, session isolation between channels, and practical patterns for Discord, Telegram, and Signal.
Updated 2026-10-17n8n Failure Classifier
One Error Trigger workflow, wired as errorWorkflow on everything active, that turns raw stack traces into buckets and routes each bucket to the action it actually deserves. Without it a…
Updated 2026-06-04n8n Patterns
The interface surfaces, sandbox traps, and failure-routing patterns that actually matter for running n8n as the multi-step workflow layer underneath an agent stack. Pick the wrong API surface and…
Sandbox Shims
Put cheap wrappers in front of risky commands so worker lanes fail closed before they touch the network, git remote, or host secrets.
Updated 2026-05-11Self-Hosted Social Publishing Stack
The publishing plumbing I actually run: Postiz for scheduling and fan-out to the networks, n8n for the multi-step orchestration around it, and an agent driving both over MCP with writes gated off by…
Updated 2026-06-10