Morning Briefing Automation with OpenClaw

Overview

Morning briefing automation with OpenClaw means receiving a single, curated message each morning (or at any time you set) that summarizes what you need to know: today's calendar, local weather, a short email or news digest, and your top tasks or priorities. Instead of opening four different apps before your first coffee, you get one message in the messaging app you already use-Telegram, WhatsApp, or Slack. The agent uses skills from ClawHub to read your calendar, optionally your inbox, weather APIs, and news or RSS; then a scheduled task (cron job or OpenClaw's built-in scheduler) triggers the agent at the same time every day. The agent composes a concise briefing and sends it to your channel. Your data stays on your machine or VPS-no third-party cloud assistant.

What you'll learn:

• Why use OpenClaw for morning briefings (one message, 24/7 agent, self-hosted)
• Prerequisites: OpenClaw, a channel, and skills for calendar (and optionally email, weather, news)
• Step-by-step setup: scheduled task, prompt design, and which skills to install
• Example prompt and configuration for a typical "today's calendar + weather + top 3 emails" briefing
• Best practices: timezone, length, and combining with email and calendar use cases
• Common pitfalls: briefing not firing, missing data, and how to troubleshoot

Why OpenClaw for Morning Briefings?

• One message, not five apps: You're already in Telegram or WhatsApp. One tap shows your full briefing-calendar, weather, email summary, tasks. No switching to Gmail, calendar app, and weather. Combines well with other personal productivity flows like email management and calendar assistant.
• 24/7 agent on your server: OpenClaw runs on your Mac, Linux box, or VPS. A scheduled task (e.g. 7:00 AM) triggers the agent; it fetches calendar, weather, and optional email/news, then sends the formatted briefing to your channel. No need for a cloud service to "wake up" and run-your instance is always on.
• Fully customizable: You choose what's in the briefing (calendar only, or calendar + weather + top 3 emails, or add news/RSS). You set the time and the channel. Use agent customization and system prompts to control tone and length (e.g. "Keep the briefing under 300 words; use bullet points.").
• Self-hosted and private: Calendar, email, and location (for weather) are accessed by your agent on your infrastructure. No need to hand your data to a third-party briefing service. See security best practices and credential management.
• Extensible: Add skills from ClawHub for Google Calendar, Outlook, Gmail, weather APIs, news or RSS. Combine them in one agent; the briefing prompt tells the agent which tools to use and in what order.

Prerequisites

• OpenClaw installed and operational (quick start guide)
• At least one messaging channel configured-e.g. Telegram, WhatsApp, or Slack (channel setup)-so the agent can send the briefing to you
• Calendar skill from ClawHub (Google Calendar, Outlook, or similar) so the agent can read "today's events." Search with openclaw skills search calendar or browse the marketplace
• Optional but recommended: An email skill (Gmail, Outlook, IMAP) if you want "top 3 emails" or "unread summary" in the briefing-see email management for setup
• Optional: Weather skill or API-based skill for local weather; news or RSS skill for a short news digest. Browse ClawHub for "weather" or "news"
• Basic understanding of OpenClaw configuration, agent customization, and how scheduled tasks work (cron or OpenClaw schedule). Gateway must run 24/7 so the scheduled task can fire
• Security best practices reviewed-credentials for calendar, email, and any APIs should be stored securely; see credential management. Audit skills before install

Implementation Guide

Step 1: Install the skills you need

From ClawHub, install at least a calendar skill (Google Calendar or Outlook). Complete OAuth so the agent can read your events. If you want email in the briefing, install an email skill and authorize it. Optionally add weather and/or news skills. Verify each skill works by asking the agent in chat: "What's on my calendar today?" or "What's the weather?" before setting up the scheduled briefing.

Step 2: Design the briefing prompt

The briefing is triggered by sending a fixed prompt to the agent at a set time. The agent uses its skills to gather data, then formats a reply and sends it to your channel. Design one prompt that tells the agent exactly what to include. Example:

Morning briefing prompt (example):
"Prepare my morning briefing for today. Include: (1) My calendar events for today in chronological order, with time and title. (2) Current weather for [your city or location]. (3) A 3–5 bullet summary of my unread emails from the last 24 hours, with sender and subject. (4) My top 3 priorities or tasks for today if I've noted them in memory or tasks. Keep the whole briefing under 300 words. Use clear sections and bullet points."

Adjust sections based on which skills you have (e.g. omit email if you didn't install an email skill; add "top 3 news headlines" if you have a news skill). Store this prompt where your scheduler will send it (e.g. in a cron script or OpenClaw schedule config).

Step 3: Set up a scheduled task

You need a trigger that runs at the same time every day (e.g. 7:00 AM) and sends the briefing prompt to the agent, then delivers the agent's reply to your channel. Two common approaches:

• Cron + channel: Use a cron job on the same machine where OpenClaw runs. The job can call the OpenClaw CLI or send a message into the channel (e.g. via a bot user or internal API) that contains the briefing prompt. The agent responds in the same channel; you see the reply as the morning briefing.
• OpenClaw schedule (if supported): If your OpenClaw version supports built-in scheduled or cron-like tasks, configure a task that runs at your desired time (e.g. 0 7 * * * for 7:00 AM daily), with the task set to send the briefing prompt to your user/channel. Check the official documentation for "scheduled tasks" or "cron."

Ensure the gateway is running 24/7 (e.g. as a systemd service or always-on machine) so the trigger can fire. Use your system timezone or set the cron/schedule to the correct timezone so "7:00 AM" is when you expect.

Step 4: Example configuration snippet

Conceptually, your setup looks like this (exact keys depend on your OpenClaw version and scheduler):

# Example: cron entry (run at 7:00 AM daily)
# Sends the briefing prompt into the channel; agent replies with the digest
0 7 * * * /path/to/openclaw-briefing-trigger.sh

# openclaw-briefing-trigger.sh (pseudo-example)
# - Send message "Prepare my morning briefing for today. Include: (1) Calendar..."
#   to the configured channel/user (e.g. via OpenClaw CLI or internal API)
# - Agent receives it, uses calendar/email/weather skills, posts reply
# - You see the reply in Telegram/WhatsApp/Slack as your morning briefing

Replace with your actual trigger mechanism (script, OpenClaw schedule config, or automation tool). The important part is: same time every day, same prompt, agent reply delivered to your channel.

Step 5: Configure the agent for briefings

In your agent's system prompt or agent customization, add instructions so the agent:

• Recognizes the morning-briefing prompt and responds with a structured digest (sections for calendar, weather, email, tasks).
• Keeps the reply concise (e.g. under 300 words) and uses bullet points or short paragraphs.
• Uses only the skills you've installed (e.g. if no weather skill, say "Weather not configured" or skip that section).

Optionally use persistent memory so the agent can include "top priorities" or "tasks for today" if you've told it those in a previous conversation.

Step 6: Test and refine

Run the briefing manually first: send the same prompt in your channel and check that the agent returns a well-formatted briefing with calendar, weather (if configured), and email summary (if configured). Then enable the scheduled task and verify the next morning that the briefing arrives on time. If something is missing (e.g. wrong timezone, skill not called), check the troubleshooting guide and skill logs.

Best Practices

• Start with calendar only: Get a "today's calendar" briefing working first. Add weather and email once that's reliable. Reduces debugging and confirms the schedule and channel work.
• Set a clear timezone: Cron and system time must match your location so "7:00 AM" is correct. Use TZ= in cron or configure the scheduler timezone in OpenClaw if supported.
• Keep the briefing short: Instruct the agent to stay under 300 words (or your preferred length). Long briefings become easy to skip; bullet points and sections improve readability.
• Combine with email and calendar use cases: Morning briefing is most valuable when it pulls from calendar and email. Use the same skills and credentials; the briefing is just a scheduled "ask" that aggregates them.
• Secure credentials: Calendar and email skills use OAuth or API keys. Store them per credential management; never expose the gateway publicly. See security best practices and network isolation.
• Community: Share your prompt or get help in the Discord community; others often share briefing prompts and skill combos.

Common Issues & Solutions

Need more help? See our complete troubleshooting guide.

Advanced Tips

• Weekday vs weekend briefings: Use different cron entries or schedule rules for weekdays (e.g. 7 AM) and weekends (e.g. 8 AM or skip). Some users prefer a lighter briefing on weekends (calendar + weather only).
• Multiple briefings: Run a second scheduled task (e.g. 6 PM) with a different prompt: "Evening wrap-up: what meetings did I have today, and what's still in my inbox?" for an end-of-day summary.
• Priorities from memory: Use persistent memory to tell the agent "My top priority this week is X." The briefing prompt can ask "Include my stated top priorities from memory."
• Combine with personal CRM: Add "Any follow-ups due today?" to the briefing prompt; if you use the agent to track contacts and follow-ups, it can surface "Follow up with Sarah" in the morning message.

For expert-level configuration, see our advanced configuration guide and creating custom skills if you need a custom data source in your briefing.

Related Resources

Next Steps

After setting up morning briefing, consider:

• Email management - Add "top 3 emails" or "unread summary" to your briefing
• Calendar assistant - View and manage calendar from chat; same skill powers the briefing
• Personal CRM - Surface follow-ups and priorities in the morning message
• Second brain system - Include "notes or tasks for today" from memory
• More use cases - Business, content creation, development
• ClawHub skills - Discover calendar, weather, news, and productivity skills
• Security audit checklist - Keep credentials and skills secure