Day 14 of 28 · OpenClaw Challenge
Build Your Morning Briefing
⏱ 8 min
📊 Intermediate
This is your first mini-project. Over the past week, you've connected email, calendar, memory, web, and files. Today you'll combine them all into something you'll use every single day.
Your morning briefing — a personalized daily summary delivered before you even start working.
What's a morning briefing?
Imagine waking up and checking your phone. Instead of opening five different apps, you see one message from your agent with everything you need to know:
Your schedule for the day. Your most important emails. The news that matters to you. The weather. Tasks that are due. All in one place.
That's a morning briefing.
Knowledge Check
How many different tools does a morning briefing combine?
A
Two — email and calendar
B
At least four — email, calendar, web browsing, and memory (for your preferences)
D
It doesn't use any tools — it's just text generation
A morning briefing pulls from email (important messages), calendar (today's schedule), web (news and weather), and memory (your preferences for what to include and how to format it). It's a multi-tool workflow.
Building it step by step
Here's how you set it up. You tell your agent what you want in your morning briefing:
I want a morning briefing every day at 7am. Here's what I need:
1. Today's calendar - all meetings with prep notes
2. Top 5 important emails from overnight
3. Any action items due today
4. Weather forecast
5. Top 3 tech industry headlines
Got it. I'll build your briefing with those 5 sections and deliver it daily at 7am.
A few questions to personalize it:
— Delivery: WhatsApp, Telegram, or email?
— News focus: general tech, or specific to your industry (DevOps/cloud)?
— Email priority: should I flag emails from your manager and clients as always-important?
WhatsApp, DevOps-focused, and yes flag manager and client emails.
Perfect. Morning briefing configured ✓
I'll send your first one tomorrow at 7am. You can say "update my briefing" anytime to change the format.
↻ Replay conversation
And here's what it looks like when it arrives:
☀️ **Good morning, Alex! Here's your briefing for Thursday, Feb 19.**
📅 **Today's Schedule** (4 meetings)
9:00am — Standup (15 min, usual team)
10:30am — Product review with Sarah
→ Prep: she updated the roadmap yesterday, moved auth to Q2
1:00pm — Client call with Acme Corp
→ Prep: Tom hasn't replied to Sarah's timeline email
3:00pm — 1:1 with your manager
→ No agenda set. Want me to draft one?
📧 **Email Highlights** (5 important)
1. 🔴 Manager — "Quarterly goals: need your input by EOD"
2. 🟡 Acme Corp (Tom) — "Re: Phase 2 timeline" (replied overnight)
3. 🟡 HR — "Benefits enrollment closes tomorrow"
4. 🔵 Sarah — "Roadmap changes committed"
5. 🔵 DevOps team — "Staging deploy successful"
✅ **Action Items Due Today**
1. Submit quarterly goals to manager (EOD)
2. Review Sarah's roadmap changes (before 10:30am meeting)
3. Respond to HR benefits enrollment
🌤️ **Weather**: 64°F, partly cloudy, light wind. No rain.
📰 **DevOps Headlines**:
1. AWS announces new container pricing — 20% cheaper for ECS
2. Kubernetes 1.30 released with improved autoscaling
3. HashiCorp makes Terraform license change — community forks gain traction
↻ Replay conversation
Knowledge Check
The briefing included prep notes for the 10:30am and 1:00pm meetings. How did the agent know what to include?
A
It checked recent emails, documents, and context to generate relevant prep for each meeting
B
The user manually typed the prep notes the night before
C
It copied notes from the calendar invite
D
It made up generic talking points
The agent cross-referenced your calendar with recent emails and documents. It noticed Sarah updated the roadmap (relevant for the 10:30 meeting) and that Tom's email was unanswered (relevant for the 1pm client call). Multi-tool synthesis at its finest.
Customizing over time
Your briefing evolves with you. Add sections, remove sections, change the format:
"Add a section for my stock portfolio."
"Skip the weather — I don't care about it."
"On Mondays, include a summary of what happened last week."
The agent remembers every change. Your briefing gets better the more you use it.
Knowledge Check
You tell your agent "On Mondays, include a weekly summary." Where does it store that instruction?
A
It doesn't store it — you have to remind it every Monday
B
In the calendar event for Monday
C
In long-term memory, so it automatically includes the summary every Monday going forward
D
In a configuration file you have to edit manually
Your agent stores this in long-term memory. Every Monday, it automatically includes the weekly summary without you asking. That's the power of memory combined with automation.
Week 2 — what you've built
Take a step back and look at what you've accomplished this week:
Day 8: Email — your agent triages your inbox and drafts replies
Day 9: Calendar — it schedules, reschedules, and protects your time
Day 10: Memory — it remembers your preferences and patterns
Day 11: Web — it researches and summarizes live internet data
Day 12: Files — it reads your documents and acts on what it finds
Day 13: Multi-step — it chains tools together from a single instruction
Day 14: Morning briefing — your first real automated workflow
You've gone from "what is an agent?" to having a personalized daily assistant in two weeks. Next week, you'll level up — customization, team tools, automation, and cost optimization.
Final Check
What makes the morning briefing more than just a notification?
A
It synthesizes information from multiple tools into actionable intelligence — not just data
B
It uses fancier formatting
C
It plays a sound when it arrives
A notification says "you have 5 emails." A briefing says "here are the 5 that matter, here's why, and here's what you should do about them." That's the difference between data and intelligence.
🌅
Day 14 Complete — Week 2 Done!
"Your first automated workflow is live. From tomorrow, your agent starts working before you do."
Tomorrow — Day 15
Custom Instructions & Personas
Week 3 begins — time to shape your agent's personality and give it specific instructions for how to behave.