Skip to main content Skip to complementary content

Configuring the communication channel for Slack

After you create a Microsoft Azure Bot, you can enable the Slack channel. This lets you query your Qlik Sense data directly from Slack using natural language queries.

Information noteBefore you begin, we recommend that you open a notepad to record usernames, passwords, IDs, and tokens that you need to complete the configuration. Add this section to the bottom of your notepad:

====Slack details====
Slack bot URL =					
Bot User OAuth Access Token =
Client ID =
Client Secret =
Signing secret = 
===================================
===================================
				

Creating a Slack app

Information noteYou must have Slack administrator privileges to use the Slack API.
  1. Go to Slack API.

  2. In the top navigation bar, click Your Apps.

  3. Click Create an App.

    Slack API navigation menu

  4. Enter an App Name and choose the Development Slack Workspace, then click Create App.

Adding a redirect URL

  1. Under Features in the left-side menu, select OAuth & Permissions.

  2. Click Add New Redirect URL.

  3. Enter https://slack.botframework.com, then click Add.

    Slack API OAuth path with redirect URL field

  4. Click Save URLs.

  5. Scroll down to the Scopes section. Add the following Bot Token Scopes:

    Slack API scopes, showing channels:history channels:read chat:write files:read files:write groups:history groups:read im:history mpim:history users.profile:read users:read

Creating a Slack bot user

  1. Under Features in the left-side menu, click App Home.

  2. Toggle on Always Show my Bot as Online.

    The Slack API App home page, showing the toggle for keep bot online

  3. Scroll down and select Allow users to send Slash commands and messages from messages tab.

Information noteIn this section, verify or edit your display name and default name.

Subscribing to Slack bot events

  1. Under Features in the left-side menu, click Event Subscriptions.

  2. Toggle on Enable Events.

  3. In the Request URL field, enter the Azure Bot URL you saved to your notepad.

    Information noteThe URL should be https://slack.botframework.com/api/Events/{Bot handle}, where {bot handle} is your Azure Bot handle.
  4. Scroll down to Subscribe to Bot Events and add the following user events, then click Save.

    • member_joined_channel

    • member_left_channel

    • message.channels

    • message.groups

    • message.im

    • message.mpim

Configuring interactive components

  1. Under Features in the left-side menu, select Interactive Components.

  2. Toggle on Interactivity.

  3. In the Request URL field, enter https://slack.botframework.com/api/Actions, then click Save Changes.

Installing the application

  1. Under Settings in the left-side menu, select Install App.

  2. Click Install App to Workspace.

  3. In the permission request window that opens, click Allow.

  4. Copy the Bot User OAuth Access Token.

    Slack API OAuth tokens window, showing the oauth token and bot user token

    Information noteSave the OAuth token to your notepad to use later when configuring the Bot Channel Configuration App.
  5. Under Settings in the left-side menu, select Basic Information.

  6. Scroll down to App Credentials.

  7. Copy your Client ID, Client Secret, and Signing Secret.

    Information noteSave these to your notepad.

Configure Slack Bot with Azure

  1. Log in to your Microsoft Azure portal.

  2. Click your Resource group to see the list of resources.

  3. Click your Azure Bot to configure it.

  4. Under Bot Management, select Channels.

  5. Under More channels, select Slack.

    The Azure channels page, showing more channels

  6. In the Client ID, Client Secret, and Signing Secret fields, enter the values you saved earlier, then click Save.

    Azure Slack bot credentials page

  7. In the permission request window that opens, click Allow.

Now that you have configured the communication channel, you can configure the Bot Channel Service.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!