Pacia Intelligence

Code integration

GitLab and Pacia

GitLab connects with nothing more than a read-only personal access token. There is no OAuth application to register and no admin consent flow to chase — a deliberate scope decision so multi-provider support could ship without a procurement conversation.

Talk to us

What Pacia reads from GitLab

  • Merge requests, approvals, review comments and merges

  • Project and namespace metadata

  • Pipeline outcomes where available

Connecting it

  1. Create a token in GitLab 2 min

    Settings → Access Tokens → create a personal access token with the read_api scope.

  2. Paste it into Pacia 1 min

    Connect GitLab via Access Token, supplying the namespace or group, the project, and the token.

  3. Let the backfill run ~15 min

    Up to 180 days of merge request history pages through per project.

Limits, stated up front

Every integration page on this site lists what the integration does not do. Finding that out during a trial is worse for both of us than finding it out now.

  • No live webhooks in this phase — GitLab projects refresh on a 20-minute reconcile cycle, or instantly when you press refresh.

  • Full webhook support is a planned fast-follow, not a blocker to using GitLab today.

  • The token is AES-256-GCM encrypted at rest and never returned in any API response.

What this unlocks

Connect GitLab and see your own data

Talk to us