OpenClaw PlaybooksAI OpenClaw workflows

This OpenClaw Playbooks page curates community guides from around the web. They are not official docs, but they are real examples you can adapt for your own workflows.

Sources include community-run sites such as openclawai.net (unofficial) and official OpenClaw docs.

OpenClaw Playbooks are community templates, so review each source carefully. OpenClaw Playbooks should be tested locally before production. OpenClaw Playbooks can be adapted to different channels and policy needs.

OpenClaw Playbooks keep workflows repeatable. OpenClaw Playbooks can be cloned per team. OpenClaw Playbooks should be verified in a private channel. OpenClaw Playbooks benefit from clear prompts and source review.

> How to use OpenClaw Playbooks

Each OpenClaw Playbooks card links to a third-party guide. Start with one, follow the setup steps, and keep the gateway running while you validate results.

OpenClaw Playbooks usage checklist

01OpenClaw Playbooks work best when you pilot one channel at a time.
02OpenClaw Playbooks should be tested in a private room before going public.
03OpenClaw Playbooks may require API keys for skills or external tools.
04OpenClaw Playbooks should log errors so you can refine prompts quickly.
05OpenClaw Playbooks can be cloned and customized for new teams.
06OpenClaw Playbooks should use allowlists and mention gating where possible.
07OpenClaw Playbooks benefit from a clear trigger and fallback rule.
08OpenClaw Playbooks should document required env vars and tokens.
09OpenClaw Playbooks should be versioned alongside your prompt changes.
10OpenClaw Playbooks should define a rollback or manual handoff path.

Cron & Heartbeat

Schedule cron tasks and run periodic heartbeat checks.
OpenClaw Playbooksopenclawai.net
01Add a cron schedule that triggers a message.
02Configure heartbeat intervals in the config file.
03Keep the gateway running on an always-on host.
Example commands
moltbot cron add --cron '0 7 * * *' --message 'Morning Brief'\n# heartbeat: { every: '30m' }
01Short intervals consume tokens; 30-60 minutes is suggested.
02Heartbeat stays quiet on OK to avoid spam.
03OpenClaw Playbooks tip: validate this playbook in a private channel first.

Voice & Media

Add voice chat, audio transcription, and media analysis.
OpenClaw Playbooksopenclawai.net
01Add ElevenLabs and OpenAI keys.
02Enable voice settings (voice.talk.enabled=true).
03Install voice-related skills and optional phone plugin.
Example commands
openclaw voicecall call --to ...\n# install skills: sag, openai-whisper-api
01Voice APIs are pay-per-use; monitor balances.
02Local Whisper requires GPU for best results.
03OpenClaw Playbooks tip: validate this playbook in a private channel first.

Lifestyle Services

Automate travel, stocks, restaurants, and recipe lookups.
OpenClaw Playbooksopenclawai.net
01Install skills with the clawdhub CLI.
02Set env vars like SERPAPI_API_KEY and TODOIST_API_TOKEN.
03Register flight data APIs such as OpenSky or AviationStack.
Example commands
npx clawdhub install <skill>\nTrack flight SWR123\nyf NVDA\nSearch italian restaurants in NYC
01Requires extra CLI tools (uv, jq).
02Real-time data depends on third-party API limits.
03OpenClaw Playbooks tip: validate this playbook in a private channel first.

> More OpenClaw Playbooks with commands

These additional OpenClaw Playbooks are based on the community index plus official docs. Use them as starting points and follow the source notes before production use.

WhatsApp Integration

OpenClaw Playbooks: connect WhatsApp via Baileys, scan the QR code, and lock DMs to allowlists.
OpenClaw Playbooksdocs.openclaw.ai
01Add WhatsApp channel config to openclaw.json.
02Set dmPolicy and allowlists for safe DMs.
03Run channel login and scan the QR code.
Example commands
# minimal config { channels: { whatsapp: { dmPolicy: "allowlist", allowFrom: ["+15551234567"] } } } # login (QR) $ openclaw channels login
01WhatsApp runs via WhatsApp Web (Baileys); the Gateway owns the session.
02A separate phone number is recommended for production.
03OpenClaw Playbooks tip: validate this playbook in a private channel first.

Telegram Integration

OpenClaw Playbooks: use the Telegram Bot API via grammY with pairing for DMs and isolated groups.
OpenClaw Playbooksdocs.openclaw.ai
01Create a bot with @BotFather and copy the token.
02Set TELEGRAM_BOT_TOKEN or channels.telegram.botToken.
03Start the gateway and approve pairing on first DM.
Example commands
export TELEGRAM_BOT_TOKEN="123:abc" # or config { channels: { telegram: { enabled: true, botToken: "123:abc", dmPolicy: "pairing" } } }
01Long-polling is the default; webhook is optional.
02OpenClaw Playbooks tip: validate this playbook in a private channel first.

Browser Automation

OpenClaw Playbooks: use the OpenClaw browser profile for scraping, form fills, and social tasks.
OpenClaw Playbooksdocs.openclaw.ai
01Open the OpenClaw browser profile and log in manually.
02Use CLI commands to launch and target the host browser.
Example commands
openclaw browser start openclaw browser open https://x.com
01Manual login is recommended to avoid bot defenses.
02OpenClaw Playbooks tip: validate this playbook in a private channel first.

Smart Home Integration

OpenClaw Playbooks: install home automation skills (HA-MCP, Hue, Tesla) and wire device credentials.
OpenClaw Playbooksopenclawai.netClawHub
01Search ClawHub for a smart-home skill.
02Install the skill into your workspace.
Example commands
clawhub search "homeassistant" clawhub install <skill-slug>
01Follow each skill's README for device tokens and API keys.
02OpenClaw Playbooks tip: validate this playbook in a private channel first.

Google Workspace Integration

OpenClaw Playbooks: automate Gmail, Calendar, and Drive with gogcli and OpenClaw webhooks.
OpenClaw Playbooksgogcli.shdocs.openclaw.ai
01Install gogcli and authorize your Google account.
02Set a default account with GOG_ACCOUNT.
03Enable OpenClaw hooks with the Gmail preset.
Example commands
brew install steipete/tap/gogcli gog auth credentials ~/Downloads/client_secret.json gog auth add you@gmail.com export GOG_ACCOUNT=you@gmail.com gog gmail labels list # OpenClaw hooks preset { hooks: { enabled: true, token: "OPENCLAW_HOOK_TOKEN", path: "/hooks", presets: ["gmail"] } }
01Gmail Pub/Sub uses gog gmail watch serve to push events into OpenClaw.
02OpenClaw Playbooks tip: validate this playbook in a private channel first.

PKM Integration

OpenClaw Playbooks: sync Obsidian, Notion, or Apple Notes via community skills.
OpenClaw Playbooksopenclawai.netClawHub
01Search for PKM-related skills in ClawHub.
02Install the skill that matches your PKM stack.
Example commands
clawhub search "obsidian" clawhub search "notion" clawhub install <skill-slug>
01Most PKM skills require API tokens; follow the skill's setup docs.
02OpenClaw Playbooks tip: validate this playbook in a private channel first.

Social Media Automation

OpenClaw Playbooks: use the OpenClaw browser for X/Twitter posting and cross-platform workflows.
01Open the OpenClaw browser profile and log in manually.
02Use host browser targeting when sandboxed.
Example commands
openclaw browser start openclaw browser open https://x.com --browser-profile openclaw --target host
01Host browser control reduces bot detection risks for social sites.
02OpenClaw Playbooks tip: validate this playbook in a private channel first.

Dev Workflow Automation

OpenClaw Playbooks: trigger OpenClaw from GitHub, Sentry, or CI/CD using webhooks.
01Enable hooks with a shared token.
02POST to /hooks/agent with your payload.
Example commands
curl -X POST http://127.0.0.1:18789/hooks/agent \ -H "Authorization: Bearer OPENCLAW_HOOK_TOKEN" \ -H "Content-Type: application/json" \ -d '{"message":"Summarize the latest CI failure","name":"CI","deliver":true}'
01Use the hooks token header or x-openclaw-token for auth.
02OpenClaw Playbooks tip: validate this playbook in a private channel first.

Slack / Discord

OpenClaw Playbooks: run OpenClaw inside collaboration platforms with Socket Mode and bot tokens.
01Create a Slack app and enable Socket Mode.
02Create a Discord bot and enable Message Content Intent.
03Configure tokens in openclaw.json.
Example commands
# Slack { channels: { slack: { enabled: true, appToken: "xapp-...", botToken: "xoxb-..." } } } # Discord { channels: { discord: { enabled: true, token: "YOUR_BOT_TOKEN" } } }
01Slack uses Socket Mode by default; Discord uses the Bot API + Gateway.
02OpenClaw Playbooks tip: validate this playbook in a private channel first.

Security & Sandbox

OpenClaw Playbooks: audit your setup and isolate tool execution with Docker sandboxing.
01Inspect sandbox status and containers.
02Run a security audit to catch risky settings.
Example commands
openclaw sandbox explain openclaw sandbox list openclaw security audit --deep
01Sandboxing is optional but recommended for non-main sessions.
02OpenClaw Playbooks tip: validate this playbook in a private channel first.

Custom Skills

OpenClaw Playbooks: install and manage skills from ClawHub to extend OpenClaw.
OpenClaw Playbooksdocs.openclaw.aiClawHub
01Search for a skill that matches your workflow.
02Install and update skills in your workspace.
Example commands
clawhub search "calendar" clawhub install <skill-slug>
01Skills are SKILL.md folders loaded from your workspace or ~/.openclaw/skills.
02OpenClaw Playbooks tip: validate this playbook in a private channel first.

Filesystem & Shell

OpenClaw Playbooks: use core tools like exec and apply_patch for file and shell workflows.
01Enable apply_patch in config if needed.
02Use exec for shell tasks.
Example commands
# exec tool example {"tool":"exec","command":"ls -la"} # enable apply_patch { "tools": { "exec": { "applyPatch": { "enabled": true } } } } # apply_patch example *** Begin Patch *** Update File: src/index.ts @@ -const foo = 1 +const foo = 2 *** End Patch
01apply_patch is disabled by default and must be enabled in config.
02OpenClaw Playbooks tip: validate this playbook in a private channel first.

> Why choose OpenClaw Playbooks

OpenClaw Playbooks are useful because they show real-world setups from the community. You can copy the command patterns, then adjust for your own channel and policy needs.

Community-tested recipes

Each card links to a community playbook that includes setup and commands.

Adaptable workflows

Use the examples as templates and adjust credentials, skills, or endpoints.

> OpenClaw Playbooks FAQ

Common questions when starting your first community playbook.

How many playbooks should I launch?

Start with one OpenClaw Playbooks workflow, validate it, then expand.

Are these official OpenClaw Playbooks?

No. These are community guides pulled from public sources, so validate them in your own environment.

Why do some commands use moltbot or clawdhub?

Community guides sometimes use older CLI names or companion tools. Follow the source page if needed.

Where do the examples come from?

Each card links directly to the community source so you can review the full playbook.