Slack
Connect your Slack bot to Connic. Trigger agents from mentions or send agent outputs to Slack channels.
On this page
app_mention event triggers every agent linked to the connector. Inbound mode does not deliver agent output by itself.How It Works
Slack signs each Events API request. Connic verifies the signature and timestamp, removes the bot mention from the text, starts linked agents with workspace, channel, user, and thread metadata, then adds 👀 to the Slack message after dispatch succeeds.
To reply automatically, link the agent to an outbound Slack connector that uses the same Connection. Connic then returns that run's output to the originating Slack thread.
Setup Instructions
Create a Slack connection
Install Slack from the connector marketplace, choose Create Slack connection, name the app, and create the connection.
Create and verify the Slack app
Open the generated manifest in Slack, save the Signing Secret in Connic, then verify the Events request URL from Slack's App Manifest page. Connic detects Slack's signed verification request automatically.
Install the app
Install the app to the workspace and save its xoxb- Bot User OAuth Token in Connic.
Create and link the connector
Select Inbound mode, choose the verified Slack connection, create the connector, and link one or more agents. Invite the bot to each channel where mentions should trigger runs.
Agent Input Payload
{
"text": "Can you summarize today's incidents?",
"user_id": "U01234567",
"team_id": "T01234567",
"channel_id": "C01234567",
"thread_ts": "1724418000.123456",
"event_id": "Ev01234567"
}Example Agent
version: "1.0"
name: slack-assistant
type: llm
model: connic/gpt-5.6-terra
description: Answers questions from Slack mentions.
system_prompt: |
Answer Slack questions clearly and concisely.
# input["text"] contains the mention text.
# A linked outbound Slack connector using the same Connection
# returns output to the originating thread.How It Works
Automatic outbound connectors send a completed run's final output and can be limited to selected inputs. Agent-tool and middleware outbound connectors send only when called. Connic owns Slack formatting, routing, credentials, rate-limit handling, and retries.
Setup Instructions
Invite the bot
Invite the installed app to every public or private channel you want to use as an outbound destination.
Create an outbound connector
Choose Outbound mode and the Slack connection. Optionally select a default channel from the channels that bot has joined, then create the connector.
Link agents
Link every agent whose completed output should be delivered through this Slack connector.
Agent-tool and Middleware Outbound Connectors
An agent-tool outbound connector exposes an editable tool name, defaulting to send_to_<connector_name>. Call a middleware outbound connector by its configured name through send_connector. Both use the payload schema below. text is required; channel_id and thread_ts are optional.
{
"text": "Daily incident review complete: 3 resolved, 1 monitoring.",
"channel_id": "C01234567",
"thread_ts": "1724418000.123456"
}An explicit route wins. Otherwise, matching inbound and outbound connectors using the same Slack Connection reply in the originating thread, then the connector uses its optional default channel. Stored channel and connection values are not exposed to the model.
Automatic Output Format
{
"text": "Daily incident review complete: 3 resolved, 1 monitoring.",
"channel_id": "C01234567",
"thread_ts": "1724418000.123456"
}Existing links without outbound connector settings remain Automatic / All runs. A plain final response is sent as text; JSON may use text, message, or body, plus the optional route fields above.
- Incoming requests use Slack signing-secret verification and replay protection.
- Signing secrets and bot tokens are encrypted and masked after saving.
- Slack only accepts outbound destinations that the customer bot is allowed to post to.
- The same verified connection can be reused by multiple connectors and agents.