Skip to main content
In this lesson, you’ll learn how to integrate the Slack Notification plugin with Jenkins to automatically publish build status messages to your Slack channels. This guide provides a step-by-step approach, complete with configuration details and example code blocks to help you set up and test notifications effectively.

​
Step 1: Install the Slack Notification Plugin

Begin by installing the Slack Notification plugin on your Jenkins instance. This plugin is accessible via the Plugin Manager in Jenkins, helping to integrate Jenkins with Slack by sending build status messages.
The image shows the Jenkins plugin management interface, specifically the "Available plugins" section, with a search for "Slack Notification" displayed.
After locating the plugin using the search feature, proceed with its installation. You can monitor the plugin download progress during the installation process:
The image shows a Jenkins interface displaying the download progress of plugins, with options for managing plugins and checking connectivity status.
Once the installation is complete, restart Jenkins to apply the new settings.

​
Step 2: Review Slack Notification Plugin Documentation

Before diving into configuration, it is essential to review the Slack Notification plugin documentation. If you are new to Slack, first create an account and set up your workspace. Within this workspace, create a dedicated Slack channel for receiving Jenkins notifications. For instance, you might create a channel named “Dasher notifications.”
The image shows a Slack interface where a user is in the process of creating a new channel named "das" within a workspace.

​
Step 3: Create a Slack App from Manifest

Next, create a new Slack App in your workspace. In Slack’s app configuration, choose to create an app from an app manifest. Select your workspace (for our purposes, the Jenkins workspace), and replace any pre-filled content with the YAML manifest provided below.
The image shows a webpage from the Jenkins plugins site, specifically for the Slack Notification plugin, including installation instructions and version details.

​
YAML Manifest for Slack App

Use the following YAML manifest, which includes all required bot scopes for full functionality: 
display_information:
  name: Jenkins
features:
  bot_user:
    display_name: Jenkins
    always_online: true
oauth_config:
  scopes:
    bot:
      - channels:read
      - chat:write
      - chat:write.customize
      - files:write
      - reactions:write
      - users:read
      - users:read.email
      - app_mentions:read
      - groups:read
      - users:read:admin
      - gnpubs:read
settings:
  org_deploy_enabled: false
  socket_mode_enabled: false
  token_rotation_enabled: false
After pasting the manifest into Slack’s configuration, click Next. You will see a summary page displaying the eight permissions associated with your bot user.
The image shows a Slack API page where a user is selecting a workspace named "Jenkins" to develop an app. A pop-up window is prompting the user to pick the workspace and proceed to the next step.
Review the summary details: 
1  display_information:
2    name: Jenkins
3  features:
4    bot_user:
5      display_name: Jenkins
6      always_online: true
7  oauth_config:
8    scopes:
9      bot:
10       - channels:read
11       - chat:write
12       - chat:write.customize
13       - files:write
14       - reactions:write
15       - users:read
16       - users:read.email
17       - app_mentions:read
18  settings:
19    org_deploy_enabled: false
20    socket_mode_enabled: false
21    token_rotation_enabled: false
When you are satisfied with the configuration details, click Create. Once the app creation process is complete, Slack will provide you with an OAuth token. Be sure to click Install App to Workspace when prompted to ensure the app is properly installed in your Slack workspace. At times, you might encounter an alternative version of the manifest used internally by Slack, such as: 
display_name: Jenkins
always_online: true
oauth_config:
  scopes:
    bot:
      - channels:read
      - chat:write
      - files:write
      - reactions:write
      - users:read
      - users:read:admin
      - gnpubs:read
settings:
  oauth_mic_enabled: true
  socket_mode_enabled: false
  token_rotation_enabled: false
After the installation, keep the provided OAuth token secure as it is crucial for connecting Jenkins with Slack.
The image shows a Slack authorization page where Jenkins is requesting permission to access a Slack workspace, with options to allow or cancel.
You can also review the installed app settings and OAuth token information:
The image shows the Slack API interface for installed app settings, displaying an OAuth token for a Jenkins app with options to copy the token or reinstall the app.

​
Step 4: Configure Slack Credentials in Jenkins

With your OAuth token ready, proceed to configure the Slack integration within Jenkins:
  1. Navigate to Manage Jenkins → Configure System.
  2. Locate the Slack notification settings.
  3. Enter your workspace name (for example, Jenkins).
  4. Create new credentials of type Secret Text, then paste your bot user OAuth token. For instance, set the credential ID as “Slack bot token.”
The image shows a Jenkins interface for adding credentials, with fields for domain, kind, scope, secret, ID, and description. The "Kind" is set to "Secret text," and there are suggestions for the ID field.
After adding the credentials, select the newly created Slack token in your configuration settings. Specify the Slack channel where notifications should be sent (e.g., “Dasher notifications”). For advanced settings, you may leave the default values for icon emoji and username. Click Test Connection. If you receive an error message like: 
Failure(["ok":false,"error":"not_in_channel"])
This error indicates that your Jenkins app user is not a member of the specified Slack channel. To resolve this, invite the Jenkins app to the channel by typing @Jenkins (or the app’s display name) within the channel.
Once the app is added to the channel, test the connection again until you receive a success confirmation. To further verify the connection via a pipeline step, use the following command: 
slackSend color: "good", message: "Message from Jenkins Pipeline"
This confirms that the integration is working correctly.

​
Conclusion

With these steps completed, you have successfully set up Slack notifications in Jenkins. Your build statuses and messages will now be automatically posted to the designated Slack channel, ensuring that you stay informed of build outcomes in real time. For further details about the Slack/Jenkins integration, you can visit the plugin page at Jenkins Plugin Page. Thank you for following this lesson.
For more information, consider reviewing the following resources:

Watch Video