Sistava

How to Add a Bot to Slack: Install, Invite, Permissions

How-to — — by Mahmoud Zalt

Install a Slack bot, invite it to the right channel, handle private channels, and get past app approval when you are not an admin.

The reason this is the top question is that the install works and then nothing happens. The bot is in your workspace, it shows up in the member directory, and it is completely silent in the channel where you wanted it. That is not a bug. A workspace install and a channel membership are different things.

This covers the whole thing: installing, inviting, the extra step private channels need, what to do when the install button turns into a request, and what a bot can and cannot read once it is in. It also covers building your own, briefly, for the people who searched this because no existing bot does the thing they want.

If your goal is a bot that does real work rather than posting notifications, it is worth knowing that whole category has moved on. Instead of wiring a bot to a trigger, you can hire an AI Employee at Sistava and reach it in Slack. Same doorway, very different thing behind it. The install mechanics below are identical either way.

How do I install a bot into my Slack workspace?

Click Tools in the sidebar, or More if Tools is not shown, then click Apps. Search for the app, click Add to open the Slack Marketplace listing, then click Add to Slack and follow the prompts. Some workspaces show an Automations tab where Tools normally sits, and that works the same way.

By default, any member of a Slack workspace can install an app. That surprises people who assume they need to ask IT. It also surprises admins who assumed nobody could, which is why app approval exists and why many workspaces have it switched on.

From nothing to a working bot in a channel

  1. Find the app in the Marketplace — Search from Tools, then Apps. Check the publisher name before you install. Lookalike apps with near identical names and icons are common.
  2. Click Add to Slack and read the permissions — This screen lists what the app is asking for. It is the only place you see the full list in one view, and it is worth ten seconds.
  3. Approve, or send a request — If your workspace requires approval, the install becomes a request. Add a short note explaining what it is for and click Submit. An owner reviews it and you get a notification.
  4. Open the channel you actually want it in — Installing puts it in the workspace, not in your channel. This is the step everyone skips before concluding the bot is broken.
  5. Invite it — Type a slash invite command followed by the app's name and send it. You can also mention the app in the message box and choose to invite it when Slack offers.
  6. Repeat for each private channel — Private channels are per channel work. There is no bulk switch for them, and skipping one is the usual cause of a bot that works in some places and not others.

Some apps document a third route through the channel itself: click the channel name to open the channel menu, open the Integrations tab, and add the app from there. That path is described in several vendors' own setup guides rather than in Slack's core help article, so treat it as a convenience that may or may not appear for the app you are installing.

Why can the bot not see my private channel?

Because it is not a member of it. Slack's developer documentation is direct about this: with a bot token, an app can read any conversation the bot is a member of, and nothing else. Try to read a channel it has not joined and the API returns not_in_channel, described as the token not having access to the proper channel.

That is a good design. It means installing an app does not hand it your entire company history, and it means the scope of a bot is something you can see by looking at the channel member lists rather than trusting a privacy policy.

What if I am not allowed to install apps?

Then your workspace has app approval turned on, and your install becomes a request. Click Add to Slack, add a message giving the reason, and click Submit. A workspace owner reviews it and you are notified either way. There is no member side workaround, and looking for one is a waste of an afternoon.

Owners manage the surrounding rules under Admin in the sidebar, then Apps and workflows, then App Management Settings, clicking Edit next to each permission. One of those permissions is to only allow apps from the Slack Marketplace, which blocks anything installed by a direct link from a vendor's own site.

If you are writing that request, be concrete. Name the channel, name the task, and name the number of people it helps. "Trying an AI tool" gets declined. "For #support, to draft first replies to the repeat questions we answer twenty times a week" gets approved, because the admin can weigh it.

Can I build my own bot?

Yes, and the shape is consistent: you create an app in Slack's developer tools, give its bot user the token scopes it needs, install it to your workspace, then invite it to channels exactly like any other bot. Reading messages needs history scopes, and Slack names them per conversation type: channels, groups, im and mpim.

The honest caveat is that the Slack side is the easy half. Getting the bot to say something worth reading is the other ninety percent, and that is where most homegrown bots stall at posting a notification nobody reads.

If your reason for building was that nothing off the shelf does your specific job, that is exactly the gap a custom AI Employee fills without a repository or a release pipeline. You describe the role in plain English, it gets a brief, and Slack becomes one of the places it can be reached. Here is what building one looks like.

What adding a bot will not fix

A bot in a channel does not change what people do in that channel. Most abandoned bots were installed correctly, invited correctly, and then ignored, because nobody was clear about which job it had taken over from a human.

The fix for all four is the same and it is boring: one channel, one job, one person who owns it for a month. Bots that survive were introduced that way. Bots that got installed across fifteen channels on a Friday were not.

FAQ

I installed the bot but it does nothing in my channel. Why?

Because installing adds it to the workspace, not to the channel. Open the channel and invite it, either with the slash invite command and the app's name, or by mentioning it in the message box and choosing to invite it when Slack offers. Private channels always need this step.

Do I need to be an admin to add a bot?

Not by default. Slack says any member of a workspace can install an app unless workspace owners have turned on app approval. If approval is on, your install turns into a request with a note attached and an owner decides.

How do I add a bot to a private channel?

From inside the private channel, as someone who is already a member. Use the slash invite command with the app's name, or mention the app and choose to invite it. Some apps also expose an Integrations tab in the channel menu. You repeat this for every private channel.

Can a bot read messages sent before it joined?

Only where the app is a member of the conversation and the app deliberately reads history. Slack's developer docs state that a bot token reaches conversations the bot belongs to, and a request for a channel it has not joined returns not_in_channel.

How do I remove a bot?

You can remove it from a single channel while leaving it installed, or uninstall the app from the workspace entirely. Removing it from a channel is the gentler option when a bot is useful in one place and noisy in another, and it takes effect immediately.

Is a bot the same as an AI assistant in Slack?

No. A traditional bot responds to commands and triggers. An AI assistant app holds a conversation, and Slack treats it as a separate experience an admin can enable per app. The install and invite mechanics are the same for both.

A rollout that sticks

Install it, invite it to exactly one channel, and post one message telling people what it is for and what it can see. Then give it a job that someone was already doing by hand. A bot with a job survives. A bot that is a demo gets muted within a week and nobody ever mentions it again.

If you get to the end of the month and the useful thing is not notifications but actual work getting finished, compare what that costs against a person's hours. The Sistava plans and credits are priced per role for exactly that comparison, and the Slack side stays the same simple install and invite.

One more thing worth doing on install day. Write down, somewhere your team can find it, which channels the bot is in and who added it. Six months later, when someone asks whether the thing posting in #ops has access to the finance channel, that note answers the question in seconds instead of starting an audit. It costs a minute now and saves an uncomfortable meeting later.

Then review that list once a quarter and remove it from any channel where nobody has spoken to it. Bots accumulate quietly, and the cleanest workspaces are the ones where someone occasionally prunes.

Sources