Meeting Prep Auto-Brief
30 minutes before any meeting, get a one-page brief — attendees, last interaction, related notes, agenda items pulled from the invite.
Productivitymedium~30m setup
- Tools
google_calendargmailmemorymemory_search- Channels
telegramios- Uses
cron
Walking into a meeting cold means the first 5 minutes are spent remembering who's on the call and what was decided last time. A 30-minute pre-meeting brief eliminates that — by the time the meeting starts, you're already up-to-date.
What it does
- Watches your calendar for upcoming meetings
- 30 minutes before each one, generates a brief
- Pulls: attendee names, your last interaction, prior meeting notes, related email threads from the past 2 weeks, related Linear/Jira tickets if you connect those
- Surfaces unanswered questions from previous meetings
- Delivers to whichever channel you have nearby (iOS push if mobile, Telegram if desk)
What you'll need
- Google Calendar integration
- Gmail integration
- Memory for prior meeting notes
- Optional: Personal CRM plugin for richer attendee context
- Cron running frequently (every 5 min) to catch upcoming meetings on time
Setup
1. Define the brief format
Send to Flowly
Remember the meeting prep format:
For any calendar event with at least one external attendee:
📅 <Time> — <Title>
🧑 <Attendees> — for each external person, 1 line:
their company, your last interaction (date + 1-line context)
📝 Prior context (if applicable):
- Last meeting with this group: <date> — link
- Open questions from last time: <list>
🎯 Apparent agenda:
- Pulled from invite description, parsed as bullets
🧠 Related notes:
- Top 3 hits from memory_search using meeting title + attendees as query
📨 Related email (last 14 days):
- 3 most recent threads with these attendees, 1-line summary each
2. Schedule the watcher
Send to Flowly
Cron "meeting-prep" every 5 minutes from 7 AM to 7 PM:
1. Read calendar events 25-35 minutes in the future
2. For each, check memory: have I sent a brief for this event already
(tag "meeting-brief-sent:<event-id>")?
3. If not, generate the brief using the format above
4. Send to:
- iOS push if my last activity was on iOS
- Otherwise Telegram
5. Log "meeting-brief-sent:<event-id>"
Skip events where:
- No external attendees
- All-day events (lunch, focus time)
- Recurring 1:1s I've explicitly opted out of (memory tag "no-prep:<event-id>")
3. Opt-out for routine meetings
For your weekly 1:1 with a known team member, prep is overkill:
Send to Flowly
Don't prep for these meetings:
- Weekly 1:1 with @manager
- Daily standup
- Any meeting titled "focus" or "no agenda"
Saved to memory; cron skips them.
4. Post-meeting hand-off
After meetings, if you ran the meeting coach (see Meeting Notes use case), the prep can include "decisions and action items from last meeting" — because they're in memory under the right tag. Use this loop to ensure continuity across recurring meetings.
Tips
- 30-min lead time is the sweet spot. Earlier and you forget; later and you're already in another tab.
- Don't surface every related email. Top 3, sorted by recency. Floods are useless.
- Brief on iOS, ack on Desktop. The brief lands on phone for visibility; the actual meeting tools (notes, recording) are at Desktop. Pair them.
- External-only filter is critical. Internal team rituals don't need briefs; they need attention. Briefs would be noise.
- Trust takes a week. First few briefs will feel surveillance-y. After a week, you'll stop walking into meetings cold and notice the difference.
- Privacy. The brief contains information about people on your calendar. Don't broadcast it to a shared channel — keep it in your personal Telegram.