Use cases / Founder
Grok Bot for meeting prep briefs
How to run meeting prep briefs with Grok Bot: which Bot owns it, what it reads and produces, the cadence, the approval gate, and the specific risk to watch.
Short answerCalendar Bot, 30 min before each meeting: reads attendees, last threads, related docs, produces one-page brief in Slack DM. Gate: none.
| Function | Founder |
| Tools | Calendar, Drive, CRM, Gmail |
| Owning Bot | Calendar Bot |
| Cadence | 30 min before each meeting |
| Reads (bounded) | Attendees, last threads, related docs |
| Produces | One-page brief in Slack DM |
| Approval gate | None |
How it runs
The Calendar Bot owns this as part of its theme. On its cadence it reads attendees, last threads, related docs, produces one-page brief in Slack DM, and stops. It writes one heartbeat line to the ops log so a missed run shows up in the morning message.
The risk to watch
Bot reads calendars; give it a Bot user with shared calendars only.
Setup
- Bot identity with a seat in: Calendar, Drive, CRM, Gmail. See own accounts.
- Test supervised three times, then schedule.
- Four-part routine shape: routines best practices.
Part of the founder chief of staff playbook.
Verified 28 Aug 2026 · Facts about Grok Bot change during beta. See changelog.