GitLab for Confluence
GitLab for Confluence
Breadcrumbs

Overview

GitLab for Confluence Cloud Overview

GitLab for Confluence Cloud allows teams to display GitLab content directly within Confluence pages, helping engineering, product, and operations teams collaborate more effectively without leaving Confluence.

The integration supports both GitLab SaaS and GitLab On-Premises deployments.

Features

GitLab for Confluence Cloud supports displaying:

  • Projects

  • Merge requests

  • Issues/work items

  • Pipelines

  • Source Code

Using simple GitLab links, the app automatically renders rich previews directly within Confluence pages.

Supported GitLab Deployments

GitLab SaaS

The app fully supports GitLab SaaS using:

https://gitlab.com

GitLab SaaS accounts can connect using either OAuth (a one-click sign-in) or a Personal Access Token.

GitLab On-Premises

GitLab On-Premises instances are also supported.

To use an On-Premises deployment, your GitLab instance must be accessible via a public internet URL so the integration can retrieve repository data securely.

On-Premises deployments must use a Personal Access Token, OAuth is not available for self-managed instances

How It Works

The integration connects to GitLab using either a GitLab Personal Access Token (PAT) or, for GitLab SaaS accounts, OAuth. Both are configured by a Confluence administrator.

Once configured:

  1. Users insert GitLab links into the macro

  2. The app retrieves GitLab metadata

  3. Rich previews are displayed automatically in Confluence

The GitLab macro currently supports:

Content Type

Example

Merge Request

https://gitlab.com/group/project/-/merge_requests/1

Issue

https://gitlab.com/group/project/-/issues/1

Projects

https://gitlab.com/group/project

Pipelines

https://gitlab.com/group/project/-/pipelines/12345678

Source Code

https://gitlab.com/group/project/-/blob/master/README.me

Getting Started

To start using GitLab for Confluence Cloud:

  1. Install the app from the Atlassian Marketplace

  2. Choose an authorization method: connect via OAuth (GitLab SaaS only) or generate a GitLab Personal Access Token

  3. Configure the GitLab connection

  4. Insert GitLab links using the macro

For detailed setup instructions, see:

Permissions

The integration requires a GitLab Personal Access Token with the appropriate permissions.

At minimum, the token should include:

  • read_api

Additional permissions may be required depending on repository visibility and organizational policies.

If you use OAuth instead of a Personal Access Token, GitLab grants read-only access automatically as part of the authorization flow, no manual scope selection is required.

Troubleshooting

If GitLab content does not load correctly, common causes include:

  • Invalid or expired Personal Access Tokens, or an expired or revoked OAuth authorization

  • Incorrect GitLab base URL

  • Missing permissions

  • Expired Marketplace license

See the Troubleshooting guide for more details.

Feedback and Support

We welcome feedback, feature requests, and bug reports.

Please contact us through our support portal for assistance.

You may also be interested in our other Atlassian integrations:

Updated: