Integrations / GitLab

GitLab

GitLab code collaboration and DevOps platform

OAuth 2.0

Indexes

Actions

Events

What Telara does

Capability matrix

Indexes Yes Tracks spend No Discovers shadow AI No Runs actions Yes Real-time events Yes

Before you connect

Prerequisites

A GitLab.com account, or a self-managed GitLab instance Telara can reach.

Owner or Maintainer on the groups and projects you want connected. A Reporter cannot finish this setup.

Vendor setup

Get the credential

Click Connect in Telara

Settings → Integrations → GitLab. Telara sends you to GitLab to approve access. You do not register an OAuth application or set a callback URL.

Approve the groups and projects

On the GitLab consent screen, authorize the groups Telara should see. If you belong to several groups, picking the wrong one is the usual empty-project list.

Token path for self-managed

If your instance cannot use the hosted button, in GitLab open Preferences → Access Tokens (or Group → Settings → Access Tokens). Create a token, copy it once, and paste it in Telara. Grant the permissions this page lists from the catalog — do not copy a permission list from an old wiki. Enter the instance URL on the Connect form.

Permissions Telara requests

api
OAuth 2.0
read_repository
OAuth 2.0
write_repository
OAuth 2.0
read_user
OAuth 2.0

In Telara

Connect in Telara

OAuth 2.0

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

Personal access token

GitLab Personal Access Token or Project/Group Access Token

In Telara, open Settings → Integrations, choose this connector, and paste the token into the field Telara shows.

Fields Telara asks for

Private token

Knowledge

What gets indexed

Resource	Coverage
Repositories	Partial — not every record the vendor holds is synced
Commits	Partial — not every record the vendor holds is synced
Issues	Partial — not every record the vendor holds is synced
Pull requests	Partial — not every record the vendor holds is synced
Code file	Partial — not every record the vendor holds is synced

Sync

Freshness & sync

Resource	Lag	Deletions
Repositories	Up to 1 day	Removed records disappear on the next full sync
Commits	Up to 1 day	Removed records disappear on the next full sync
Issues	Up to 1 day	Removed records disappear on the next full sync
Pull requests	Up to 1 day	Removed records disappear on the next full sync
Code file	Up to 1 day	Removed records disappear on the next full sync

Data handling

Permissions & data handling

The scopes above are the permissions this connector requests. They come from the catalog, not from a hand-written page.

Excluded from semantic search: Repositories, Commits, Issues, Pull requests, Code file.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

Self-managed instances must allow Telara to reach the GitLab API. A reachable GitLab UI is not enough if the API hostname is firewalled.

Some self-managed installs block outbound webhooks; real-time events then wait on the next sync.