Slack Integration
DevBoy tools provide integration with Slack for searching chat history, fetching messages, and posting structured notifications through AI assistants. Slack is the first provider in the Messenger category.
Authentication
Slack uses an OAuth-issued bot token (Bot User OAuth Token, xoxb-…):
The bot needs the following OAuth scopes — devboy doctor will tell you which ones are missing:
You can list extra required scopes via slack.required_scopes in config (the doctor check enforces them).
Configuration
Basic configuration
Configuration file
~/.config/devboy-tools/config.toml:
Environment variables
Available tools
The Slack provider implements the Messenger category. The same four tools are exposed for any Messenger-class provider; this page documents the shape against Slack.
get_messenger_chats
List channels / DMs visible to the bot.
get_chat_messages
Fetch recent messages from one chat.
search_chat_messages
Full-text search across messages the bot can see.
send_message
Post a message to a channel / DM.
Doctor check
Verifies:
- The bot token authenticates against
auth.test. - All scopes listed in
slack.required_scopesare present on the token. - Reports the missing scopes in the diagnostic output if any.
Use cases
- Daily summary —
chat-summaryskill summarises the last 24 h of a channel for a stand-up note. - Notification —
notifyposts a structured message after a long-running CI / deploy. - Decision archaeology —
chat-searchlets the agent grep team channels for "why did we choose Postgres over MySQL".
API reference
- Endpoint:
https://slack.com/api - Protocol: HTTPS / JSON
- Rate limits: Slack's tier-based rate limits — typically 50–100 calls/minute per method.
- Documentation: Slack Web API methods