AtlasWork, planned itself.

The AI-native, all-in-one work platform. Tasks, projects, CRM, contracts, and analytics in one calm workspace.

  • SOC 2 II
  • ISO 27001
  • HIPAA
  • GDPR

Product

  • Overview
  • PDF tools
  • People & HR
  • Integrations
  • Marketplace
  • Pricing

Resources

  • Guides
  • Docs
  • API reference
  • Support
  • Changelog
  • Status

Company

  • About
  • Careers
  • Press
  • Contact

Legal & trust

  • Trust center
  • Security
  • Privacy
  • Terms
  • DPA
  • GDPR
  • SLA
  • Refunds
Atlas, a product by wrxstack.com·© 2026 wrxstack·All rights reserved
Made in India
Skip to documentation
AtlasDocs
Back to Atlas

Start here

  • Overview

Developer

  • REST API
  • MCP (AI agents)
  • SDKs
  • Quick actions

Connect

  • Connectors
  • Integrations

Reference

  • Keyboard shortcuts
  • Module reference

GitLabDeveloper

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

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

1

Open GitLab application settings

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

Screenshot placeholder
2

Create a new application

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

Screenshot placeholder
3

Pick scopes

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

Screenshot placeholder
4

Save and copy credentials

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

Screenshot placeholder
5

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.

Screenshot placeholder

Required scopes and permissions

Full API accessapi
Read user identityread_user
Read repository contentread_repository

Setup checklist

  1. Create the provider app in a sandbox or development workspace.
  2. Add the Atlas redirect URL to the provider app configuration.
  3. Copy the client id, client secret, or API key.
  4. Paste the credentials into the Atlas connector settings page.
  5. Click Connect and complete the provider sign-in screen.
  6. 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

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

Ready to connect GitLab?

Paste the credentials you copied above into the live connector page.

Open the connector page