Project integrations

{{< details >}}

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated

{{< /details >}}

[!note] This page contains user documentation for project integrations. For administrator documentation, see Project integration administration.

You can integrate with external applications to add functionality to GitLab.

You can view and manage integrations for the:

• Instance (GitLab Self-Managed)
• Group

You can use:

• Instance or group default settings for a project integration
• Custom settings for a project or group integration

Manage group default settings for a project integration

Prerequisites:

• You must have the Owner role for the group.

To manage the group default settings for a project integration:

1. In the top bar, select Search or go to and find your group.
2. Select Settings > Integrations.
3. Select an integration.
4. Complete the fields.
5. Select Save changes.

[!warning] This may affect all or most of the subgroups and projects belonging to the group. Review the details below.

If this is the first time you are setting up group settings for an integration:

• The integration is enabled for all subgroups and projects belonging to the group that don't already have this integration configured, if you have the Enable integration toggle turned on in the group settings.
• Subgroups and projects that already have the integration configured are not affected, but can choose to use the inherited settings at any time.

When you make further changes to the group defaults:

• They are immediately applied to all subgroups and projects belonging to the group that have the integration set to use default settings.
• They are immediately applied to newer subgroups and projects, even those created after you last saved defaults for the integration. If your group default setting has the Enable integration toggle turned on, the integration is automatically enabled for all such subgroups and projects.
• Subgroups and projects with custom settings selected for the integration are not immediately affected and may choose to use the latest defaults at any time.

If instance settings have also been configured for the same integration, projects in the group inherit settings from the group.

Only the entire settings for an integration can be inherited. Per-field inheritance is proposed in epic 2137.

Remove a group default setting

Prerequisites:

• You must have the Owner role for the group.

To remove a group default setting:

1. In the top bar, select Search or go to and find your group.
2. Select Settings > Integrations.
3. Select an integration.
4. Select Reset and confirm.

Resetting a group default setting removes integrations that use default settings and belong to a project or subgroup of the group.

Use instance or group default settings for a project integration

Prerequisites:

• You must have the Maintainer or Owner role for the project.

To use instance or group default settings for a project integration:

1. In the top bar, select Search or go to and find your project.
2. Select Settings > Integrations.
3. Select an integration.
4. On the right, from the dropdown list, select Use default settings.
5. Under Enable integration, ensure the Active checkbox is selected.
6. Complete the fields.
7. Select Save changes.

Use custom settings for a project or group integration

Prerequisites:

• You must have the Maintainer or Owner role for the project integration.
• You must have the Owner role for the group integration.

To use custom settings for a project or group integration:

1. In the top bar, select Search or go to and find your project or group.
2. Select Settings > Integrations.
3. Select an integration.
4. On the right, from the dropdown list, select Use custom settings.
5. Under Enable integration, ensure the Active checkbox is selected.
6. Complete the fields.
7. Select Save changes.

Available integrations

The following integrations can be available on a GitLab instance. If an instance administrator has configured an integration allowlist, only those integrations are available.

CI/CD

Integration	Description	Integration hooks
Atlassian Bamboo	Run CI/CD pipelines with Atlassian Bamboo.	{{< yes >}}
Buildkite	Run CI/CD pipelines with Buildkite.	{{< yes >}}
Drone	Run CI/CD pipelines with Drone.	{{< yes >}}
Jenkins	Run CI/CD pipelines with Jenkins.	{{< yes >}}
JetBrains TeamCity	Run CI/CD pipelines with TeamCity.	{{< yes >}}

Event notifications

None of these integrations have integration hooks.

Integration	Description
Campfire	Connect Campfire to chat.
Discord Notifications	Send notifications about project events to a Discord channel.
Google Chat	Send notifications from your GitLab project to a space in Google Chat.
irker (IRC gateway)	Send event notifications to IRC channels.
Matrix notifications	Send notifications about project events to Matrix.
Mattermost notifications	Send notifications about project events to Mattermost channels.
Microsoft Teams notifications	Send event notifications to Microsoft Teams.
Pumble	Send event notifications to a Pumble channel.
Pushover	Send event notifications to your device.
Telegram	Send notifications about project events to Telegram.
Unify Circuit	Send notifications about project events to Unify Circuit.
Webex Teams	Send event notifications to Webex Teams.

Stores

Integration	Description	Integration hooks
Apple App Store Connect	Use GitLab to build and release an app in the Apple App Store.	{{< no >}}
Google Play	Use GitLab to build and release an app in Google Play.	{{< no >}}
Harbor	Use Harbor as the container registry for GitLab.	{{< no >}}
Packagist	Update your PHP dependencies in Packagist.	{{< yes >}}

External issue trackers

The following integrations add links to external issue trackers in the left sidebar in your project. None of these integrations have integration hooks.

Integration	Description	Issue sync	Can create new issues
Bugzilla	Use Bugzilla as an issue tracker.	{{< no >}}	{{< yes >}}
ClickUp	Use ClickUp as an issue tracker.	{{< no >}}	{{< no >}}
Custom issue tracker	Use a custom issue tracker.	{{< no >}}	{{< no >}}
Engineering Workflow Management (EWM)	Use EWM as an issue tracker.	{{< no >}}	{{< yes >}}
Linear	Use Linear as an issue tracker.	{{< no >}}	{{< no >}}
Phorge	Use Phorge as an issue tracker.	{{< no >}}	{{< yes >}}
Redmine	Use Redmine as an issue tracker.	{{< no >}}	{{< yes >}}
YouTrack	Use JetBrains YouTrack as your project's issue tracker.	{{< yes >}}	{{< no >}}

External wikis

The following integrations add links to external wikis in the left sidebar in your project. None of these integrations have integration hooks.

Integration	Description
Confluence Workspace	Use Confluence Cloud Workspace as an internal wiki.
External wiki	Link an external wiki.

Other

Integration	Description	Integration hooks
Asana	Add commit messages as comments to Asana tasks.	{{< no >}}
Assembla	Manage projects with Assembla.	{{< no >}}
Beyond Identity	Verify that GPG keys are authorized by Beyond Identity Authenticator.	{{< no >}}
Datadog	Trace your GitLab pipelines with Datadog.	{{< yes >}}
Diffblue Cover	Automatically write comprehensive, human-like Java unit tests.	{{< yes >}}
Emails on push	Send commits and diffs on push by email.	{{< no >}}
GitGuardian	Reject commits based on GitGuardian policies.	{{< no >}}
GitHub	Receive statuses for commits and pull requests.	{{< no >}}
GitLab for Slack app	Use the native Slack app to receive notifications and run commands.	{{< no >}}
Google Artifact Management	Manage your artifacts in Google Artifact Registry.	{{< no >}}
Google Cloud IAM	Manage permissions for Google Cloud resources with Identity and Access Management (IAM).	{{< no >}}
Jira	Use Jira as an issue tracker.	{{< no >}}
Mattermost slash commands	Run slash commands from a Mattermost chat environment.	{{< no >}}
Pipeline status 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 >}}
Slack slash commands	Run slash commands from a Slack chat environment.	{{< no >}}
Squash TM	Update Squash TM requirements when GitLab issues are modified.	{{< yes >}}

Project webhooks

Some integrations use webhooks for external applications.

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.

For a list of integrations that use webhooks, see Available integrations.

Push hook limit

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

To change the number of supported branches or tags, configure the push_event_hooks_limit setting.

SSL verification

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

You can disable SSL verification when you configure webhooks and some integrations.

Related topics

• Integrations API
• GitLab Developer Portal