✦ 66 · solid

One chat that knows the business better than I do

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.

verified 2026-08-21 ~60 min setup work scouted on x
install in grok bot

How it’s set up

  1. In Grok Bot, create a bot named Brain and connect Slack, Gmail, Notion, GitHub, Google Calendar, Stripe.
  2. Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: company cos.
  3. Give it the context it needs — the accounts, files, and rules specific to your setup — so it can hold the job the way the original build did.
  4. Run it on demand; it acts once you approve each step.
  5. Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.

Prompt

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.

Why it’s cool

Six tools feeding one chat isn’t new; what’s notable is who built it — a non-developer, in one sitting, with normal logins and zero code. The daily brief format (decisions, money moved, who’s waiting, what you said you’d do) is a template anyone can copy without touching an API.

prompt reconstructed by the Curator from @DavidCarbutt_'s published setup — not their verbatim text

prompt
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.
then paste it into Grok

Copy the prompt and paste it into Grok.

what you need

Reconstructed from @DavidCarbutt_'s published Grok Bot build. Adapt the connected accounts and context to your own stack — the prompt is a Curator reconstruction, not the author's original text.
by @DavidCarbutt_

related

✦ 65 · solid

Get interrogated until your plan is actually specific

Nate Herk’s week-of-lessons article starts with a job he actually runs: a Grill Me skill that relentlessly interviews him about the business, goals, and plans until the bots share context. He uses it before quarterly planning or a new project — not a four-bot staffing listicle.

via @nateherk · 𝕏
✦ 62 · worth a look

It noticed who I was ignoring and booked the call

Jesse’s Chief of Staff reads Gmail, Calendar, Slack/Discord, and sends a 5am summary with fires. Unlike his old script, he can ask it to do something after: it noticed he was ignoring Nate Berkopec, opened SavvyCal, and found a time in both timezones.

via @jessethanley · 𝕏

the week's best, in one email

new plugins, use cases and collections. one email a week. that's it.

one email a week. what we do with it.