Slack
Set up an AI agent for Slack. This Slack chatbot answers questions in the thread from your knowledge, links the source, and works your other apps from there.
eesel's AI agent for Slack is an AI Slack bot your team @mentions in a channel or messages directly. It answers in the thread from your connected knowledge, with a link to the source, and it can also draft replies or do work in your other apps from that thread.
Invite your AI teammate into Slack and it answers questions in the thread from your knowledge, with a link to the source. It keeps answering follow-ups in that thread without being mentioned again. From the same thread it also does work in your other integrations, such as looking things up and drafting replies. It is not Slack AI, which is Slack's own built-in feature.

Set up eesel in Slack
Ask your agent to connect Slack
Open the chat in your dashboard and ask it to connect Slack. It posts an Add to Slack link for you to open and approve in the browser. It then waits for you to say it is done. Prefer to click? Integrations > Slack has the same Connect button.

Approve it in Slack
The link opens Slack's own permission screen. Pick the workspace, read the list of what the app can view and do, and click Allow.
Slack shows a notice saying the app is not approved by Slack. That is because eesel is not listed in the Slack Marketplace. It is not an error and it does not limit what the app can do.

A person approves this in the browser.
Confirm the connection
Tell your agent in the chat that you approved it. It confirms the connection, names the person who approved it, and says how to reach it in Slack.

Check it worked. The left sidebar now lists Slack with your workspace name. From a terminal, eesel status lists the integration as connected.
Check the workspace is on your agent
Integrations > Slack shows the connection as Connected, with your Slack workspace name. The Automations section lists the mention automation for this workspace, switched on. The Actions section shows the Read and Write action groups.

Ask it a question in a channel
Your teammate asks before it joins a channel. Right after you connect, it sends a direct message to whoever installed it, naming the public channels it would like to join and why. It joins only the ones you say yes to, then reads the most active of them to get to know your team. Naming a channel yourself, for example "read #support", counts as a yes. Private channels always need a person to run /invite @eesel.
Connecting alone does not start your agent. It needs an automation first. Ask in the dashboard chat to turn on the mention automation, and tell it how you want it to answer. Anyone can then mention it in a channel it is in and get the answer in the thread. Direct messages need no mention. It has an App Home tab in Slack too.

Check it worked. Your Automations page lists the automation, switched on. From a terminal, eesel automations lists the automation as on.
Ask it to do work in your other apps
Mention your agent and ask for a look-up in a connected store or helpdesk. It answers in the thread with what it found.

Ask it to draft a reply and the draft appears in the thread. It sits there until you tell it to send, and the thread says so.

Approve it from the thread
Tell it to go ahead. If an action is waiting on a person, its approval card posts in the same thread. Each action gets its own card naming the integration, the action, the record it touches and the content. Approve and Deny decide it, and Review in eesel opens the same approval in the dashboard. Nothing runs until someone decides it.
Only people with edit rights in your eesel workspace can decide an approval, in Slack or in the dashboard.

Sources, triggers and actions
Sources
Slack is a place your agent answers, not a knowledge source it indexes. Nothing in your Slack workspace is copied into eesel. Your agent searches messages live while it answers. Once it is in a channel it can read that channel's history, including messages from before it arrived.
Its answers in Slack come from what else you have connected. Confluence, Notion and Google Drive are usually where the answers live. Your help center or website helps if people in Slack ask what customers ask. See Integrations.
Search only ever covers channels your agent is in. Within those, it covers every public channel, plus the private channels the person asking is also in. Reading a channel's history also needs your agent to be in it.
Your agent also reads images attached to a mention, up to five of them.
Triggers
Triggers are the Slack events an automation can run on:
When @eesel is mentioned in a channel
Someone mentions the eesel app in a channel it is in
Answering questions on demand
slack_eesel_mentioned
Slack has one trigger. The trigger event is fixed when the automation is created. So a new automation is required for each different trigger event.
The automation has three controls:
Channels. A multi-select picker where you choose channels by name, or paste channel IDs. Leave it empty and the automation covers every channel your agent is in.
The instructions. Describe in plain language the questions you want it to take and what to do with them, and it skips the rest.
Pause. A switch that stops the automation. While it is paused your agent is silent in Slack.
Several agents on one Slack workspace. The Channels picker on each automation decides which agents are eligible in a channel. Where more than one is eligible, eesel picks from the question itself. When it is not sure, it posts a picker in the thread and you choose. The first agent to answer in a thread owns that thread from then on.
Actions
Actions are what it can do:
Respond
Send Message
Sends a message to a channel, a thread, or a person as a direct message, using Slack's own formatting
Add reaction
Reacts to a message with an emoji
Manage
Join channel
Joins a public channel with no /invite needed, after asking in the conversation first. Public channels only
List channels
Lists the workspace's channels, flagging which ones your agent is in
Look up
Look up user
Finds a Slack user by email or name
Read thread
Reads a full thread, with each message marked as your agent's or someone else's
Read channel
Reads the recent messages in a channel
Search messages
Searches past Slack messages live. Nothing is indexed
You stay in control the whole way. Adjust your AI agent's access to knowledge and its action permissions to your liking. See Actions and Approvals.
Limitations
It only reads and posts where it is a member. Private channels need a person to invite it.
Nothing from Slack is indexed. It searches your Slack history live while it answers. The rest of its answers come from your other connected sources.
One trigger. The mention automation is the only Slack trigger. Follow-ups in a thread it has answered need no new mention.
One Slack workspace, one eesel workspace. A Slack workspace answers to the eesel workspace that connected it last. Connecting it from a second eesel workspace moves it there.
Up to five images per mention. It reads images attached to a mention, up to five of them.
Older connections may lack newer permissions. Reconnect to pick them up. See Troubleshooting below.
Troubleshooting
FAQ
Related pages
Internal operations for the job your agent does for your team
Helpdesk for the customer-facing work it can run from a thread
Actions and Approvals for choosing what your agent may do
Integrations overview for how sources, triggers and actions fit together
Last updated
