Skip to main content
Connector ID gitlab The GitLab source reads projects, groups, group members, project members, issues, merge requests, CI pipelines, commits, and branches from the GitLab REST API. It uses an HTTP manifest. This connector is in preview. It targets API version v4.

Configuration

Connection testing sends GET /projects?membership=true&per_page=100.

Resources

All resources are selected by default. Top-level resources list projects and groups. Child resources fan out across their respective parent entities. projects queries /projects with membership=true to retrieve only projects accessible to the authenticated token. groups queries /groups with min_access_level=10 to restrict listing to groups where the user holds membership. group_members retrieves direct members of each accessible group. project_members lists direct members and access levels for each project. issues extracts issues including issue numbers, state, labels, assignees, and timestamps. merge_requests captures merge request lifecycle events, branch details, status flags, and reviewers. pipelines reads CI/CD pipeline executions, status outcomes, commit references, and timestamps. commits lists Git repository commits, authored and committed timestamps, messages, and author metadata. branches captures branch names, commit references, default branch status, and push protection rules.

Modes

All resources support full reads. Use full upsert to refresh rows or full replace to reconcile active records. issues, merge_requests, and pipelines support incremental reads: Each incremental resource shares a single durable watermark across projects. The 300-second overlap window re-reads a short lookback span to capture records modified during the previous scan. All other resources run in full read mode.

Limitations

commits executes a full read for every project on every run. Git commit timestamps reflect author or commit dates on branches rather than repository merge dates. Filtering commits with since would silently skip older commits merged after the watermark. Incremental resources share a single watermark across projects. If a run is interrupted before scanning all projects, remaining projects advance with the watermark on subsequent runs.

Behavior

  • Auth. Every request sends either a PRIVATE-TOKEN header when auth_method is private_token or an Authorization: Bearer header when set to oauth_token.
  • Pagination. Requests use standard RFC 5988 Link headers (rel="next") with per_page=100.
  • Rate limiting. Requests pace at 5 requests per second with adaptive backoff honoring RateLimit-Remaining and RateLimit-Reset response headers. HTTP 429 responses back off using Retry-After.
  • Scope confinement. Top-level queries enforce membership=true on projects and min_access_level=10 on groups to prevent accidental traversals of public GitLab.com entities.
  • Every resource includes a raw remainder column preserving unmapped upstream payload fields.