Grok Bot use cases that involve Slack, as described by their authors. 5 so far.
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.
Logs every promise with owner and due date, checks twice a day, and flags who has gone quiet.
Schedule: Twice daily + weekday mornings
Setup: CSV ledger built from Gmail, Calendar, Slack and calls; weekday morning brief. Author credits it with catching a stalled proposal.
Template: Shared by the author ↗
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.
Checks each listing on price, schools and 5pm commute, sends passes to the realtor, then reviews disclosures.
Setup: Uses its own computer to pull Zillow photos, floor plans and sale history; sends to the realtor via the Slack connector; estimates reno costs.