GitLab for Slack app

Introduced for self-managed instances in GitLab 16.2.

note
This page contains information about configuring the GitLab for Slack app on GitLab.com. For administrator documentation, see GitLab for Slack app administration.

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:

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:

  1. On the left sidebar, select Search or go to and find your project.
  2. Select Settings > Integrations.
  3. Select GitLab for Slack app.
  4. Select Install GitLab for Slack app.
  5. 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:

  1. Go to the GitLab for Slack page.
  2. 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:

  1. On the left sidebar, select Search or go to and find a project for which the GitLab for Slack app is configured.
  2. Select Settings > Integrations.
  3. Select GitLab for Slack app.
  4. 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:

For Slack slash commands on self-managed GitLab, Mattermost slash commands, and ChatOps, replace /gitlab with the slash command trigger name configured for your integration.

The following slash commands are available:

CommandDescription
/gitlab helpShows 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 declareOpens 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:

  1. On the left sidebar, select Search or go to and find your project.
  2. Select Settings > Integrations.
  3. Select GitLab for Slack app.
  4. The current Project Alias, if any, is displayed. To edit this value, select Edit.
  5. 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:

  1. On the left sidebar, select Search or go to and find a project for which the GitLab for Slack app is installed.
  2. Select Settings > Integrations.
  3. Select GitLab for Slack app.
  4. 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.
  5. 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).
    note
    If the channel is private, you must also add the GitLab for Slack app to the private channel.
  6. Select the Notify only broken pipelines checkbox to notify only on failures.
  7. 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).
  8. 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.
  9. 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:

  1. Mention the app in the channel by typing @GitLab and pressing Enter.
  2. Select Add to Channel.

Notification events

The following events are available for Slack notifications:

Event nameDescription
PushA push to the repository.
IssueAn issue is created, updated, or closed.
Confidential issueA confidential issue is created, updated, or closed.
Merge requestA merge request is created, updated, or merged.
NoteA comment is added.
Confidential noteA confidential note is added.
Tag pushA new tag is pushed to the repository.
PipelineA pipeline status changed.
Wiki pageA wiki page is created or updated.
DeploymentA deployment starts or finishes.
AlertA new, unique alert is recorded.
Group mention in publicA group is mentioned in a public context.
Group mention in privateA group is mentioned in a confidential context.
VulnerabilityA new, unique vulnerability is recorded.

Trigger notifications for group mentions

Introduced in GitLab 16.4.

To trigger a notification event for a group mention, use @<group_name> in:

  • Issue and merge request descriptions
  • Comments on issues, merge requests, and commits

Troubleshooting

GitLab for Slack app does not appear in the list of integrations

The GitLab for Slack app might not appear in the list of integrations. To have the GitLab for Slack app on your self-managed instance, an administrator must enable the integration. On GitLab.com, the GitLab for Slack app is available by default.

The GitLab for Slack app is enabled at the project level only. Support for the app at the group and instance levels is proposed in issue 391526.

Project or alias not found

Some Slack commands must have a project full path or alias and fail with the following error if the project cannot be found:

GitLab error: project or alias not found

As a workaround, ensure:

Slash commands return /gitlab failed with the error "dispatch_failed" in Slack

Slash commands might return /gitlab failed with the error "dispatch_failed" in Slack. To resolve this issue, ensure an administrator has properly configured the GitLab for Slack app settings on your self-managed instance.

Notifications are not received to a channel

If you’re not receiving notifications to a Slack channel, ensure:

The App Home does not display properly

If the App Home does not display properly, ensure your app is up to date.