Developer

GitLab

Pull GitLab merge requests, issues, and pipeline status into Atlas so engineering progress lives next to project plans.

AuthOAuth 2.0UpdatesReal-timeAvailable

What this connector does

Link merge requests and issues to Atlas tasks.
Read project, branch, and pipeline metadata for evidence rows.
Watch merge request events to update Atlas task state.
Post Atlas task links back to merge request descriptions.

Before you begin

You are an owner or maintainer of the GitLab group that contains the projects to connect.
Your GitLab plan allows OAuth applications at the group or instance level.
You can create webhooks on projects.

Get your credentials

Open GitLab application settings

Open User Settings, Applications for a personal install, or Group Settings, Applications for a group-wide install. gitlab.com applications

Create a new application

Name it Atlas Connector. Set Redirect URI to https://YOUR-ATLAS-HOST/oauth/callback/gitlab.

Pick scopes

Select api and read_user. For self-hosted GitLab also confirm the Atlas hostname is allowed by your CSP.

Save and copy credentials

Click Save application. Copy the Application ID and Secret into the Atlas GitLab connector settings page.

Set the GitLab base URL

If you use self-managed GitLab, set the base URL to https://gitlab.example.com in the Atlas connector settings before clicking Connect.

Required scopes and permissions

Full API accessapi

Read user identityread_user

Read repository contentread_repository

Setup checklist

Create the provider app in a sandbox or development workspace.
Add the Atlas redirect URL to the provider app configuration.
Copy the client id, client secret, or API key.
Paste the credentials into the Atlas connector settings page.
Click Connect and complete the provider sign-in screen.
Run Test connection from the connector page to verify health.

Troubleshooting

invalid_grant
The OAuth code expired or was already used. Retry the connect flow once.
redirect_uri does not match
GitLab compares the Redirect URI string exactly. Update the application and retry.
self-managed CORS errors
Add YOUR-ATLAS-HOST to GitLab Admin Area, Settings, Network, Outbound requests allowlist.

Webhooks

Atlas creates a project-scoped webhook secret per connected project and validates the GitLab token header on every event.

Events Atlas listens for

Push events
Merge request events
Issue events
Pipeline events

Provider docs: https://docs.gitlab.com/ee/user/project/integrations/webhooks.html

Disconnect and data deletion

Click Disconnect on the Atlas GitLab connector page.
Open Applications and remove the Atlas Connector authorization.
Delete the project webhook in Project Settings, Webhooks if you want to stop event delivery immediately.

Once you have the credentials above, paste them into the live connector page to finish connecting GitLab.

Open the GitLab connector page