Channels
Slack.
Connect a agent to one or more Slack workspaces. The agent answers mentions, DMs, and threads using the same tools and knowledge it has on the web embed.
Capabilities
What you'll get
- The agent replies to
@mentionsin any channel it's been invited to - Direct messages to the bot work end-to-end
- Threaded replies stay in the same thread for context continuity
- Reactions can be wired into your tools
Before you start
Prerequisites
- A Slack workspace where you have permission to install apps
- A agent already created in the Onpilot dashboard
OAuth install
Connect
- Open the agent in the Onpilot dashboard
- Go to the Publish tab
- Click the Slack tile → Connect
- Approve the OAuth consent in Slack
- You're redirected back with the workspace connected — the agent is live
What we ask for
Scopes
The standard install requests these scopes:
| Scope | Why |
|---|---|
chat:write | Post replies |
channels:history | Read public channel messages it's mentioned in |
groups:history | Read private channel messages it's mentioned in |
im:history | Read direct messages |
app_mentions:read | Detect when it's mentioned |
users:read | Resolve user names from IDs |
reactions:write | Add reactions to messages |
Some configurations request a wider set (read public channels, write to DMs, customize bot identity). The dashboard install flow asks for exactly what your agent needs.
Slack-side step
Inviting the bot to channels
Slack workspaces require explicit /invite @your-bot in each channel before the bot can read or write. Without the invite, the bot only responds in DMs and channels it's already been added to.
Common issues
Troubleshooting
"missing_scope" errors after a Slack permission change.
Slack revoked a scope when an admin tightened permissions. Reinstall from the dashboard's Publish tab — re-installing requests the full set again.
Bot doesn't reply when mentioned in a channel.
Run /invite @your-bot in the channel. Slack workspaces require explicit channel-level invites.
Same workspace, two agents.
Each agent has its own install flow. Run the connect flow twice — once per agent. They show up as separate apps in Slack's app list.
Token rotation.
If a Slack admin force-rotates your bot tokens, the next request fails silently. Reinstall to mint fresh tokens.