Slack
Connect a Slack bot to Connic. Trigger agents from mentions or send agent outputs to Slack channels.
Overview
Create the Slack app from a generated manifest, choose its workspace, name, icon, and channel membership, then save it as a reusable Connic connection.
Connic generates the app manifest and Events API request URL. Create the app in Slack, then copy two secrets into Connic: its Signing Secret and Bot User OAuth Token. Inbound mentions trigger linked agents; outbound connectors reply to the originating thread or deliver agent output to a Slack channel.
How it works
Create a Slack connection
Install Slack from the connector marketplace and create a reusable Slack connection for the workspace app.
Create the app from the manifest
Connic opens Slack with a generated manifest containing the Events request URL, app_mention event, and five required bot scopes. Choose the workspace, create the app, and upload the app icon.
Verify the app
Copy the app's Signing Secret into Connic. Verify the Events request URL from Slack's App Manifest page, install the app to the workspace, then paste the xoxb- Bot User OAuth Token.
Choose a connector mode
Use inbound mode for app mentions or outbound mode to reply to Slack context, use an output channel_id, or use an optional default channel.
Production patterns
Patterns teams ship in production, with Connic running the queues, workers, and schedulers.
A teammate mentions the bot with a question
app_mentionThe agent searches its connected knowledge sources and posts a concise answer in the mention thread without reading the rest of the channel.
A teammate mentions the bot with a question
app_mentionThe agent searches its connected knowledge sources and posts a concise answer in the mention thread without reading the rest of the channel.
An engineer mentions the bot with an alert or error
app_mentionThe agent checks its assigned tools, identifies likely causes, and returns the next diagnostic steps in the same Slack thread.
An engineer mentions the bot with an alert or error
app_mentionThe agent checks its assigned tools, identifies likely causes, and returns the next diagnostic steps in the same Slack thread.
A teammate asks for the status of a release
app_mentionThe agent queries the connected delivery systems and replies with the current status, blockers, and owners while keeping the conversation contained to one thread.
A teammate asks for the status of a release
app_mentionThe agent queries the connected delivery systems and replies with the current status, blockers, and owners while keeping the conversation contained to one thread.
A fraud-detection agent flags a risky transaction
agent_completedThe outbound Slack connector posts the transaction, risk signals, and recommended action to #fraud-alerts without waiting for a Slack mention.
A fraud-detection agent flags a risky transaction
agent_completedThe outbound Slack connector posts the transaction, risk signals, and recommended action to #fraud-alerts without waiting for a Slack mention.
One reusable Slack connection
The Slack app is created inside the customer's Slack account from a generated manifest. They control its branding, workspace installation, channel membership, and removal. Connic provides the agent runtime and event endpoint behind it, with the app description identifying the bot as powered by Connic.
Reuse the verified connection across inbound and outbound Slack connectors, and link each connector to one or more agents.
Minimal Slack access
The generated manifest requests only app_mentions:read and chat:write for mention handling and delivery, plus channels:read and groups:read to list metadata for public and private channels the bot has joined, plus reactions:write to add the 👀 acknowledgement after successful dispatch.
It does not request channel history, direct-message, file, user-profile, or broad public-channel posting access. The Signing Secret and bot token are encrypted after saving. Connic verifies Slack's request signature and timestamp before an event can reach the linked agent.
Mentions in, agent outputs out
An app_mention carries the mentioned text plus workspace, channel, user, and thread metadata into the agent run. An explicit channel_id in agent output chooses the destination. Without one, an outbound Slack connector using the same Connection replies in the originating thread; other runs use the optional default channel. There is no background channel reading.
See the complete setup and security model in the Slack docs.
Information
- Publisher
- By Connic
- Connectors
- Connectors
- Modes
- Inbound, Outbound
- Documentation
- Slack docs
Frequently Asked Questions
app_mentions:read and chat:write for mentions and delivery, plus channels:read and groups:read to list metadata for joined public and private channels, and reactions:write for the 👀 acknowledgement. It has no channel-history, direct-message, file, or user-profile scopes.xoxb- Bot User OAuth Token lets Connic validate the installation and send the agent's answer through their Slack bot. Both are encrypted after saving.Bring the event source, payload shape, result destination, and any private-network or approval requirements. We will map Slack to the right Connic connector mode, deployment path, and observability setup.
Talk to Sales