Slack v3 Backend

This backend lets you connect to the Slack messaging service using the Real-time Messaging Protocol, Events Request-URL or Events Socket mode.

Note

The use of the Real-time messaging protocol is not recommended by Slack and they urge people to move to the Event based protocol. https://api.slack.com/changelog/2021-10-rtm-start-to-stop

To select this backend, set BACKEND = ‘SlackV3’.

Dependencies

You need to install Slackv3 dependencies before using Errbot with Slack. In the below example, it is assumed slackv3 has been download to the /opt/errbot/backends directory and errbot has been installed in a python virtual environment (adjust the command to your errbot’s installation):

git clone https://github.com/errbotio/err-backend-slackv3.git
source /opt/errbot/bin/activate
/opt/errbot/bin/pip install -r /opt/errbot/backends/err-backend-slackv3/requirements.txt

Connection Methods

Over the years, Slack has changed to their OAuth and API architecture that can be a source of confusion. No matter which OAuth bot token you’re using or the API architecture in your environment, slackv3 can handle it.

The backend will automatically detect which token and architecture you have and start listening for Slack events in the right way:

Legacy tokens (OAuthv1) with Real Time Messaging (RTM) API

When the following oauth scopes are detected, the RTM protocol will be used. These scopes are automatically present when using a legacy token.

"apps"
"bot"
"bot:basic"
"client"
"files:write:user"
"identify"
"post"
"read"

  • Current token (OAuthv2) with Event API using the Event Subscriptions and Request URL.

  • Current token (OAuthv2) with Event API using the Socket-mode client.

Backend Installation

These instructions are for errbot running inside a Python virtual environment. You will need to adapt these steps to your own errbot instance setup. The virtual environment is created in /opt/errbot/virtualenv and errbot initialised in /opt/errbot. The extra backend directory is in /opt/errbot/backend.

  1. Create the errbot virtual environment

mkdir -p /opt/errbot/backend
virtualenv --python=python3 /opt/errbot/virtualenv

  1. Install and initialise errbot. See here for details

source /opt/errbot/virtualenv/bin/activate
pip install errbot
cd /opt/errbot
errbot --init

  1. Configure the slackv3 backend and extra backend directory. Located in /opt/errbot/config.py

BACKEND="SlackV3"
BOT_EXTRA_BACKEND_DIR=/opt/errbot/backend

  1. Clone err-backend-slackv3 into the backend directory and install module dependencies.

cd /opt/errbot/backend
git clone https://github.com/errbotio/err-backend-slackv3
pip install -r /opt/errbot/backend/err-backend-slackv3/requirements.txt

  1. Configure the slack bot token, signing secret (Events API with Request URLs) and/or app token (Events API with Socket-mode). Located in /opt/errbot/config.py

BOT_IDENTITY = {
    'token': 'xoxb-...',
    'signing_secret': "<hexadecimal value>",
    'app_token': "xapp-..."
}

Setting up Slack application

Legacy token with RTM

This was the original method for connecting a bot to Slack. Create a bot token, configure errbot with it and start using Slack. Pay attention when reading real time messaging explaining how to create a “classic slack application”. Slack does not allow Legacy bot tokens to use the Events API.

Current token with Events Request URLs

This is by far the most complex method of having errbot communicate with Slack. The architecture involves server to client communication over HTTP. This means the Slack server must be able to reach errbot’s /slack/events endpoint via the internet using a valid SSL connection. How to set up such an architecture is outside the scope of this readme and is left as an exercise for the reader. Read slack events api document for details on how to configure the Slack app and request URL.

Current token with Events Socket-mode client

Create a current bot token, enable socket mode. Configure errbot to use the bot and app tokens and start using Slack. Read socket-mode for instructions on setting up Socket-mode.

Ensure the bot is also subscribed to the following events:

  • file_created

  • file_public

  • message.channels

  • message.groups

  • message.im