Remote OpenClaw Blog
The Daily Intelligence Briefing: OpenClaw's Most Popular Workflow
8 min read ·
Remote OpenClaw Blog
8 min read ·
Every morning, most knowledge workers open the same five apps in the same order: calendar, email, weather, task manager, messages. According to a McKinsey Global Institute report, the average professional spends 28% of their workweek reading and answering email alone. Add calendar checking, weather lookups, and task review, and the first 20-30 minutes of every day disappear before any real work starts.
The OpenClaw daily briefing compresses all of that into a single Telegram message delivered at a time you choose. No app switching. No scrolling through notification stacks. One message, everything you need, waiting when you wake up.
Based on community data from the Remote OpenClaw Skool community, over 40% of active operators run some version of a daily briefing. It is the first workflow most people set up after their initial OpenClaw deployment, and it is the one they cite most often when asked what makes OpenClaw worth the setup effort.
The briefing works because it maps perfectly to how OpenClaw operates. The agent has persistent access to your connected services. It runs on a schedule via HEARTBEAT.md. It formats output and delivers it to a messaging channel you already check. No new habits required. No dashboards to open. Just a message in Telegram that replaces five separate app checks.
For a detailed walkthrough of the Daily Briefing skill itself, see the Daily Briefing Skill Guide.
The most effective briefings include six data sources. You do not need all six from day one, but operators who have iterated on their briefings over weeks consistently converge on this combination.
Pull today's events from Google Calendar, including start times, attendees, and meeting links. OpenClaw uses the Google Calendar API with OAuth credentials stored in your deployment. The briefing shows the next 12 hours of events by default, with prep notes for meetings that have attached agendas.
Not every email. OpenClaw scans your inbox for unread messages received since your last briefing and groups them by priority. High-priority emails (from known contacts, containing keywords like "urgent" or "deadline") get full subject lines and sender names. Low-priority emails get a count: "14 other emails received overnight."
The Gmail integration uses the Gmail API with read-only scope by default. You can extend this to draft replies, but most operators keep the briefing read-only and handle responses separately.
Current conditions and a 12-hour forecast from OpenWeatherMap (free tier allows 1,000 API calls per day). The briefing includes temperature, precipitation probability, and a plain-language summary like "Light rain expected after 2 PM, bring an umbrella."
Tasks due today and overdue tasks from your task management system. OpenClaw integrates with Todoist, Things 3 (via AppleScript on Mac), Apple Reminders, and plain-text task files stored in your deployment. The briefing sorts tasks by due date and flags anything overdue in bold.
Custom reminders you have asked OpenClaw to track. "Remind me to follow up with Sarah on Tuesday" becomes a line item in Tuesday's briefing. OpenClaw stores these in its memory system and surfaces them on the appropriate date.
Pull from Google Contacts or a local contacts file. When a birthday falls on today's date, the briefing includes it with a suggested action: "Sarah's birthday today. Last year you sent flowers."
OpenClaw's scheduling system runs through HEARTBEAT.md, a Markdown file in your deployment directory that defines recurring tasks using standard cron syntax. The OpenClaw scheduler checks this file on each heartbeat cycle (default: every 30 minutes) and fires any tasks whose cron expression matches the current time.
Navigate to your OpenClaw deployment directory and open HEARTBEAT.md. If the file does not exist, create it in the root of your OpenClaw config folder.
# HEARTBEAT.md — Scheduled Tasks
## Daily Morning Briefing
- cron: 0 7 * * *
- task: Run the morning briefing skill. Pull calendar events, email summary, weather forecast, tasks due today, reminders, and birthdays. Format as a single consolidated message and send to Telegram.The cron expression 0 7 * * * means "at 7:00 AM every day." This uses your server's timezone, not your local timezone. If your VPS runs in UTC and you are in EST (UTC-5), set the cron to 0 12 * * * to receive the briefing at 7:00 AM local time.
Common scheduling patterns:
0 7 * * 1-5 — Weekdays only at 7 AM0 6 * * * — Every day at 6 AM (early risers)0 7 * * 1-5; 0 9 * * 0,6 — Weekdays at 7 AM, weekends at 9 AMYour OpenClaw instance must have a heartbeat interval short enough to catch the cron window. The default 30-minute heartbeat means the briefing could fire anywhere within a 30-minute window of the target time. For more precise delivery, reduce the heartbeat interval to 5 or 10 minutes in your config:
# In your OpenClaw config
heartbeat_interval_minutes: 10A 10-minute interval means your 7:00 AM briefing will arrive between 7:00 and 7:10 AM. Most operators find this acceptable. Shorter intervals increase API token usage because each heartbeat consumes a small number of tokens for the scheduling check.
Marketplace
Free skills and AI personas for OpenClaw — browse the marketplace.
Browse the Marketplace →For a deeper dive into cron job configuration, see the OpenClaw Scheduled Tasks and Cron Guide.
Telegram is the preferred delivery channel for daily briefings because it supports rich text formatting (bold, italic, code blocks), link previews, and has no rate limits for bot messages. According to Telegram's documentation, the Bot API supports up to 30 messages per second to different users, which is far more than any briefing needs.
Message @BotFather on Telegram and create a new bot. Copy the bot token. Store it in your OpenClaw environment variables:
TELEGRAM_BOT_TOKEN=your_bot_token_hereSend any message to your bot, then visit https://api.telegram.org/bot<YOUR_TOKEN>/getUpdates to find your chat ID. Add it to your config:
telegram_chat_id: "123456789"For security, restrict your bot to only accept messages from your Telegram user ID. This prevents unauthorized users from sending commands to your OpenClaw instance. See the Telegram ALLOWFROM Guide for the full setup.
Send a test message through OpenClaw to confirm delivery works before relying on the scheduled briefing. Run the briefing skill manually once and verify the message arrives in your Telegram chat with correct formatting.
Once the basic briefing runs reliably, most operators customize it within the first week. Here are the most common modifications based on patterns from the community.
Use OpenClaw's web browsing capability or an RSS feed integration to include 3-5 headlines from sources relevant to your industry. Keep it short. The briefing should inform, not overwhelm. Operators who add more than 5 headlines report ignoring the news section within a week.
Pull stock prices, crypto portfolio values, or revenue metrics from connected APIs. One community member pulls their Stripe dashboard summary, showing yesterday's revenue, new subscribers, and churn count. Format: "Stripe: $342 revenue, 4 new subs, 1 churn."
Some operators include a "Focus for today" line that OpenClaw generates based on their calendar density and task priority. Light calendar day? "Deep work day — block 3 hours for the product roadmap." Back-to-back meetings? "Meeting-heavy day — prep for the board review at 2 PM."
Use two separate cron entries with different task descriptions. Weekday briefings include work calendar and email. Weekend briefings drop the work context and add personal items: family events, weather for outdoor plans, and personal project tasks.
Some operators run an evening briefing at 6 PM that summarizes what happened during the day: emails sent, tasks completed, calendar events attended, and a preview of tomorrow. This takes the same skill with a modified prompt and a second cron entry.
One operator in the Remote OpenClaw community tracked their morning routine for two weeks before and after implementing the daily briefing. The results:
The time savings alone are significant, but operators consistently report a second benefit: reduced decision fatigue. Instead of deciding which app to check first and what to prioritize, the briefing presents everything in a pre-sorted, pre-summarized format. You start the day knowing exactly what is ahead.
Over a year, 19 minutes per day equals 115 hours — nearly three full work weeks recovered from passive information gathering.
Most operators modify their briefing 3-4 times in the first month. The most common changes:
By week 4, the briefing stabilizes and operators rarely change it again. The key is to start with the six core sources and then adjust based on what you actually read versus what you skip.
An OpenClaw daily briefing can pull from Google Calendar, Gmail or IMAP email, OpenWeatherMap for weather forecasts, local task files or Todoist/Things 3, Apple Reminders, contacts databases for birthdays, and any API-connected service. The HEARTBEAT.md cron triggers the briefing at your chosen time, and OpenClaw compiles everything into a single Telegram message.
Add a cron entry to your HEARTBEAT.md file with the pattern 0 7 * * * and a task description like "Run morning briefing skill." OpenClaw's scheduler checks HEARTBEAT.md on each cycle, and the cron expression tells it to fire at 7:00 AM server time daily. Make sure your server timezone matches your local timezone, or adjust the hour accordingly.
The daily briefing works on any channel OpenClaw supports, including Telegram, WhatsApp, Slack, Discord, and Signal. Telegram is the most popular choice because it supports rich formatting, link previews, and has no rate limits for bot messages. WhatsApp works but has more limited formatting options.