Slack integration
This is not a bot that sits in Slack waiting to be asked. This is your assistant — wherever it runs — reaching into your workspace: searching what was said, posting where it matters, replying in the thread that already exists.
Connecting Slack
Open the assistant and choose Slack
The integrations list is in the assistant's tools section. This is the tool integration — connecting your assistant as a bot inside Slack is a separate thing, set up on the channels side.
Authorise the workspace
You are redirected to Slack, you pick the workspace and approve the permissions, and Slack sends you back. No app to register, no token to copy.
Always enable the finding tools
Find user by email and find public channel are what turn names into the IDs every other tool needs. Skip them and most of the rest has nothing to work with.
Then add reading, then sending
Search messages is the one that changes how the assistant answers. Send and reply are the ones other people see. Add them in that order and you will always know what changed.
Leave the managing tools off unless you mean it
Delete message is permanent with no confirmation, and remove user from channel does exactly what it says. Neither is needed for the useful cases.
What Slack is bad at once the workspace is old
It was decided in a thread and the thread is gone
Not deleted — just buried under four months of other conversation, in a channel you are no longer sure you were in. The answer exists and is unreachable in practice.
Notifications go to the wrong place
Something happens in your product, on your website, in your CRM. The people who need to know are in Slack, and the two never meet without somebody copying and pasting.
Answering the same question in four channels
The same policy, the same link, the same explanation — retyped, in a slightly different form each time, until nobody is sure which version is current.
Most integrations want the whole workspace
Read everything, post anywhere, delete anything. The permissions you actually want are much narrower than what you are usually offered.
Twelve tools in four groups — and a distinction worth two minutes
First, the distinction. Mingleego can do two different things with Slack, and mixing them up leads to disappointment. A Slack bot means your assistant lives in Slack and your team talks to it there — that is the channel, and it has its own page. This integration is the other direction: your assistant, running anywhere at all, uses Slack as a tool. The assistant answering on your website can search Slack for an answer and post a notification to a channel. You can have both, and most teams eventually do. The tools come in four groups. Finding resolves names into the identifiers everything else needs: a user by email, a public channel by name. Reading covers a single message, its permalink, a channel's metadata, its members, and a full-text search across the workspace. Sending is three tools — a new message in a public channel, a message in a private one, and a reply inside an existing thread. Managing is two, and both are blunt: delete a message, remove a user from a channel. One thing to know before you plan around it: the assistant has no built-in map of your workspace. Channel IDs, user IDs and message timestamps are either handed to it or looked up first. That is why the finding tools matter more than they sound — without them, most of the others have nothing to act on. Connecting is one authorisation. Mingleego uses a managed Slack application, so there is no app to create and no bot token to paste. Teams that need their own app can build one; the guide covers that path.
What teams actually wire up
A website conversation raises a flag in Slack
Something on the site needs a human. The assistant posts it into the channel where that gets picked up, with the context already written.
Answering from what the team already said
Did we ever agree a policy on this. The assistant searches Slack, reads what it finds and answers — with the permalink, so you can check it.
Replying in the thread, not beside it
Follow-ups land inside the conversation that started them, which is the difference between a useful channel and an unreadable one.
CRM and Slack in one step
With HubSpot or Bitrix24 connected as well, the lead is recorded and the sales channel is told, from the same conversation.
Finding the right person
Resolve an email into a Slack user, then post where they will see it — instead of guessing who owns what.
Slack plus the workspace
With Notion connected, the assistant can read what was decided, post the summary to the channel and link the page.
The twelve tools, with their real limits
Find a user, find a channel
Resolves an email into a Slack user and a channel name into a channel ID. Both are exact lookups — no fuzzy matching, no "#" on the channel name, and private channels cannot be discovered this way.
Search messages
Full-text search across the workspace, returning author, text, timestamp and a permalink. This is the tool for "find where we discussed the budget". It needs a user token with search permission — a bot token alone will not do it.
Read a message or a conversation
Fetch one message by its timestamp, get its permanent link, check a channel's details, or list its members — up to fifty ids per call, requested page by page.
Post a message
One message to a public channel, by channel ID. A separate tool posts to private channels, and for those the bot has to already be a member — it cannot invite itself in.
Reply in thread
Posts inside an existing thread rather than as a new top-level message, so the answer stays attached to the question that prompted it.
Delete and remove
Delete a message — permanent, no confirmation, no undo, and normally only messages the bot posted itself. Remove a user from a channel, which your workspace permissions may refuse outright.
Questions worth asking first
Direction. The Slack bot channel puts your assistant inside Slack so your team can talk to it there. This integration lets your assistant — running on your website, in Telegram, anywhere — use Slack as a tool: search it, post to it, reply in it. They are complementary, and connecting one does not connect the other.
Give it the finding tools and search, and nothing else
An assistant that can look things up in Slack and quote the permalink is useful on day one and cannot change a thing. Decide about posting after that.
Create an assistant