Project integrations

You can integrate your GitLab projects with other applications. Integrations are like plugins, and give you the freedom to add functionality to GitLab.

View project integrations

Prerequisites:

  • You must have at least the Maintainer role for the project.

To view the available integrations for your project:

  1. On the top bar, select Menu > Projects and find your project.
  2. On the left sidebar, select Settings > Integrations.

You can also view and manage integration settings across all projects in an instance or group. For a single project, you can choose to inherit the instance or group configuration, or provide custom settings.

note
Instance and group-based integration management replaces service templates, which were removed in GitLab 14.0.

Manage SSL verification

By default, the SSL certificate for outgoing HTTP requests is verified based on an internal list of Certificate Authorities. This means the certificate cannot be self-signed.

You can turn off SSL verification in the configuration settings for webhooks and some integrations.

Available integrations

You can configure the following integrations.

Integration Description Integration hooks
Asana Add commit messages as comments to Asana tasks. No
Assembla Manage projects. No
Atlassian Bamboo CI Run CI/CD pipelines with Atlassian Bamboo. Yes
Bugzilla Use Bugzilla as the issue tracker. No
Buildkite Run CI/CD pipelines with Buildkite. Yes
Campfire Connect to chat. No
Confluence Workspace Use Confluence Cloud Workspace as an internal wiki. No
Custom issue tracker Use a custom issue tracker. No
Datadog Trace your GitLab pipelines with Datadog. Yes
Discord Notifications Send notifications about project events to a Discord channel. No
Drone CI Run CI/CD pipelines with Drone. Yes
Emails on push Send commits and diff of each push by email. No
EWM Use IBM Engineering Workflow Management as the issue tracker. No
External wiki Link an external wiki. No
Flowdock Send notifications from GitLab to Flowdock flows. No
GitHub Obtain statuses for commits and pull requests. No
Google Chat Send notifications from your GitLab project to a room in Google Chat. No
Harbor Use Harbor as the container registry. No
irker (IRC gateway) Send IRC messages. No
Jenkins Run CI/CD pipelines with Jenkins. Yes
JetBrains TeamCity CI Run CI/CD pipelines with TeamCity. Yes
Jira Use Jira as the issue tracker. No
Mattermost notifications Send notifications about project events to Mattermost channels. No
Mattermost slash commands Perform common tasks with slash commands. No
Microsoft Teams notifications Receive event notifications. No
Packagist Keep your PHP dependencies updated on Packagist. Yes
Pipelines emails Send the pipeline status to a list of recipients by email. No
Pivotal Tracker Add commit messages as comments to Pivotal Tracker stories. No
Prometheus Monitor application metrics. No
Pushover Get real-time notifications on your device. No
Redmine Use Redmine as the issue tracker. No
Slack application Use Slack’s official GitLab application. No
Slack notifications Send notifications about project events to Slack. No
Slack slash commands Enable slash commands in a workspace. No
Unify Circuit Send notifications about project events to Unify Circuit. No
Webex Teams Receive events notifications. No
YouTrack Use YouTrack as the issue tracker. No
ZenTao Use ZenTao as the issue tracker. No

Project webhooks

You can configure a project webhook to listen for specific events like pushes, issues, or merge requests. When the webhook is triggered, GitLab sends a POST request with data to a specified webhook URL.

Learn more about webhooks.

Push hooks limit

Introduced in GitLab 12.4.

If a single push includes changes to more than three branches or tags, integrations supported by push_hooks and tag_push_hooks events aren’t executed.

You can change the number of supported branches or tags by changing the push_event_hooks_limit application setting.

Troubleshooting integrations

Some integrations use hooks to integrate with external applications. To confirm which ones use integration hooks, see the available integrations. Learn more about troubleshooting integration hooks.

Test Failed. Save Anyway error

Some integrations fail with an error Test Failed. Save Anyway when you set them up on uninitialized repositories. This error occurs because the integration uses push data to build the test payload, and there are no push events in the project.

To resolve this error, initialize the repository by pushing a test file to the project and set up the integration again.

Contribute to integrations

To add a new integration, see the Integrations development guide.