Real Grok Bot use cases for work & productivity, with how each bot is set up. 14 so far.
At day's end it pulls every decision and to-do from Granola call notes into Linear, then prints a paper focus list each morning.
Schedule: End of day + every morning
Setup: Calls are transcribed by Granola; the author tells the bot at end of day to extract decisions and to-dos and file them as Linear tickets.
Text or call a Google Voice number with a secret word and a request, and the bot handles it and texts back, even from a flip phone.
Setup: Free Google Voice number plus Gmail; only listens to the owner's number and secret word; three permission levels, with money, deleting or contacting someone new waiting for an in-app tap; texts capped at 20 a day. Author says a template link is in the post.
Searches chats, reads threads and pulls attachments across every network linked in Beeper, with no WhatsApp connector needed.
Setup: Beeper Desktop runs on an always-on Mac with its local API and MCP server; Tailscale Serve shares it on a private tailnet; a small proxy on the bot's computer points an MCP connector at it, with the Beeper token kept in a connector secret. Read-only and draft-only by default, never sending.
Reads the personal calendar hourly and copies events marked “Team” to the shared team calendar.
Schedule: Hourly
Sorts forwarded client emails, briefs the right agent and flags what needs the author.
Setup: Gmail filters forward client emails to the email address of the author's chief-of-staff bot.
Gets newsletters out of the main inbox and combines all five into a single digest every morning.
Schedule: Every morning
Setup: Moved the newsletter subscriptions to the bot's own email address and set up an agent that merges them.
Set up Obsidian as a plain-Markdown shared memory where several bots read, write and hand off work.
Setup: Each bot has its own folder, status page and append-only log; handoffs go through a shared inbox; one rules file governs all bots.
30 minutes before standup it reads everything relevant and hands over one page with agenda, scope and things to raise.
Schedule: Weekdays, 30 min before sync
Setup: Reads the calendar, Notion agenda, planning notes, Slack since yesterday, Linear progress and the engineering digest. The author says the prompt is on the card in the post.
A chief of staff for client priorities plus bots for production monitoring, data takedowns, inbox cleanup and Linear triage.
Schedule: Daily / weekly
Setup: Chief of staff reads Slack, Linear, GitHub, Gmail, Calendar and Notion; a monitor watches Vercel logs, the database, GitHub and support email; a privacy guard re-checks takedowns weekly; others triage spam, LinkedIn DMs, iMessage and physical mail via Earth Class Mail's MCP.
Every email is copied to the bot's own address; it only flags what needs a decision and checks spam twice a day.
Schedule: On email + twice daily
Setup: Gmail forwarding to the bot's claimed address wakes it on each email. It never replies on its own.
A long client email forwarded to the bot's address became a broken-down project in Notion.
Schedule: On email
Setup: Uses the bot's own email address.
Added 5 weeks of leave, cleared 24 events, emailed every participant and made a to-do list, by voice while driving.
Setup: Author talked to Grok in the car, which handed the work to his bot team.
The bot has its own Fastmail mailbox, calendar, contacts and notes, and now answers forwarded mail live.
Schedule: Was every 15 min; now on new email
Setup: Previously a routine checked the inbox every 15 minutes; now a Fastmail forward rule to the bot's own Grok Bot email address triggers it instead.
The chief-of-staff bot's own email address receives signups, verification codes, receipts and newsletters.
Setup: Nothing triggers unless a routine is set; sending still needs approval.