Slack Bot
In one line: Create a Slack bot named after your chatbot, drop it into your workspace, and let it answer when someone mentions it in a channel or messages it directly.
This is not the Slack connector. That one gives an agent tools — send a message, read channels — as steps inside a workflow. This page is about deploying a chatbot into Slack so people can talk to it. They’re independent: you can use either, or both.
1. Overview
Slack Bot creates a real Slack app in your workspace, named after your chatbot, and wires it to UnleashX. From then on the bot listens for two things: @mentions in a channel and direct messages. Either one is passed to your chatbot, and the answer is posted back — in-thread when it was a mention. The bot is created from a Slack App Configuration Token you generate once. UnleashX uses it a single time to build the app, then the app runs on its own credentials. Connecting Slack this way means your chatbot lives where your team already works — no new window, no portal to log into, just@yourbot in the channel where the question came up.
2. What you’ll need
- A Slack workspace you can sign in to and install an app on.
- A chatbot (or agent) in UnleashX with Slack selected as one of its channels.
- A Slack App Configuration Token, generated in Section 3.
An agent has one Slack bot at a time. Creating a new one replaces the current bot, which you can reconnect later.
3. Get your Slack App Configuration Token
These are the steps exactly as they appear in the Slack setup dialog:1
Open api.slack.com/apps
Open api.slack.com/apps and sign in to your workspace.
2
Generate a token
Scroll to Your App Configuration Tokens and click Generate Token.
3
Copy the access token
Pick your workspace, click Generate, and copy the Access Token (starts with
xoxe.xoxp-).4
Paste it into UnleashX
Paste it below and click Connect Slack. The token lasts 12 hours and is used only once to create the bot.
Because the token is used only once, at creation, it doesn’t need to be stored or rotated. It expires by itself after 12 hours. If setup fails and the token has gone stale, just generate a fresh one and start again.
4. Connect on UnleashX
1
Open the Deploy step
Open your chatbot in UnleashX and go to the Deploy step.
2
Expand Slack
Find the Slack section — “Connect Slack to reply to messages in your workspace with this chatbot.” It shows Setup required until it’s connected.
3
Click Connect Slack
This opens the Slack setup dialog.
4
Name the bot and paste the token
Fill in the two fields:
Then click Connect Slack.
5
Approve the install in Slack
A Slack window opens. Click Allow to install the bot into your workspace.
6
Choose channels
Once it connects, pick the public channels for the bot to join — or Skip and invite it yourself later.Only public channels are listed. For a private channel, invite the bot from Slack.
5. Talk to the bot in Slack
Once connected, there are two ways to reach it:
The bot must be in the channel before a mention reaches it. If you skipped the channel picker, invite it with:
The bot only responds when it’s mentioned or messaged directly. It doesn’t read everything said in a channel it belongs to.
6. Reconnect an existing bot
Disconnecting keeps the Slack app, so a bot you created before can be brought back without a new token.1
Open the Slack setup dialog
On the Deploy step, click Connect Slack.
2
Switch to Reconnect existing bot
If you have a previously created bot, a Reconnect existing bot option appears next to Create new bot. Pick it, then select the bot from the list.Each entry shows its name, its workspace, and why it stopped — removed from Slack or access revoked.
3
Approve in Slack
Click Allow in the Slack window to turn it back on. No token is needed for a reconnect.
7. Permissions & data access
The bot CAN:- Receive @mentions in channels it has been added to, and direct messages.
- Post replies in those channels (in-thread) and DMs.
- List the workspace’s public channels during setup, and join the ones you pick.
- Read messages in a channel that don’t mention it.
- See private channels it hasn’t been invited to.
- Act in any workspace other than the one the app was installed in.
8. Troubleshooting
For general connector issues, see /mcp/integrations.
9. Frequently asked questions
Is my configuration token stored? It’s used once, at creation, to build the Slack app. After that the bot runs on its own app credentials, and the token expires on its own after 12 hours. Can I rename the bot later? The name is set at creation from the Bot name field. To change it, rename the app in Slack, or create a new bot — which replaces the current one. Can one chatbot have bots in two workspaces? No. An agent has one Slack bot at a time. Creating a new one replaces the current bot, which can be reconnected later. Do I need to be a Slack admin? You need to be able to generate a configuration token and approve the install. On workspaces that restrict app installs, an admin has to approve it. How is this different from the Slack connector? This deploys your chatbot into Slack so people can talk to it. The Slack connector gives an agent Slack tools — sending messages, reading channels — to use inside a workflow. Does it reply in a thread? Yes, for channel mentions. Direct messages are answered in the DM.10. References
- Slack apps dashboard: https://api.slack.com/apps
- App configuration tokens: https://api.slack.com/authentication/config-tokens
- Slack Events API: https://api.slack.com/apis/connections/events-api

