How to Connect Slack
Connect your Slack workspace to CRHQ. Install the bot for team automation, link your personal account for agent-as-you access, or set up a custom branded app.
Overview
CRHQ connects to Slack in two ways — and you can use one or both:
| Mode | What It Does | How to Talk to It |
|---|---|---|
| Bot | An always-on bot that lives in your workspace. Team members @mention it in channels or DM it directly. | @Operator what's our MRR? |
| Personal | Links your personal Slack account so agents can read and act as you. | Ask your agent: "check my Slack DMs" |
Both connections are managed from a single place: Settings > Connectors > Slack.
The Slack Connector
When you open the Slack connector, you'll see a modal with three tabs:
- Bot — Install and manage the workspace bot
- Personal — Connect your personal Slack account
- App — Configure which Slack app to use (CRHQ default or your own custom app)
Connect the Bot
1. Open the Slack Connector
Navigate to Settings > Connectors and find the Slack card. Click Manage (or Connect if nothing is connected yet).
2. Go to the Bot Tab
Select the Bot tab if it's not already selected.
3. Install to Your Workspace
Click Install Bot to Workspace. Slack will open an authorization window showing the permissions the bot needs. Select your workspace and click Allow.
4. Verify
Back in CRHQ, the Bot tab should show a green "Bot is running" indicator with your workspace name.
Using the Bot
Invite the Bot to Channels
The bot can only see messages in channels it's been added to.
- Open the Slack channel
- Type
/invite @Operator(or whatever your bot is named) - The bot joins and starts listening
Talk to the Bot
- @mention in a channel —
@Operator summarize today's discussion. The bot replies in a thread. - Direct message — Open a DM with the bot and type your request. No @mention needed.
The bot sends a "Working on it..." indicator, processes through your chosen agent, then posts the full response.
Threaded Conversations
All replies happen in threads. Continue the conversation by replying in the same thread — the bot keeps context across the entire thread.
Configure the Bot
Choose Which Agent Responds
In the Bot tab, use the Agent dropdown to pick which CRHQ agent handles incoming Slack messages. Default is Operator, but you can switch to any agent on your satellite.
Customize Appearance
Set a custom Display Name and Icon URL for the bot's message posts. This changes the name shown on replies, but the @mention name is set by the Slack app itself.
Tip: Want full control over the @mention name too? See Creating a Custom Slack App.
Connect Your Personal Account
The Personal tab lets you link your own Slack identity. Once connected, agents can read your channels, search your messages, and send messages as you — not as the bot.
For a full guide, see How to Connect Personal Slack.
Use a Custom App
By default, satellites use the shared CRHQ Slack app. If you want your bot to have a custom name (like @Aria or @TeamBot), you can create your own Slack app and enter its credentials in the App tab.
For a step-by-step guide, see Creating a Custom Slack App.
Disconnecting
Disconnect the Bot
In the Bot tab, click Disconnect Bot. The bot stops immediately. Your Slack workspace retains the app installation — you can reconnect anytime without re-authorizing.
Disconnect Personal
In the Personal tab, click Disconnect. The stored personal token is deleted from your server.
Remove from Slack Entirely
To fully remove the app from your workspace, go to your Slack workspace Settings > Manage Apps and uninstall it.
Troubleshooting
Bot shows "stopped" after connecting
The bot credentials were stored but the process failed to start. Try disconnecting and reconnecting.
Bot doesn't respond to @mentions
- The bot must be invited to the channel — it can't see messages in channels it hasn't joined
- Make sure you're @mentioning the correct name (the Slack app name, not the display name)
- Check that the bot status shows "running" in the Bot tab
Bot responds with errors
The message reached the bot but the agent couldn't process it. Common causes:
- The configured agent doesn't have model access (check API keys)
- The agent's Anthropic/OpenAI API key is missing or expired
- Claude CLI isn't properly configured on the satellite
I can't install the bot
If Slack says "This app can't be installed", your Slack workspace admin may need to approve the app first. Check Manage Apps in your workspace settings.
Security & Privacy
What can the bot access?
The bot can only see messages in channels where it's been explicitly invited. It cannot read other users' DMs, private channels it hasn't joined, or messages from before it joined.
How are credentials stored?
All Slack tokens (bot xoxb- and personal xoxp-) are encrypted with AES-256-GCM on your dedicated satellite server. Tokens never leave your server. The bot connects directly to Slack via Socket Mode (WebSocket) — no webhooks or public URLs are exposed.
Can I revoke access?
Yes, at any time:
- From CRHQ: Disconnect in Settings > Connectors > Slack
- From Slack: Go to your workspace's Manage Apps and remove the app