Skip to main content

GitLab integration

GitLab is a good fit when merge requests and review activity are part of how your team understands contribution. ClarityLoop connects to GitLab through a token plus webhooks so merge request activity can be used as real context inside feedback and growth conversations.

What GitLab helps with​

Use GitLab when you want to bring:

  • merge request examples
  • review discussion context
  • meaningful engineering delivery evidence

into ClarityLoop without relying on memory or vague summaries.

Who sets it up​

Workspace owners connect GitLab for the workspace.

Before you start​

You need:

  • a GitLab base URL
  • a GitLab group access token or bot personal access token with api scope
  • permission to configure webhooks for the projects or groups you want to sync

This works for both gitlab.com and self-hosted GitLab instances.

How to connect GitLab​

  1. Open Workspace Settings > Integrations.
  2. Find GitLab.
  3. Enter the GitLab base URL and access token.
  4. Save the connection.

ClarityLoop then gives you a webhook URL and secret. You can reopen the integration and use View instructions later if you need them again.

Configure GitLab webhooks​

In GitLab, for each project or group you want connected:

  1. Open Settings > Webhooks.
  2. Paste the webhook URL from ClarityLoop.
  3. Paste the secret token from ClarityLoop.
  4. Enable Merge request events and Note events.
  5. Save the webhook.

How people use it​

Once connected, GitLab context becomes useful when merge request work should support:

  • clear feedback examples
  • 1:1 conversations about delivery or collaboration
  • goals and follow-up actions tied to real work

Use it for the merge requests that matter, not every change in the repo.

How ClarityLoop uses GitLab data​

  • Automatic context: supported GitLab flows can bring merge request details and review collaboration into ClarityLoop so feedback opportunities and growth signals are grounded in shared engineering work.
  • Manual linking: people can also attach a merge request directly in feedback, 1:1s, requests, or goals when that MR is the best example.

Use it well​

  • use a bot or group token that is stable enough to manage over time
  • reconnect and replace the token if you rotate credentials
  • keep PR Quick Action enabled if you want GitLab merge requests to surface the Add to ClarityLoop action

FAQs​

Can we use self-hosted GitLab?

Yes. Enter your own GitLab base URL during setup.

What if we rotate the token?

Reconnect GitLab and save the replacement token.

Can we view the webhook details again later?

Yes. Use View instructions in the GitLab integration row.

How do we disconnect it?

Remove the integration in ClarityLoop and delete the webhook in GitLab if you no longer want events sent.

Next steps​