Grok Bot and Slack: plugin, triggers and Team Bots

Slack works with Grok Bot in three ways: a plugin that lets a Bot read and post as you, a trigger that starts a routine when a message arrives, and a Team Bot that joins Slack under its own name. Start with the plugin, and keep every post behind your click.

#Three ways Slack and Grok Bot work together

The three connect in different places, and only one of them gives a Bot a name of its own in Slack. The drawing shows which way the work flows in each.

Pick by what you want the Bot to do:

#Connect Slack

Slack takes up to two connections. The plugin is the one every job needs, and the Cursor app is the extra one for a routine that starts from a message. Connect plugins covers how plugins work in general.

The plugin belongs to your account, so every Bot you have can now read and post in that workspace.

#Four jobs to hand over

Each of these reads or drafts, and none of them posts. Add one rule first, so a Bot that does try to post has to ask: in Settings, under Custom Rules, type post a message in Slack beside When Grok Bot wants to:, set It should: to Ask first and click Add Rule. Write a rule of your own shows the screen.

Then paste a message into a Bot's chat and change the parts in brackets. Start with the one that saves a scroll every morning.

Set up a routine: every weekday at 8:30 AM, read what was posted in #[channel] since your last run. Post one summary in this chat with three lists: decisions made, questions still open, and anything addressed to me. Say who wrote each item. Don't post, reply or react in Slack.

The second job is the one that writes in Slack, so it ends in a card.

A job to hand over

Reply drafts that wait for you

For the threads where someone is waiting on you.

Apps it needsSlack

Rule to setAsk first: post a message in Slack

PromptCopy

Find today's messages in #[channel] that mention me. For each one, write a reply in its thread, in the way I usually write in Slack, and show it to me as a draft. Post nothing: I'll send each one myself.

You get back

One Slack message card for each reply. Edit it in the card, then click Send message or Discard.

Marker 1Marker 2Marker 3

1. 1Ready to send means the message is still waiting for you.
2. 2Where it will go: the workspace, the person or channel, and the thread. New message starts a new one.
3. 3Nothing is posted until you click Send message.

The next two open with a click. The first runs once a week.

Set up a routine: every Friday at 4:00 PM, read #[channel] for the past seven days. Post a digest in this chat of the decisions the team made: what was decided, who decided it and on which day. End with the questions nobody answered. Don't post anything in Slack.

The last job starts from a Slack message instead of a clock, so every matching message is a run. A Slack trigger on a busy channel can use a week of usage in a day: keep it to one channel and one word. When your usage runs out has what to do if a week drains anyway.

Set up a routine: when a new message in #[channel] mentions the word "[word]", tell me about it in this chat in two lines: who wrote it and what they need. Then suggest a reply I could send. Don't post anything in Slack.

#What a Bot can and can't do in Slack

Everything the plugin does, it does as the Slack user you signed in with. Here is a post a Bot made through it, as the rest of the channel sees it.

Marker 1Marker 2

1. 1The post sits under the person's own name and picture (blurred here), not under a Bot's.
2. 2The footer Sent using @Cursor shows that a Bot sent it.

So the plugin's limits are your own limits in Slack, plus a few of its own.

#A Team Bot in a channel

A Team Bot is one Bot a whole team shares, on Cursor Teams and Enterprise. Once its owner has published it, it can join Slack as an app of its own, with the Bot's name and picture, and it posts as itself.

Its owner adds it, on a computer. Click the Bot's name at the top of its chat, scroll to the bottom of Details and click Bring to your team's Slack.

Where a message is sent decides whether the Bot answers:

Three things to know before a teammate's first message:

• Link your Slack account once. Open Settings > General > Team Bots and click Link. Until you do, the Bot answers you with a private Link Account button.
• You spend your own usage. Whoever asks pays for the answer. A post from a Slack workflow has no person behind it, so it spends the owner's. Whose usage a request spends has the picture.
• A channel thread isn't private. In channels the Bot works on one computer of its own, shared by every thread, so keep out of a thread anything the whole channel shouldn't see.

Grok Bot for teams covers creating a Team Bot, publishing it and who can change it.

#Fix a Slack connection

When Slack and a Bot stop working together, the cause is usually one of these. Find what you see on the left, then do what's beside it.

#Check you've got it

Five jobs, three ways to connect. Put each job where it belongs.

Next, see how a schedule or a trigger is set, checked and paused.

1. 6 October 2026
   First published.