Slack
Overview
The Slack integration lets an ElevenLabs agent send and receive messages in Slack. Once connected, the agent replies in a thread when mentioned in a channel and maintains separate conversation context per thread.
Capabilities
Setup
The integration offers two ways to connect:
- OAuth — install the shared ElevenLabs Slack app into your workspace. A single Slack workspace maps to a single ElevenLabs connection. Fastest setup, no Slack app management required.
- Bring your own app — connect using a Slack app you create and own. Use this when you need the bot to appear under your brand or when your workspace policies require apps to be installed by an admin.
Option A — OAuth
The user installing the app must have permission to add apps to the target Slack workspace.
Open the integrations page
In the ElevenLabs dashboard, go to Agents > Integrations and select Slack.
Option B — Bring your own Slack app
Use this if you want the bot to show up under your own app name and icon, or if your workspace requires apps to be reviewed and installed by your admin.
Create a Slack app
Go to Slack API: Your Apps and click Create New App > From scratch. Name the app and pick the Slack workspace to install it into.
Add bot scopes
Open OAuth & Permissions and add the following Bot Token Scopes:
app_mentions:read, channels:history, channels:join, channels:manage, chat:write, files:read, groups:history, groups:write, im:history, reactions:read, reactions:write.
Then click Install to Workspace and approve. Copy the Bot User OAuth Token (starts with xoxb-).
Create the connection in ElevenLabs
In the ElevenLabs dashboard, go to Integrations, click the Add integration button and choose Slack. Pick the Bring your own app credential. Paste the bot token and signing secret, then save. ElevenLabs verifies the token against Slack and records your workspace id.
After the connection is created, the connection page shows two webhook URLs derived from your Slack app’s identity. The same Slack app, reconnected from the same ElevenLabs workspace, always produces the same URLs — so you can delete and recreate the connection without re-updating your Slack app’s configuration. Keep that page open for the next steps.
Configure Event Subscriptions
In your Slack app, open Event Subscriptions, enable events, and paste the Events URL from the ElevenLabs connection page into Request URL. Slack will verify the URL using the signing secret you provided.
Subscribe to bot events based on how you want the agent to behave in channels:
- Mention-only — subscribe to
app_mention. The agent responds only when a user@-mentions the bot. - All messages — subscribe to
message.channelsandmessage.groups. The agent responds to every message in channels the bot is in, without requiring a mention.
If you use the SlackDirectMessage trigger, also subscribe to message.im. If you use the Reaction trigger, also subscribe to reaction_added.
When a user @-mentions the bot, Slack sends both an app_mention event and a message event for the same message if the app subscribes to both. ElevenLabs collapses the two deliveries into one turn, so subscribing to both is safe, but message.channels and message.groups alone are enough: a mention is also a message.
The Respond to setting on the Channel Message trigger then decides which delivered messages get a reply (see Talking to the bot in Slack).
A Slack workspace can only be connected once via the shared ElevenLabs OAuth app. Reinstalling
from a different ElevenLabs workspace returns a duplicate Slack workspace error — remove the
existing connection first. Bring-your-own-app connections are independent and do not conflict.
OAuth scopes
The ElevenLabs Slack app requests the following scopes:
Agent tools
When you add Slack tools to an agent, the following built-in tools are available:
Removing the connection
Removing the connection from the Integrations page uninstalls the ElevenLabs Slack app from the Slack workspace. After removal, the bot is no longer present in any channel.
For bring-your-own-app connections, ElevenLabs cannot uninstall an app it does not own — removing the connection only deletes the local mapping. To fully remove the bot from your Slack workspace, uninstall the app from your Slack admin settings.
Configure the trigger
The integration exposes a single trigger, SlackMessage. It fires when the bot sees a new user message in a configured channel.
Add a SlackMessage trigger
On your agent’s configuration page, add a new trigger and select SlackMessage.
Slack does not allow apps to auto-join private channels. For a private channel, run /invite @Eleven in that channel after saving the trigger so the bot can see messages.
Only one trigger is allowed per (Slack workspace, channel) pair. Edit the existing trigger
instead of creating a duplicate.
Configure the DM trigger
The SlackDirectMessage trigger lets any Slack user chat with the agent by sending a direct message to the bot. Unlike the channel trigger, no @ mention is needed — every message a user sends in a DM with the bot is processed.
For BYO apps, make sure you have subscribed to the message.im bot event and added the
im:history bot scope. Reinstall the app if prompted after adding these.
Only one DM trigger is allowed per Slack connection. To change the agent, edit the existing trigger.
Configure the Message in Any Channel trigger
The Message in Any Channel trigger covers every channel the bot is a member of, so you don’t need a trigger per channel. Add the app to a channel in Slack and the agent answers there straight away. Remove the app from the channel and the agent stops.
Add a Message in Any Channel trigger
On your agent’s configuration page, add a new trigger and select Message in Any Channel.
Configure the trigger
Pick the Agent, and set Respond to messages from and Respond to as for the Channel Message trigger (see Talking to the bot in Slack).
The trigger only answers in channels that don’t have a trigger of their own. A channel with a Channel Message or support-ticket trigger keeps using that trigger, and other channels are unaffected. Add a Channel Message trigger when one channel needs a different agent or its own Initial Dynamic Variables. If you delete it later, the bot stays in the channel and this trigger takes over again.
The agent gets the channel in the integration__slack_channel_id dynamic variable, so it can look
up which customer or team the channel belongs to. For BYO apps, subscribe to message.channels
and message.groups (or app_mention for mention-only).
Only one Message in Any Channel trigger is allowed per Slack connection. The bot answers in every channel it is in, internal ones included, so only add the app where the agent should respond.
Configure the Reaction trigger
The Reaction trigger starts an agent turn when someone reacts with an emoji to a message in a channel. Use it for actions such as opening a ticket on :ticket:, or logging :+1: feedback on the agent’s replies.
Add a Reaction trigger
On your agent’s configuration page, add a new trigger, select Reaction, and enter the Channel ID. The bot joins the channel.
The agent reads the reacted message’s thread, followed by a user turn such as [<@U123> reacted with :ticket: to the message: "Checkout fails on Safari"]. The turn continues the thread’s conversation, so if the same agent already answered in that thread, it keeps that context. The reply is posted in the thread.
What each emoji does is up to the agent. Name the emoji in its prompt, or branch a workflow on the integration__slack_reaction dynamic variable with an expression condition, and give each branch the tools it needs. An agent that should only acknowledge a reaction can call skip_turn to reply with nothing.
Only people’s reactions start a turn: the bot ignores its own reactions (including the :eyes: it adds while working) and other bots’. A thread paused with @bot stop ignores reactions too.
The ElevenLabs Slack app added the reactions:read scope for this trigger. If your connection was
created before, reconnect it. For BYO apps, add the reactions:read bot scope, subscribe to the
reaction_added bot event, and reinstall the app.
Only one Reaction trigger is allowed per (Slack workspace, channel) pair. It can sit alongside a
Channel Message trigger on the same channel.
Talking to the bot in Slack
Once the trigger is active and the bot is in the channel, start a conversation in a channel thread. Which messages get a reply depends on two things: the events your Slack app delivers (its event subscriptions; the OAuth app delivers mentions only) and the trigger’s Respond to setting, which filters those deliveries:
- Every message Slack delivers: no filtering. With
app_mentiononly this is mention-only; withmessage.channels/message.groupsit answers every message in the channel. - Mentions only: reply only to messages that
@-mention the bot, whatever the app delivers. - Mentions, then the whole thread (default): a mention starts the conversation, and every later message in that thread is answered without a further mention. Messages in threads the bot has not been mentioned in are ignored. Requires your own Slack app subscribed to
message.channels/message.groups, since the follow-ups carry no mention; the shared ElevenLabs Slack app only delivers mentions, so on it this mode behaves like Mentions only.
Triggers created before this setting existed behave as Mentions, then the whole thread. For apps that only subscribe to app_mention nothing changes. If your app subscribes to message.channels / message.groups and you relied on the agent answering every message in the channel, set Every message Slack delivers on the trigger.
Pausing the bot in a thread
Anyone in a thread can tell the bot to stop by mentioning it with nothing but a stop word, for example @Eleven stop. Accepted stop words: stop, stop replying, stop responding, please stop, stop please, mute, quiet, be quiet. The bot reacts with 🔇 and stays silent in that thread, whatever the Respond to setting, until someone mentions it again. The next mention lifts the mute and is answered as usual. A longer message that merely contains “stop” is an ordinary turn.
Mention-only (app_mention)
All messages (message.channels, message.groups)
While the bot is generating a response, it adds a :eyes: reaction to the user’s triggering message and removes it once the reply is posted.
The Respond to messages from setting on the Channel Message trigger controls who can trigger the agent:
- Only humans (default): messages from other bots and from Slack workflows are ignored. This is the safe default and preserves the behavior of existing triggers.
- Humans and bots: messages from other bots and workflow-posted messages (including legacy
bot_messageevents) also trigger the agent.
The bot always ignores its own messages — using the bot-user and app identity in Slack’s signed webhook — under either setting, so it never replies to itself even when self-mentioned. It also continues to ignore edited messages (message_changed) and deleted messages (message_deleted). It handles message and app_mention events and works in both public and private channels.
Legacy bot events that contain only a bot_id identify the sender but not the receiving app. They
are treated as messages from another bot; self-loop detection for this Slack app uses the bot-user
or app identity included in modern Slack event payloads.
If your Slack app subscribes to both app_mention and message.channels / message.groups, a
single @-mention arrives twice. Only the first delivery becomes a turn, so the bot replies once.
Conversation model
The conversation ID is deterministic per (agent_id, channel_id, thread_ts):
- A new Slack thread maps to a new ElevenLabs conversation.
- Continuing the same thread continues the same conversation, including transcript history and dynamic variables.
When constructing chat history, the bot reads the Slack thread directly. Messages from Slack members and other bots are treated as user turns, while the bot’s own messages are treated as agent turns. Mentions of the bot user (<@BOT_USER_ID>) are rewritten to @<agent_name> before the agent processes them.
Dynamic variables
When an agent runs from Slack, the following dynamic variables are available in prompts and tools:
See dynamic variables for how to reference these in prompts and tool calls.
Troubleshooting
File attachments not working
When a user attaches an image or PDF in Slack but the agent does not process it (or behaves as if no file was sent), work through the checks below.
Confirm the Slack app has files:read
The bot needs the files:read bot scope to download attachments from Slack.
- Bring your own app — open your app at Slack API: Your Apps, go to OAuth & Permissions, and verify
files:readis listed under Bot Token Scopes. If you added it recently, reinstall the app to your workspace so the token picks up the new scope.
Confirm the agent model supports file input
File attachments are only forwarded when the agent’s LLM supports multimodal input — image input and/or document (PDF) input, depending on the file type. In the agent configuration, open the Agent tab and check the selected model. If the model does not support the attachment type, switch to a model that does.