Overview
The Slack Agent (Slack Router) lets your team interact with BrightAgent directly from Slack. Ask data questions, create Jira tickets, search Notion docs, find Google Drive files, and more — all without leaving your messaging workspace. A fast intent classifier routes each message to the right backend.What You Can Ask in Slack
- “Show me our top customers by revenue” — Routes to BrightAgent for data queries
- “Create a Jira ticket for the data pipeline bug” — Routes to Jira via MCP
- “Find the doc about our onboarding process” — Routes to Notion via MCP
- “Search for the Q4 report in Drive” — Routes to Google Drive via MCP
- “What is the difference between a data lake and a warehouse?” — Routes to general chat
How It Works
- Message arrives from Slack — User sends a message in a connected Slack channel or DM.
- Intent classification — A fast LLM classifier determines what the user needs and routes to the right backend.
- Backend processes the request — Data questions go to the BrightAgent. Tool requests go to MCP-powered integrations. General questions get a direct chat response.
- Response sent back to Slack — Results are formatted for Slack and posted as a reply.
Supported Integrations
BrightAgent Platform
Full data platform access — query data, run analysis, generate visualizations, check data quality — all from Slack.
Jira
Create tickets, check sprint status, view your issues, and manage project tracking via MCP.
Notion
Search pages, create documents, and browse your team’s wiki and knowledge base via MCP.
Google Drive
Find files, list folders, and access shared documents via MCP.
Architecture
- Intent Classifier — Uses Claude Haiku for fast (~130ms) intent classification.
- MCP Tool Execution — Uses the ReAct pattern for multi-step tool calls against external services.
- General Chat — Powered by Amazon Bedrock Nova for quick conversational responses.
- Workspace Mapping — Each Slack workspace maps to a Brighthive workspace for proper authentication and data isolation.