CoAgentorSlack
Connecting Slack lets your silent agents deliver real-time trigger insights and post-meeting summaries directly to your Slack workspace — as a DM to a specific user, or as a message in a channel.
What CoAgentor posts to Slack
When a trigger fires on an agent configured to deliver to Slack, CoAgentor posts a formatted message containing:
- The trigger label (e.g. "Competitor mentioned")
- The transcript snippet that triggered the response
- The agent's response text
- The meeting name and timestamp
Post-meeting summaries sent to Slack contain the full event log for the meeting.
XXX SCREENSHOT: A CoAgentor Slack DM message showing a formatted trigger event — with the trigger label in bold, the transcript context in a quoted block, and the agent response below it
Connecting your workspace
- Go to Integrations → and click the Back Channel Comms tab
- Click Connect Slack
- You'll be redirected to Slack's OAuth consent screen — authorise CoAgentor for your workspace
- After authorising, you'll be redirected back. The workspace will appear with an Active badge.
XXX SCREENSHOT: The Slack connection card in the Back Channel Comms tab — showing the pre-connection state with the "Connect Slack" button, and the post-connection state showing the workspace name and Active badge
Connecting multiple workspaces
On Solo and Pro plans, you can connect more than one Slack workspace. Each connection is independent — agents can be configured to deliver to any connected workspace.
| Plan | Max Slack workspace connections | |---|---| | Free | 1 | | Solo | 2 | | Pro | Unlimited | | Business+ | Unlimited |
Configuring an agent to deliver to Slack
Once Slack is connected, open any agent in the Agent Builder and set the back-channel destination to Slack.
You'll then select:
- Workspace — which connected Slack workspace to post to
- DM or Channel — deliver as a direct message to a user, or post to a channel
- Target — the specific user or channel
XXX SCREENSHOT: The Back Channel section of the Agent Form with Slack selected as the destination, showing the workspace selector, DM/Channel toggle, and the user/channel picker populated
The same picker is available for both the live back-channel (per-trigger delivery) and the post-meeting summary channel.
DM vs Channel delivery
DM delivery — messages are sent as a direct message from the CoAgentor bot to the selected Slack user. Best for private monitoring (e.g. a manager monitoring a rep's call).
Channel delivery — messages are posted to the selected channel. Best for team visibility (e.g. a sales team channel where the whole team can see objection responses as they happen).
The CoAgentor bot must be a member of any channel it posts to. If it's not yet a member, invite it by typing /invite @CoAgentor in the channel.
Per-trigger Slack routing
Individual trigger rules can have their own Slack destination, independent of the agent's default back-channel. This lets you route critical triggers (e.g. "Contract terms mentioned") to a specific channel while routing lower-priority triggers to a general inbox.
Set this in the Trigger Rule Builder by selecting Silent as the action type and choosing a Slack target for that specific rule.
Connecting multiple workspaces for multi-team setups
If your agents serve multiple teams across different Slack workspaces, you can connect each workspace separately and configure different agents to post to different workspaces. Each connection uses its own OAuth token and is managed independently.
Disconnecting
- Go to Integrations →
- Click the Back Channel Comms tab
- Click Disconnect on the Slack connection
Disconnecting Slack will prevent future messages from being posted, but does not affect your meeting history or event logs in CoAgentor.
Troubleshooting
Messages aren't appearing in my channel — Ensure the CoAgentor bot has been invited to the channel (/invite @CoAgentor). Check that the agent is configured to deliver to that channel and the connection is Active.
DMs aren't arriving — Confirm the correct Slack user is selected in the agent configuration. If the user has DMs from apps disabled, they may not receive messages from the bot.
My workspace connection shows an error — Slack OAuth tokens can expire if permissions are changed or the app is removed from the workspace. Try disconnecting and reconnecting.