Connect GitLab to Well

From Well, open Connections, find GitLab, and click Connect. Well discovers the OAuth metadata at gitlab.com/api/v4/mcp/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on GitLab's side. No client_id or client_secret to paste; the handshake takes roughly a minute.

Well brings in merge request, pipeline, author, and issue from GitLab and reshapes each entity into your workspace: merge request becomes work item; pipeline becomes build record. Every record arrives with the source identifier preserved, so GitLab stays the source of truth while Well lets you query the data alongside the rest of your stack.

Every GitLab incident, postmortem, or rollback event carries the affected services, which Well joins to the customer entities those services support. Asking "which customers were impacted by last Tuesday's incident" returns the list with severity, restoration time, and any open follow-up actions per customer.

Well watches for updates to merge requests and applies them on the next sync, preserving the original workspace identifier so anything downstream (records tables, conversation history, agent runs) keeps pointing at the right work item. Edits flow in incrementally; nothing is duplicated, and the GitLab source identifier is retained on every revision.

Well combines live GitLab events with periodic reconciliation reads of merge request, pipeline, author, and issue. New rows appear within seconds when GitLab pushes them; periodic reads catch anything a push missed. The first connect backfills history from GitLab in the background.

Open Connections > GitLab in Well and click Disconnect. Well calls GitLab's token revocation endpoint and stops calling GitLab immediately on its side; provider-side propagation to GitLab's admin panel varies by provider. The merge request, pipeline, author, and issue Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.

GitLab records are stored in the region Well operates for your workspace. Specific region details and the steps to change region are available from Support. See /privacy for the current data-handling policy.