💬 Chat Hub
Communications — Complete Guide
Legacy channel routing surface (Slack/Discord). Hidden from nav — not under active product development.
Sign in required
This guide covers in-app features. Sign in or create an account to follow along in your workspace.
Updated July 19, 2026
5 min read
⚠️
Frozen surface. Communications is hidden from the main sidebar and not receiving new features (scope freeze). Prefer Chat Hub for operator sessions and Slack/Discord inbound Swarm triggers for production channel automation. This guide remains for teams that still deep-link to /communications.
Open Communications from the sidebar. Legacy channel routing surface (Slack/Discord). Hidden from nav — not under active product development.
What you can do
- Legacy: route Slack/Discord channels (where still enabled for your workspace)
- Inbound Swarm triggers remain available via Integrations + Swarm — not this UI
- Outbound approval patterns — prefer Swarm Approvals nodes going forward
- No new channel types or product investment on this surface
Step-by-step — start to finish
1
Prefer Chat Hub for talking to agents, and Integrations for OAuth.
2
If you still use /communications via bookmark, connect Slack/Discord under Integrations first.
3
For new work, configure inbound triggers on Swarm (webhook/Slack/Discord) instead of expanding Communications.
4
Gate customer-facing posts with Swarm Approval nodes or the Approvals queue.
5
Do not plan new product features on Communications — it is frozen.
Get value from Communications
💡
Active path: Chat Hub + Integrations + Swarm inbound. Communications docs stay for legacy access only.
Go deeper
Was this helpful?