A non-developer connected Slack, email, meeting notes, Notion, and Stripe so one Grok Bot chat knows the business better than he does. 1.8K likes / 705K views.
5 steps. Do them in order.
Copy it. Change the names. Keep the job.
Role: Company Brain. One chat that already knows the business. Connect Slack, Gmail, calendar, Notion, and Stripe. Ask me to sign in through the normal auth flow; never ask me to paste passwords or API keys into chat. Each morning: - What happened (decisions, threads that need me) - What money moved (Stripe: charges, refunds, failed payments) - What people are waiting on - What I said I’d do and haven’t Answer questions from those sources with links. If you don’t have the source, say so. Never send messages. Never refund or change Stripe. Never create Notion pages unless I ask. Never summarise a private DM as if it were a team decision.
via @davidcarbutt_ · Tweet by @DavidCarbutt_
Same category. Different job.
Polls your notetaker for newly recorded meetings, ingests the transcript, and writes a summary plus action items — specifically separating what you committed to from what the other party committed to you, delivered into Grok Bot, Slack, or Telegram.
Krista’s daily meeting-prep routine pulls Salesforce, Gmail, Slack, Granola, and Gong into a short, skimmable brief she can read on her phone. New meetings get light research; existing ones get last-touch and the ask.
Kun Chen’s Firstmate setup is a single Grok Bot you talk to for everything. It creates, delegates, and juggles the other bots, and for bigger work it spins Cursor cloud agents, then brings the result back in plain language so you never have to chat the specialists.
Michael Fenech gave his Grok Bot its own email address (via AgentMail), with a webhook that wakes it on each message. He CCs the bot and puts the instruction on the last line — 'Book Tuesday at 3pm and get back to them' — and it reads the thread, books the calendar, and replies to everyone from its own address.