agentos.guide › blog

Grok Bot Slack: Set Up A Shared Team Bot, Write Its Triggers And Guard Its Approvals In Your Agent OS

By Julian Goldie · 31 October 2026 · agentos.guide

Grok Bot Slack becomes far easier to run when your Agent OS does the paperwork: the Bot brief, the trigger wording, the Ask first rules and the weekly usage audit.

Grok Bot itself does the Slack work, as a shared Bot your teammates @mention in channels.

Your agent in the Agent OS writes and checks everything around it, so the setup stays tidy as the team grows.

If you would like help planning it, book a free SEO strategy session with my team.

What you are actually setting up

A shared Bot is one Bot you share with your Cursor team, and each person's conversation with it stays private (Shared Bots docs).

Once the owner or a Manager connects it to Slack, it gets its own Slack app and handle.

Separately, a routine can carry a Slack trigger, which the routine docs describe as part of the routine rather than the Slack app.

Your Agent OS sits beside all of this as the planning desk.

Quick start in five moves

1. Check your plan: Premium, Super and Ultra include Grok Bot, Plus doesn't (plan page).
2. In Grok Bot, choose +, then Create a Bot, and share it through Share.
3. Click the Bot's name, find Bring to your team's Slack and choose Connect; a Slack admin may need to approve it.
4. Have each teammate link Slack under Settings > General > Shared Bots.
5. Invite the Bot to one channel, then use the prompts below to finish the job.

Prompt 1: have your agent write the shared Bot brief

The brief decides what every teammate's chat inherits, so write it before you share.

I'm setting up a Grok Bot shared Bot that my team will @mention in Slack.
Write me a one-page brief with:
1. A short Bot name people will type after @.
2. One sentence on what it helps the team with.
3. A table of apps, secrets, skills and files to add, with a keep/remove
   decision for each. Remember: anything I add works in every teammate's chat.
4. Who should be a Manager and who should be a Collaborator.
5. The three Slack channels it should join first, and the ones it must stay out of.
Keep it plain English and ask me questions where you need facts about my business.

Paste the brief into the Bot's setup steps, one card at a time.

Read the keep/remove table twice, because a shared Bot's apps, secrets and files carry into every teammate's conversation.

If a key belongs to one person, leave it off the shared Bot and let that person connect their own account when asked.

Prompt 2: turn a job into a narrow Slack trigger

Triggers can fire on a Bot mention, a word or phrase, your reaction, or any message, in one channel or across Slack.

Broad listeners burn usage, so let your agent tighten the wording first.

Turn this job into a Grok Bot routine with a Slack trigger: [describe the job].
Rules:
- Watch ONE channel and ONE phrase. Never "any message".
- Say exactly what the Bot does when it fires and where it replies.
- End with: "Never post outside this thread without my approval."
- Give me the sentence I should expect to see under "When to run".
- List two test messages: one that should start the routine and one that shouldn't.

Paste the result into your chat with the Bot, then press Test on the routine.

Only new messages start a run, so post a fresh test message after the trigger exists.

🔥 Get the Agent OS these prompts were written for

Inside the AI Profit Boardroom you get the installable Agent OS, step-by-step video trainings, four coaching calls a week and 3,400+ members running their own agent workflows.

→ Join the AI Profit Boardroom

Prompt 3: write the Ask first rules

In a thread, the approval card gives the requester three buttons, Allow once, Deny and View details, and no one else can use them.

Your rules decide how often that card appears.

Write a short rule list I can paste into my shared Grok Bot and ask it to remember.
Cover:
- Ask first before sending anything to a customer, client or shared Slack Connect channel.
- Keep Slack drafts on for anything external.
- Never use @here or @channel; mention the named person or user group instead.
- Reply in the thread you were asked in, never in a new post, unless told.
- If an approval is denied, stop and wait for my next message.
Keep each rule under 15 words.

Drafts are the default anyway, and since v0.77.0 a Slack draft shows a formatted preview and who it will notify (changelog).

Prompt 4: the weekly usage and routine audit

Every routine run spends usage, and a shared Bot reply is billed to whoever it answers.

Since v0.75.5, routines are capped at 300 runs an hour in total and 200 an hour each.

Here is my list of Grok Bot routines with their triggers and how often they ran
this week: [paste list].
For each one, tell me:
- Keep, narrow, widen the schedule, or pause.
- Whether it could hit 200 runs an hour on a busy day.
- A tighter channel or phrase if the trigger is broad.
Finish with the three changes that would save the most usage.

The routine usage notes say to pause, widen and narrow before you raise any limit, so do the audit first.

Prompt 5: the teammate onboarding note

Write a Slack message (under 120 words) introducing our shared Bot to the team.
Include:
- How to link: Settings > General > Shared Bots > Link.
- Your chat with the Bot is private; the owner can't read it.
- Only you can answer approval cards on your own requests.
- Replies use your own Grok Bot usage, so keep requests specific.
- Two example requests for our team.
Friendly, direct, no hype.

Unlinked teammates get limited features and can't reach the owner's logins or private data, so the link step matters.

Post the note in the first channel the Bot joins and pin it so new starters find it.

Anyone who messages the Bot before linking is sent the steps anyway, but the pinned note saves that round trip.

The daily workflow once it is live

1. Teammates @mention the Bot in the channel thread where the question came up.
2. The Bot answers there and, for a shared Bot, can hand work to that person's own Bots, with replies posted back to the thread (handoff docs).
3. Anything risky appears as a Review an action card for the person who asked; since v0.77.0 those auto-review cards wait 30 minutes.
4. Routine posts don't buzz your phone since v0.75.8, so skim the routine threads once a day.
5. On Fridays, run Prompt 4 in your Agent OS and apply the changes.

📞 Want your team's Slack workflow mapped for you?

Book a free SEO strategy session and my team will help you decide which channels, triggers and approval rules your Bot needs.

→ Book a free SEO strategy session

Five mistakes your agent can catch before launch

Ask your agent to read your brief, triggers and rules against this list before anyone in Slack sees the Bot.

• A trigger on every message. The docs say it runs often and spends usage on messages that never needed the Bot, so swap it for one phrase in one channel.
• Secrets nobody should share. A key added to a shared Bot works in every teammate's chat, so move personal keys out before you share.
• Unlinked teammates. Until someone links Slack, they get a cut-down Bot, so put the link path in the launch note.
• Drafts switched off too early. With drafts off, sends follow your Auto Review settings, so keep drafts on until the team trusts the flow.
• The wrong Bot in the channel. A personal Bot asked in a channel thread can't hand work off, so the channel needs the shared Bot.

Give your agent the official pages as context so it checks against the docs, not its own memory.

The Shared Bots page and the approvals page are the two worth pasting in.

Once the check passes, run the onboarding note from Prompt 5 and launch in one channel.

Limits your agent should know about

• Shared Bots need a Cursor team and always run in the cloud.
• In channels and threads a shared Bot uses its owner's apps and one shared computer of its own.
• A personal Bot can't hand off work from a Slack channel thread.
• Routines on a Team Bot can read any channel the two of you sit in together (v0.75.8).
• Deleting a shared Bot removes its Slack app for everyone and can't be undone (teams docs).
• The v0.61.0 notes call the Settings section Team Bots; current docs call it Shared Bots.

Where to go next

Get one channel working with one narrow trigger before you add a second.

Then copy the same brief, trigger and rule pattern to the next team.

If you want a hand choosing that first channel, book a free call with my team and we will look at your workflow together.

For the full Agent OS and the trainings behind these prompts, join the AI Profit Boardroom.

FAQ

Does my Agent OS connect directly to Grok Bot?

No. Grok Bot runs the Slack side. Your agent in the Agent OS writes the brief, triggers, rules and audits that you paste into Grok Bot.

Which prompt should I run first?

Prompt 1, the shared Bot brief, because the apps, secrets and files you add work in every teammate's chat.

How do I stop a Slack trigger eating usage?

Limit it to one channel and one phrase, avoid any-message triggers, and run the weekly audit prompt to pause or narrow noisy routines.

Can the Bot ping the whole channel?

No. Since v0.68.1 a Team Bot can mention a Slack user group, but @here and @channel still don't ping anyone.

Final word on Grok Bot Slack

Write the brief, tighten the trigger, set the rules and audit weekly, then join the AI Profit Boardroom for the full Agent OS behind your grok bot slack workflow.

Related guides on agentos.guide

→ Grok Bot Teams: Roll Out A Shared Bot In Your Agent OS

→ Grok Bot Routines: Plan And Review Them In Your Agent OS

→ Grok Bot Plugins: 5 Prompts To Run Them In Your Agent OS

→ Grok Bot AI Full Course (Step By Step)

📺 Video notes + links to the tools 👉

🎥 Learn how I make these videos 👉

🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉

← all guides on agentos.guide