Hermes Agent Slack Setup: Socket Mode in Minutes

What do you need before connecting Slack?

You need a Slack workspace where you can install apps, permission to create a Slack app, and an active Hermes Agent plan. With Socket Mode you do not need a public URL, a reverse proxy, or a VPS.

Choose whether the assistant should serve one workspace or several. A single dedicated Slack app per workspace keeps token rotation, scope review, and audit trails much simpler.

Why use Socket Mode instead of a request URL?

Socket Mode opens an outbound WebSocket from the agent to Slack, so Slack never has to reach your infrastructure. That removes the need for a public HTTPS endpoint and inbound firewall rules.

• No public request URL, tunnel, or ngrok process to maintain.
• Works behind NAT and on hosts without inbound ports.
• Reconnects automatically when the network drops.
• Requires an app-level token with connections:write in addition to the bot token.

Which Slack scopes does the assistant need?

Start with the smallest set that covers reading mentions and posting replies, then add history scopes only for channels the assistant must summarize. Extra scopes widen the blast radius if a token leaks.

• app_mentions:read to receive mentions in channels.
• chat:write to post replies as the app.
• channels:history and groups:history only when the assistant reads context.
• im:history only when the assistant must answer direct messages.

Why does the Slack bot stay silent?

The usual causes are a bot that was never invited to the channel, a missing scope added after install, an app-level token that is missing or expired, or a deployment that has not finished becoming ready.

• Invite the bot with /invite before expecting a reply in a channel.
• Reinstall the app after changing scopes, then redeploy with the current token.
• Confirm the deployment status is running rather than provisioning or failed.
• Test in a private channel before debugging threads, topics, or shared channels.

How should you roll Slack out to a whole workspace?

Prove one private channel first, then expand to a small pilot group, and only then invite the bot into high-traffic channels. Keep an approval rule for anything the assistant can post publicly.

Slack conversations are visible to colleagues immediately, which makes a bad reply more expensive than in a private chat. Start read-only in busy channels and enable posting after the replies look consistently useful.