Grok Bot + Slack

How a Bot connects

Slack connector; Bot user with scopes for the channels it needs. Event triggers (a mention, a new message in a channel) can start routines.

The Bot's identity

A Slack bot user or a real user seat named for the Bot; invited only to its channels. Don't reuse a human's login. If you did, see shared computer cleanup.

Routines we've run

• On mention — the Bot's intake: someone @mentions it with a request; it files it and acknowledges
• Daily 08:00 — the morning message: approvals waiting, routine health, spend, yesterday's outputs
• On new message in #support-escalations — summarise the thread and draft a response for the on-call human

Each routine follows the four-part shape: when it runs, what it reads (bounded), what it produces, when it stops. See routines best practices.

The thing to gate

DMing customers in Slack Connect channels, and reading channels it shouldn't. Invite narrowly.

Verdict

Slack is where Bot output should land. If your team lives in Slack, every other integration's output gets routed here.

Setup notes

• Test every routine supervised until it's produced the right output three times.
• Add the routine's completion line to your heartbeat log so silent failures show up.
• Put the Slack token in the Bot's connector settings or knowledge file, never in a chat message.