
Inbox Declutter
Summarize newsletters, classify email noise, and send a clean daily inbox digest with preference learning.
Ready to automate your workflow?
Deploy your own OpenClaw instance and try these use cases today.

Aggregate all family calendars into a morning briefing, monitor messages for appointments, and manage household inventory through chat.
Every morning at 8 AM, compile a family briefing: 1. Fetch my Google Work Calendar (read-only) 2. Fetch shared Family Google Calendar 3. Fetch partner's calendar (shared view) 4. Check ~/Documents/school-calendars/ for new PDFs → OCR and extract events Include: - Today's events (color-coded by source) - 3-day lookahead for conflicts - New events added since yesterday - Weather context for outdoor events Deliver via Telegram family channel.
calendar-api
Built-inimessage
Built-intelegram
Built-inical)imessage skill for message monitoring (macOS only)Configure OpenClaw to pull from all family calendar sources:
## Calendar Sources
On morning briefing (8:00 AM):
1. Fetch my Google Work Calendar (read-only OAuth)
2. Fetch shared Family Google Calendar
3. Fetch partner's calendar (shared view)
4. Check ~/Documents/school-calendars/ for any new PDFs → OCR and extract events
5. Check recent emails for calendar attachments or event invitations
Compile into a single briefing:
- Today's events (all calendars, color-coded by source)
- Upcoming 3-day lookahead for conflicts
- Any new events added since yesterday
- Weather context for outdoor events
Deliver via Telegram/Slack family channel.This is the key differentiator — the agent watches passively and acts when it recognizes something actionable:
## Message Monitoring (HEARTBEAT.md)
Every 15 minutes:
1. Check new iMessages across all conversations
2. Detect appointment-like patterns:
- "Your appointment is confirmed for..."
- "Can we meet on [date] at [time]?"
- "Practice moved to Saturday at 3pm"
3. When detected:
- Create calendar event with details
- Add 30-minute driving buffer before AND after
- Send confirmation to family Telegram: "Created: Dentist appointment, Tue 2pm. Added drive time 1:30-2:00 and 3:00-3:30."
- If relevant to partner, add invite
4. Detect promise/commitment patterns:
- "I'll send that over by Friday"
- "Let's do dinner next week"
→ Create calendar hold or reminder## Pantry Tracking
Maintain ~/household/inventory.json with:
- Item name, quantity, location (fridge/pantry/basement)
- Last updated timestamp
- Low-stock threshold
Update methods:
- Photo: User sends photo of fridge/pantry → vision model extracts items
- Text: "We're out of eggs" / "Bought 2 gallons of milk"
- Receipt: Photo of grocery receipt → update inventory
Query: Either partner can ask via Telegram:
- "Do we have butter?" → Check inventory, respond with location and quantity
- "What's running low?" → List items below threshold
- "Generate grocery list" → Compile low-stock items + any recipe ingredients neededangiolillo, who detailed the pain of checking 5+ calendars separately each morning.@theaaron called chat-based calendar management "one of the best uses of an LLM I've ever experienced."dns_snek noting: "I forget where I put things down 5 seconds ago... It's genuinely a big problem for me because I let things expire."Skip the setup — get a fully managed OpenClaw instance ready to run this use case.
| Starter Plan | Pro Plan | |
|---|---|---|
| Monthly | $49/mo | $99/mo |
| Infrastructure | 2 vCPU · 2 GB RAM · 20 GB SSD | 2 vCPU · 4 GB RAM · 50 GB SSD |
| AI Credits | $10/mo included | $25/mo included |
| Messaging | Telegram (Discord/Slack coming soon) | Telegram (Discord/Slack coming soon) |
Why Pro? Managing multiple calendars, reminders, and meal planning with photo OCR requires 4 GB RAM. Starter ($49/mo) works for basic calendar alerts, but the full household assistant needs Pro.

Summarize newsletters, classify email noise, and send a clean daily inbox digest with preference learning.

Build and maintain a personal CRM automatically — daily email/calendar scanning, contact enrichment, meeting prep briefings, and natural language queries.

Decentralized project coordination where subagents work autonomously on tasks, coordinating through shared STATE.yaml files rather than a central orchestrator.
Join the community
Subscribe to our newsletter for the latest news and updates