OpenClaw Automation Workflows: 10 Recipes That Run Themselves
Claude just launched web-based scheduled tasks. The whole developer community noticed. Here's why running your AI automations locally with OpenClaw is still smarter — and 10 battle-tested workflows you can copy right now.
The Automation Moment (March 2026)
This week, Anthropic quietly pushed something that lit up Hacker News: Claude.com now supports web-based scheduled tasks. You can point Claude at a URL, give it a schedule, and it'll run the task from Anthropic's servers.
The reaction from developers was immediate — and telling. Not amazement. More like: "Wait, OpenClaw has had this for months."
That's the moment we're in. Every major AI lab is racing to build autonomous, scheduled, action-taking agents. The difference is where those agents run, what data they touch, and who pays the bill when they run 10,000 times a month.
🦾 The core insight
An AI that waits to be asked is a tool. An AI that acts on its own schedule is an agent. The future is agents. And agents that run locally, on your hardware, on your schedule — that's the edge OpenClaw was built for.
Local vs Cloud Automation
Claude's cloud-scheduled tasks are genuinely useful — but they come with tradeoffs that matter once you're running serious automations:
| Feature | Claude.com Scheduled | OpenClaw (Local) |
|---|---|---|
| Access local files | ❌ No | ✅ Full |
| Send Telegram/iMessage | ❌ No | ✅ Yes |
| Control your desktop | ❌ No | ✅ Browser control |
| Custom skills/plugins | ❌ No | ✅ Unlimited |
| Data stays private | ⚠️ Anthropic servers | ✅ Your machine |
| Cost at 1,000 runs/mo | 💸 Usage-based | ✅ Fixed (your LLM key) |
| Sub-agents + chaining | ❌ No | ✅ Yes |
| Memory across runs | ⚠️ Limited | ✅ Persistent MEMORY.md |
The cloud solution is a great starting point. Local OpenClaw is where you go when it gets serious.
The OpenClaw Building Blocks
Before diving into recipes, here are the primitives every workflow is built from:
Cron Jobs
Schedule recurring tasks — minutely, hourly, daily, or on a cron expression. The backbone of all automation.
System Events
Inject a message into your main session at any time — like a wake-up call for the agent to do something specific.
Sub-agents
Spawn isolated task agents that run in parallel, complete a job, and report back — without blocking your main session.
Skills
Pre-built capability packs — email, calendar, GitHub, weather, browser control, iMessage, and more. Drop them in.
Memory
MEMORY.md persists state across runs. Your agent remembers what it did yesterday and adjusts today.
Delivery
Results land where you want — Telegram, Discord, webhooks, or stored to a file. Set it and walk away.
Anatomy of a Workflow
Every OpenClaw workflow is a JSON job definition. It has four parts:
{
"name": "Daily crypto brief",
"schedule": {
"kind": "cron",
"expr": "0 7 * * 1-5", // Weekdays at 7am
"tz": "Europe/Belgrade"
},
"payload": {
"kind": "agentTurn",
"message": "Fetch BTC + ETH prices, check my portfolio allocation, write a 3-bullet morning brief, and send it to Telegram.",
"timeoutSeconds": 120
},
"delivery": {
"mode": "announce"
},
"sessionTarget": "isolated"
}scheduleWhen to run — at, every, or cron expression
payloadWhat to do — a natural language task prompt
deliveryWhere to send results — announce, webhook, or none
10 Real Automation Recipes
Copy any of these. They run on your machine, 24/7, without you.
1. Morning Intelligence Brief
⏰ Daily 7amNews + crypto prices + weather + calendar summary — delivered to Telegram before you're out of bed.
{
"name": "Morning brief",
"schedule": { "kind": "cron", "expr": "0 7 * * *", "tz": "Europe/Belgrade" },
"payload": {
"kind": "agentTurn",
"message": "Good morning brief: (1) top 3 AI/crypto headlines from HN, (2) BTC ETH prices + 24h change, (3) today's weather in Belgrade, (4) my Google Calendar events for today. Format as a clean Telegram message with emojis.",
"timeoutSeconds": 90
},
"delivery": { "mode": "announce" },
"sessionTarget": "isolated"
}2. GitHub PR Watchdog
⏰ Every 2 hoursChecks your repos for new PRs, open review requests, and failing CI runs. Pings you only when action is needed.
{
"name": "GitHub PR watchdog",
"schedule": { "kind": "every", "everyMs": 7200000 },
"payload": {
"kind": "agentTurn",
"message": "Check GitHub for: (1) any PRs waiting for my review, (2) PRs where CI just failed, (3) PRs with new comments since last check. Only report if something needs my attention. Be brief.",
"timeoutSeconds": 60
},
"delivery": { "mode": "announce" },
"sessionTarget": "isolated"
}3. Weekly Content Digest
📅 Monday 8amCurates the week's best AI content across HN, Reddit, and key blogs into a single Telegram summary.
{
"name": "Weekly content digest",
"schedule": { "kind": "cron", "expr": "0 8 * * 1", "tz": "Europe/Belgrade" },
"payload": {
"kind": "agentTurn",
"message": "Weekly AI digest: fetch the top 5 posts from r/LocalLLaMA + r/MachineLearning this week, top 3 from HN tagged AI, and 2 articles from therundown.ai. Summarize in 1 sentence each. Group by topic. Send to Telegram.",
"timeoutSeconds": 120
},
"delivery": { "mode": "announce" },
"sessionTarget": "isolated"
}4. Server Health Check
⏰ Every 30 minMonitors uptime, disk space, and memory on your VPS or Mac mini. Alerts only when thresholds are crossed.
{
"name": "Server health",
"schedule": { "kind": "every", "everyMs": 1800000 },
"payload": {
"kind": "agentTurn",
"message": "Run a quick health check: disk usage (warn if >80%), memory usage (warn if >90%), check that my key processes are running (nginx, openclaw). Only notify me if something is wrong.",
"timeoutSeconds": 45
},
"delivery": { "mode": "announce", "bestEffort": true },
"sessionTarget": "isolated"
}5. Daily Journal Prompt
🌙 9pm DailySends a thoughtful, contextual journaling prompt every evening — customized based on what you were working on that day.
{
"name": "Evening journal prompt",
"schedule": { "kind": "cron", "expr": "0 21 * * *", "tz": "Europe/Belgrade" },
"payload": {
"kind": "agentTurn",
"message": "Evening wind-down. Check my calendar and recent messages to understand what I worked on today. Then craft one thoughtful journaling question — specific to my day, not generic. Send it as a Telegram message.",
"timeoutSeconds": 60
},
"delivery": { "mode": "announce" },
"sessionTarget": "isolated"
}6. Email Triage + Summary
⏰ Every 4 hoursReads your inbox, flags emails that need a reply today, and summarizes the rest. Zero inbox anxiety.
{
"name": "Email triage",
"schedule": { "kind": "every", "everyMs": 14400000 },
"payload": {
"kind": "agentTurn",
"message": "Check my email inbox (last 4 hours). Flag anything that needs a reply today as URGENT. Summarize the rest in 1 line each. Send me the triage list via Telegram. Ignore newsletters and automated emails.",
"timeoutSeconds": 90
},
"delivery": { "mode": "announce" },
"sessionTarget": "isolated"
}7. Crypto Portfolio Snapshot
📅 Weekdays 9amTracks your key holdings, calculates allocation drift, and flags any major moves overnight.
{
"name": "Portfolio snapshot",
"schedule": { "kind": "cron", "expr": "0 9 * * 1-5", "tz": "Europe/Belgrade" },
"payload": {
"kind": "agentTurn",
"message": "Morning portfolio check: fetch current prices for BTC, ETH, SOL. Calculate 24h change. Note if anything moved more than 5%. Write a 3-line summary. Send to Telegram. No financial advice.",
"timeoutSeconds": 60
},
"delivery": { "mode": "announce" },
"sessionTarget": "isolated"
}8. Weekly Memory Consolidation
📅 Sunday 11pmReviews the week's conversations, extracts key decisions and project updates, and writes them to MEMORY.md. Your agent gets smarter every week.
{
"name": "Weekly memory update",
"schedule": { "kind": "cron", "expr": "0 23 * * 0", "tz": "Europe/Belgrade" },
"payload": {
"kind": "agentTurn",
"message": "Weekly memory consolidation: review this week's conversations. Extract: new projects started, decisions made, APIs configured, milestones hit. Update MEMORY.md with anything new and significant. Be concise.",
"timeoutSeconds": 180
},
"delivery": { "mode": "announce" },
"sessionTarget": "isolated"
}9. Competitor Intelligence Monitor
📅 Tuesdays 8amTracks product updates, pricing changes, and announcements from your key competitors. Know before your customers do.
{
"name": "Competitor intel",
"schedule": { "kind": "cron", "expr": "0 8 * * 2", "tz": "Europe/Belgrade" },
"payload": {
"kind": "agentTurn",
"message": "Weekly competitor check: search for news about [your competitors] in the last 7 days. Look for: product launches, pricing changes, funding news, outages, acquisitions. Summarize the most important 3-5 items. Send to Telegram.",
"timeoutSeconds": 120
},
"delivery": { "mode": "announce" },
"sessionTarget": "isolated"
}10. Auto-Publish Blog Article
📅 Fridays 8amResearches trending topics, writes an SEO article, generates a banner image, and deploys to production. Full pipeline, zero manual work. (This is actually how this article was written.)
{
"name": "Weekly blog article",
"schedule": { "kind": "cron", "expr": "0 8 * * 5", "tz": "Europe/Belgrade" },
"payload": {
"kind": "agentTurn",
"message": "Research trending AI topics from HN + Reddit. Pick the best angle for claw.mobile's audience. Write a 1400-word SEO article, generate a banner image, deploy to Vercel. Report title + live URL.",
"timeoutSeconds": 600
},
"delivery": { "mode": "announce" },
"sessionTarget": "isolated"
}What the Community Is Saying
"Claude adding scheduled tasks is validation that this is the right direction — but the implementation is still sandboxed. No file access, no custom tools. Until they solve that, OpenClaw runs laps around it for real workflows."
— Hacker News thread on Claude Web Scheduled Tasks (50+ comments, trending #1)
"The thing people miss: it's not about having an AI that can do things. It's about having one that does things without being asked. The cron-based agent pattern is underrated."
— Developer discussion on autonomous agent patterns, X/Twitter, 200+ likes
"Running GPT-4o on a $6 VPS 24/7, doing my morning brief, watching my PRs, and summarizing my email. Total cost last month: $1.20 in API calls. I cancelled my $20 ChatGPT Plus subscription."
— r/LocalLLaMA community, paraphrased from multiple similar posts
Chaining Workflows Together
The recipes above are standalone. But the real power comes from chaining: a morning brief that checks your calendar and then auto-schedules focus blocks. A PR watchdog that then drafts a reply comment. A competitor monitor that then adds items to your research queue.
OpenClaw supports this through sub-agents. A parent cron job spawns child agents for parallel research, collects results, and synthesizes them into a single output. It's the difference between a to-do list and an org chart.
// Example: Spawn 3 parallel sub-agents from one cron job "message": "You are orchestrating a morning intelligence operation. Spawn 3 sub-agents in parallel: 1. Fetch top 5 AI headlines from HN + therundown.ai 2. Get BTC/ETH/SOL prices and calculate 24h delta 3. Summarize today's Google Calendar events Wait for all 3. Combine results into a single briefing. Format for Telegram. Send when complete."
Learn more about sub-agent orchestration in the OpenClaw Sub-Agents guide →
Ready to Build Your First Workflow?
Start with Recipe #1 — the morning brief. It takes 5 minutes to set up and will change how you start every day. Then add one workflow per week. Within a month, your AI handles most of the repetitive work in your life.
# Get OpenClaw brew install openclaw # Start the gateway openclaw gateway start # Open Telegram, message your bot: # "Create a morning brief cron at 7am Belgrade time"
Stay in the Loop
Get weekly OpenClaw tips, new skills, and automation ideas. No spam, unsubscribe anytime.
Join 2,000+ builders · No spam · Unsubscribe anytime