GitLab + Datagrid integration

Overview

What is GitLab: GitLab is a DevSecOps platform combining source code management, CI/CD pipelines, security scanning, and project planning in one application. It's available as multi-tenant SaaS (GitLab.com), self-managed (on-premises), or a single-tenant dedicated instance.

How to integrate GitLab with Datagrid

Connect GitLab to Datagrid by setting up the integration, authenticating with a Personal Access Token, configuring recurring data pulls, and reviewing the data sync details. Here are the steps:

Set up the integration

Before you start, make sure you have an active GitLab account with the necessary permissions, a GitLab API key in the form of a Personal Access Token, and the GitLab data you want to import selected.

1. Click + Create in the top left of the Datagrid interface

2. Select Connect Apps

3. Search for GitLab in the integration list

4. Connect your GitLab account and grant Datagrid the requested permissions when prompted

5. Click Next

6. Select the data objects to import (e.g., Issues, Merge Requests, Pipelines)

7. Click Start first import to begin the initial sync

Authenticate access

Datagrid's GitLab integration requires a GitLab API key in the form of a Personal Access Token. Generate one from your GitLab account settings. Datagrid requires read-only access.

For team integrations, you can also consider a Group Access Token. Group Access Tokens on GitLab.com require a Premium or Ultimate subscription.

Configure recurring data pulls

Once the first import is complete, you can set the sync schedule for the dataset.

1. Open your GitLab dataset from the left side panel

2. Click … in the top right of the dataset view

3. Click Edit pipeline to rename the integration (optional)

4. Click the Schedule button next to Import configuration

5. Set the frequency: daily, weekly, or monthly

6. Specify the time of day for the pull

7. Optionally define downtime periods when sync should not run

8. Click Update to save

Review data sync details

The list below summarizes the data objects Datagrid syncs from GitLab.

• Issues — GitLab → Datagrid, issue data from GitLab projects and groups

• Merge Requests — GitLab → Datagrid, merge request data from GitLab

• Pipelines — GitLab → Datagrid, pipeline data from GitLab

• Users — GitLab → Datagrid, user data from GitLab

• Projects — GitLab → Datagrid, project data from GitLab

• Groups — GitLab → Datagrid, group data from GitLab

Sync runs on the schedule you configure. Datagrid requires read-only access. It does not write data back to GitLab.

Why use GitLab with Datagrid

Teams use this integration to bring software development lifecycle data into Datagrid for recurring analysis and reporting. Here's why you need to use GitLab with Datagrid:

• Automated data collection: Datagrid pulls GitLab data into datasets on a schedule, without requiring manual export.

• Backlog and project visibility across projects and groups: GitLab data is consolidated into Datagrid datasets, making it easier to analyze issues, merge requests, pipelines, and project activity across multiple projects and groups.

• Reporting on development activity: Datagrid brings GitLab issues, merge requests, pipelines, users, projects, and groups into one place for analysis and reporting.

• Scheduled, hands-off syncs: Configure daily, weekly, or monthly syncs with optional downtime windows. Teams receive updated datasets without running queries or exporting CSVs.

• Single dataset for development data: Combine issues, merge requests, pipelines, users, projects, and groups in one queryable dataset for analysis and reporting.

What you can build with the GitLab Datagrid integration

Once GitLab data is available in Datagrid, teams can use it for reporting and operational visibility across projects, groups, and pipelines:

• Project progress tracking: Monitor the status of issues and merge requests to understand project velocity and identify bottlenecks.

• Code quality analysis: Use merge requests and pipeline data to analyze code review activity and development process health.

• CI/CD pipeline monitoring: Visualize pipeline success rates and durations using scheduled data pulled from GitLab into Datagrid datasets.

• Team contribution reporting: Analyze activity across users, projects, and groups to understand contributions and development trends.

• Risk visibility: Monitor open issues and related project activity to identify potential risks earlier.

Resources and documentation

• GitLab REST API reference — Core API usage, authentication, pagination, and request encoding

• GitLab REST API resources index — Directory of all available endpoints by resource type

• GitLab Personal Access Token documentation — Token creation, scopes, rotation, and usage tracking

• GitLab OAuth 2.0 API — Authorization code, device grant, and password credential flows

• GitLab webhook configuration — Webhook setup, security, secret token validation, and event subscriptions

• GitLab webhook events reference — Full JSON payload schemas for all project and group event types

Frequently asked questions

What permissions does Datagrid need to access GitLab data?

Datagrid requires read-only access. A Personal Access Token with read access provides access to the GitLab data the token owner can access. For team integrations, you can also use a Group Access Token for group-scoped access. Datagrid does not require write permissions.

How often can Datagrid sync data from GitLab?

Datagrid's scheduled integration supports daily, weekly, or monthly data pulls. You specify the time of day and can define downtime windows when sync should not run.

Which GitLab data objects does the integration currently support?

The Datagrid GitLab integration syncs six data objects: Issues, Merge Requests, Pipelines, Users, Projects, and Groups. GitLab's API exposes additional objects that are not yet available in the integration. Contact support@datagrid.ai to request additional objects.

Do some GitLab features require a paid subscription to access via the integration?

Yes. Several GitLab data objects and fields are gated by plan tier. Epics, the Issue weight field, Group Webhooks, and Group Access Tokens on GitLab.com require a Premium or Ultimate subscription. The Issue health_status field requires Ultimate. Data objects available on the Free tier — Issues, Merge Requests, Pipelines, Users, Projects, and Groups — work with the Datagrid integration regardless of GitLab plan.

What should I do if my GitLab connection stops working?

Verify that your Personal Access Token still has the necessary permissions and that the associated account retains access to the target projects. If the token was revoked, you must generate a new token and re-authorize. If the issue persists, contact support@datagrid.ai.