GitLab for Slack app
Introduced for self-managed instances in GitLab 16.2.
The GitLab for Slack app is a native Slack app that provides slash commands and notifications in your Slack workspace. GitLab links your Slack user with your GitLab user so that any command you run in Slack is run by your linked GitLab user.
Install the GitLab for Slack app
Prerequisites:
- You must have the appropriate permissions to add apps to your Slack workspace.
- On self-managed GitLab, an administrator must enable the integration.
In GitLab 15.0 and later, the GitLab for Slack app uses granular permissions. Although functionality has not changed, you should reinstall the app.
From project integration settings
To install the GitLab for Slack app from project integration settings:
- On the left sidebar, select Search or go to and find your project.
- Select Settings > Integrations.
- Select GitLab for Slack app.
- Select Install GitLab for Slack app.
- On the Slack confirmation page, select Allow.
To update the app in your Slack workspace to the latest version, you can also select Reinstall GitLab for Slack app.
From the Slack App Directory
On GitLab.com, you can also install the GitLab for Slack app from the Slack App Directory.
To install the GitLab for Slack app from the Slack App Directory:
- Go to the GitLab for Slack page.
- Select a GitLab project to link with your Slack workspace.
Update the GitLab for Slack app
When GitLab releases new features for the GitLab for Slack app, you might have to manually update your app to use the new features.
To update your GitLab for Slack app:
- On the left sidebar, select Search or go to and find a project for which the GitLab for Slack app is configured.
- Select Settings > Integrations.
- Select GitLab for Slack app.
- Select Reinstall GitLab for Slack app.
The GitLab for Slack app is updated for all projects that use the integration.
Alternatively, you can configure the integration again.
Slash commands
You can use slash commands to run common GitLab operations. Replace <project>
with a project full path.
For the GitLab for Slack app:
- You must authorize your Slack user on GitLab.com when you run your first slash command.
- You can create a shorter project alias for slash commands.
For Slack slash commands on self-managed GitLab and Mattermost slash commands,
replace /gitlab
with the slash command trigger name configured for your integration.
The following slash commands are available:
Command | Description |
---|---|
/gitlab help
| Shows all available slash commands. |
/gitlab <project> issue new <title> Shift+Enter <description>
| Creates a new issue with the title <title> and description <description> .
|
/gitlab <project> issue show <id>
| Shows the issue with the ID <id> .
|
/gitlab <project> issue close <id>
| Closes the issue with the ID <id> .
|
/gitlab <project> issue search <query>
| Shows up to five issues matching <query> .
|
/gitlab <project> issue move <id> to <project>
| Moves the issue with the ID <id> to <project> .
|
/gitlab <project> issue comment <id> Shift+Enter <comment>
| Adds a new comment with the comment body <comment> to the issue with the ID <id> .
|
/gitlab <project> deploy <from> to <to>
|
Deploys from the <from> environment to the <to> environment.
|
/gitlab <project> run <job name> <arguments>
| Executes the ChatOps job <job name> on the default branch.
|
/gitlab incident declare
| Opens a dialog to create a new incident from Slack (Beta). |
The deploy
slash command
To deploy to an environment, GitLab tries to find a deployment manual action in the pipeline.
If only one action is defined for a given environment, it is triggered. If more than one action is defined, GitLab tries to find an action name that matches the environment name to deploy to.
The command returns an error if no matching action is found.
Create a project alias for slash commands
By default, slash commands expect a project full path. To create a shorter project alias in the GitLab for Slack app:
- On the left sidebar, select Search or go to and find your project.
- Select Settings > Integrations.
- Select GitLab for Slack app.
- The current Project Alias, if any, is displayed. To edit this value, select Edit.
- Enter your desired alias, and select Save changes.
Slack notifications
Introduced in GitLab 15.9.
With Slack notifications, GitLab can send messages to Slack workspace channels for certain GitLab events.
Configure notifications
To configure Slack notifications:
- On the left sidebar, select Search or go to and find a project for which the GitLab for Slack app is installed.
- Select Settings > Integrations.
- Select GitLab for Slack app.
- In the Trigger section, select the checkbox for each GitLab event you want to receive a notification for in Slack. For a full list, see Notification events.
- For each checkbox you select, enter the name of the channel that receives the notifications (for example,
#my-channel
).- To send notifications to multiple Slack channels, enter up to 10 channel names separated by commas (for example,
#channel-one, #channel-two
).
If the channel is private, you must also add the GitLab for Slack app to the private channel. - To send notifications to multiple Slack channels, enter up to 10 channel names separated by commas (for example,
- Select the Notify only broken pipelines checkbox to notify only on failures.
- From the Branches for which notifications are to be sent dropdown list, select which branches you want to receive notifications (if relevant to your events).
- Leave the Labels to be notified text box blank to receive all notifications, or add labels the issue or merge request must have to trigger a notification.
- Select Save changes.
Your Slack workspace can now start receiving GitLab event notifications.
Receive notifications to a private channel
To receive notifications to a private Slack channel, you must add the GitLab for Slack app to the channel:
- Mention the app in the channel by typing
@GitLab
and pressing Enter. - Select Add to Channel.
Notification events
The following events are available for Slack notifications:
Event name | Description |
---|---|
Push | A push to the repository. |
Issue | An issue is created, updated, or closed. |
Confidential issue | A confidential issue is created, updated, or closed. |
Merge request | A merge request is created, updated, or merged. |
Note | A comment is added. |
Confidential note | A confidential note is added. |
Tag push | A new tag is pushed to the repository. |
Pipeline | A pipeline status changed. |
Wiki page | A wiki page is created or updated. |
Deployment | A deployment starts or finishes. |
Alert | A new, unique alert is recorded. |
Vulnerability | A new, unique vulnerability is recorded. |