Grok Bot Slack: Set Up A Shared Bot In 4 Steps (2026)

Grok Bot Slack runs through a shared Bot: you share one Bot with your Cursor team, connect it to your Slack workspace, and from then on anyone in a channel can @mention it and get the answer in that thread.

That sounds like one switch, but it is really three separate connections, and mixing them up is the setup mistake I see most.

Below is the exact order I'd follow, the settings I'd change on day one, and the release notes from x.ai/changelog/bot that explain why Slack behaves the way it does now.

If you want my team to help you pick the first Slack jobs to hand to an agent, book a free SEO strategy session and we'll map them with you.

The three Slack pieces you are actually wiring up

Grok Bot touches Slack in three different ways, and each one lives in a different place.

The Slack app connector. It lets a Bot read and post as the Slack user you connected, only in channels that user can post in, per Use the computer and apps.
A shared Bot's own Slack app. A shared Bot gets its own Slack app and handle, so anyone in the channel can give it work, per Message and collaborate.
A Slack trigger on a routine. It starts a routine when something happens in Slack, and the routine docs say plainly that the trigger is part of the routine, not the Slack app.

The connector is personal, the shared Bot's app is team-wide, and the trigger is automation.

Keep those three apart and every later step makes sense.

Four checks before you touch a single setting

Your plan includes Grok Bot. Per docs.x.ai/x-subscription/grok-bot, Premium, Super and Ultra include it, and Plus doesn't.
You are on a Cursor team. Shared Bots are only for Cursor team members with Grok Bot, and a missing Browse shared Bots option under + means you aren't on a team or the app needs an update.
The Bot runs in the cloud. A Bot that runs on your own computer can't be shared.
You know your Slack workspace admin, because the app may sit at Awaiting admin approval until they approve it.

Routines aren't on every plan, and since v0.77.0 the Bot names the plan that includes them when yours doesn't.

Step 1: Build the Bot and share it with your team

Slack comes after sharing, so start inside the Grok Bot app.

Choose + in the sidebar, then Create a Bot, and give it a short name people will happily type after the @.
Tell it what it should help the team with. One sentence is enough.
Work through its setup steps for apps, secrets, skills and files.
Click the Bot's name at the top of the chat and choose Share.

Under Who has access, pick your whole team or People you invite.

Add helpers as Manager if they should change instructions, skills, memory and apps, or as Collaborator if they only chat with it.

Only add keys and files every teammate may use, because the Shared Bots docs confirm that a shared Bot's secrets, apps and files work in every teammate's chat.

Step 2: Bring the shared Bot to your team's Slack

The owner or a Manager does this, and only after the Bot is shared.

Click the Bot's name at the top of the chat.
Find Bring to your team's Slack and choose Connect.
If the status reads Awaiting admin approval, ask your Slack workspace admin to approve the app.

Once it says Connected, teammates can DM the Bot or mention it in channels (How do I add a shared Bot to Slack?).

Since v0.64.0 on 30 September, the creator of a published Team Bot can add Managers who handle the Slack app too, so the creator isn't the bottleneck.

🔥 Want your Slack Bot set up next to the rest of your agent stack? Inside the AI Profit Boardroom you get step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members swapping the exact Bot rules they run. → Join the AI Profit Boardroom

Step 3: Get every teammate to link their Slack account

This is the step people skip, and it decides what the Bot will do for them.

Each teammate opens Settings > General > Shared Bots and chooses Link.

Anyone who messages the Bot before linking gets a reply with the linking steps.

Unlinked people get less, and that's deliberate.

v0.77.0: an unlinked person who mentions the Bot gets nothing from the owner's saved logins or private data.
v0.78.1: the Bot now explains to unlinked people what is restricted and walks them to the link step.

Paste the Settings path into your launch announcement so nobody has to ask.

Step 4: Invite it to channels and run a first mention

The v0.61.0 release notes say a Team Bot in Slack replies in threads, reads channels it has joined, answers workflow mentions and starts new posts.

So invite it only where you actually want it reading.

Then run a harmless first request, such as asking it to summarize the last ten messages in the channel and list open questions.

Check three things in the reply: it landed in the thread, it acted for you, and nothing went anywhere else.

From v0.68.1 it can tag a Slack user group, but @here and @channel stay silent.

How approval cards behave inside a Slack thread

A shared Bot asks the person it's answering before risky actions.

Inside a thread it shows up as a Review an action card, and nobody but the requester can press its Allow once, Deny or View details buttons.

That card shipped in v0.63.0 on 29 September.

Since v0.77.0, auto-review approval cards stay open for 30 minutes instead of 10, in the app and in Slack.

Since v0.75.5, once you deny a card the Bot stops and won't retry until you send another message.

Answer with the buttons or a written reply, not an emoji, because the collaboration docs say a reaction alone shouldn't carry a safety-critical decision.

Drafts: leave them on for anything a customer reads

Bots draft outgoing email and Slack messages for review by default, and the draft card shows Needs approval.

In the desktop app you choose Send message on a Slack draft, or Discard to drop it.

Since v0.77.0, Slack drafts show a formatted preview and who the message will notify.

In shared Slack conversations the Bot also checks each post against who can read it.

You can turn drafts off for one Bot with Disable drafts for Bot, and after that its sends follow your Auto Review settings.

My rule is simple: drafts stay on for client channels, and come off only for internal status posts.

Set up a Slack-triggered routine the narrow way

A routine can start when the Bot is mentioned, when a word or phrase is mentioned, when you react to a message, or on any message.

It can watch one channel or all of Slack, and When to run spells the trigger out in words.

Connect Slack on the Cursor account that owns the Bot before you rely on it, because Cursor account integrations start these routines.

Here's the shape of trigger I'd ask the Bot for:

When a message in #support-triage contains a ticket link and the phrase "needs repro",
open the ticket, reproduce the problem in staging, and reply in this thread with the
repro steps as a draft. Never post outside this thread without my approval.

Since v0.77.0, Slack routines that listen for messages also see images on the message that started them, so a screenshot in the bug report reaches the Bot.

Since v0.75.5, a Team Bot whose routine replied in a thread follows that thread and answers later replies without a fresh @mention.

Since v0.78.1, a Team Bot routine that needs one of your connectors asks in the routine's Slack thread and tags you.

Hit Test to run it now, and remember that only new messages count, so anything posted before the trigger existed never starts a run.

📞 Not sure which Slack channel deserves a trigger first? Book a free SEO strategy session and my team will look at your channels with you and pick the ones worth automating. → Book your free call

Rate limits and usage you will hit on a busy channel

Since v0.75.5, all your routines together can run up to 300 times an hour, and each routine up to 200 times an hour.

Go past either limit and the run fails with Automation run rate limit exceeded.

Every run costs usage, and xAI's own routine notes say one chatty-channel trigger can eat seven days of allowance in a single day.

A shared Bot reply draws on the usage of the person it's answering, in Slack as everywhere else.

Owner usage picks up the owner's own chats and any Slack post coming from an app or workflow with no Cursor account behind it.

The fix for a fast-draining allowance is always the same: narrow the channel, narrow the phrase, and pause routines nobody reads.

Handoffs: when one Slack mention reaches several Bots

Bot	Where you ask	Can it hand off?	Where the reply lands
Personal Bot	Your own Slack DM with it	Yes	The app chat, not Slack
Personal Bot	A Slack channel thread	No	The Bot says it can't do that
Shared Bot	A channel thread or Slack DM	Yes, to the asker's own Bots	The same Slack thread

That table comes straight from the handoff section of the docs.

The lesson for operators: if channel requests should fan out to specialist Bots, the front door must be a shared Bot.

Since v0.77.0, teammates in a DM with a Team Bot can also have it message other Team Bots.

Computers, privacy and who sees which chat

Each person's chat with a shared Bot is private, and the owner and Managers can't read it.

When you DM a shared Bot in Slack, it works on your own Grok Bot computer.

In Slack channels, threads, group DMs and group chats, it uses one shared computer of its own.

In those shared spaces it uses only its owner's apps, and asks before touching your accounts.

Bots record who asked for each message they post in Slack, so anyone in the thread can ask who requested it.

Gotchas worth checking before the team announcement

The Settings label changed. The v0.61.0 notes say Settings > General > Team Bots, today's docs say Settings > General > Shared Bots, and since v0.78.1 the admin page says "Shared Bots" too.
Since v0.75.8, a Bot posting to Slack for you from a routine doesn't notify your phone, so check the thread instead of waiting for a buzz.
v0.75.8 lets a Team Bot's routines read any channel where both you and the Bot are members, so keep it out of channels it shouldn't summarize.
Also since v0.75.8, people not on a Team Bot's share list, teammates included, have no access until an owner shares it.
Deleting a shared Bot removes its Slack app for the whole team and can't be undone, per the teams and enterprises docs.
Approval requests and Slack drafts don't appear in Grok Bot group chats, so handle them in your own chat or the Slack thread.

Your rollout checklist, in order

Create the Bot and trim its apps, secrets and files.
Share it with the team or a named group.
Choose Bring to your team's Slack, then Connect, and clear admin approval.
Get every teammate to link under Settings > General > Shared Bots.
Invite it to one channel and run a harmless test mention.
Add one narrow routine and run Test.
After a week, open your Weekly usage limit and pause anything noisy.

Want the same discipline across every agent you run, not just this one?

Join the AI Profit Boardroom for the trainings, the Agent OS and the live calls where members walk through setups like this.

Also On Our Network

FAQ: Grok Bot Slack

Who can add a shared Grok Bot to Slack?

The owner or a Manager adds it after the Bot is shared, using Bring to your team's Slack and Connect. If it shows Awaiting admin approval, a Slack workspace admin has to approve the app.

Why does the Bot tell a teammate to link their account?

Each teammate must link Slack under Settings > General > Shared Bots. Until they do, some features are limited and the owner's logins and private data stay off limits.

Can a Slack trigger watch every channel?

Yes, a trigger can watch one channel or all of Slack. The docs advise keeping the channel and phrase narrow, because broad triggers run often and spend usage.

What happens if I deny an approval card in Slack?

Since v0.75.5 the Bot stops and doesn't retry until you send another message. Only the person who asked can answer a Review an action card in a thread.

Why doesn't my phone buzz when a routine posts to Slack?

Since v0.75.8, when a Bot posts to Slack for you, for example from a routine, your phone isn't notified. Check the thread directly.

📺 Video notes + links to the tools 👉

🎥 Learn how I make these videos 👉

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

About Julian

I'm Julian Goldie, an SEO entrepreneur, author and founder of the AI Profit Boardroom, which has 3,400+ members.

I help business owners scale with AI agents, automation and SEO.

I've built a 7-figure SEO and link building agency, Goldie Agency, with a team of 70+ SEO experts.
I've grown a YouTube channel to 400,000+ subscribers.
I wrote "Link Building Mastery".
My Udemy courses have taught over 29,000 students.

→ Get my best AI training inside the AI Profit Boardroom

Share the Bot, connect it, get every account linked and keep each trigger narrow, then book a free SEO strategy session if you want help planning your grok bot slack rollout.