Feature Marketplace · Connectors

GitLab Connector

GitLab DevOps platform. Syncs projects, issues, merge requests, and users via the REST API v4 with PRIVATE-TOKEN authentication and webhook support for real-time updates.

Connectors connector Dev Tools

What syncs

The GitLab records STRAX brings into your hub.

Each kind of record is mapped once to your company model in the STRAX hub, then kept current in every system that needs it. Where GitLab announces changes, they arrive as they happen.

Projects

Projects the token holder is a member of, including visibility, branch, and activity statistics.

Issues

Issues across all projects visible to the token, including labels, milestone, and assignee.

Changes arrive as they happen

Merge Requests

Merge requests across all projects visible to the token, including branches, merge status, and draft state.

Changes arrive as they happen

Users

Active users on the GitLab instance.

GitLab data in your own SQL Server, then wherever it is needed.

STRAX is a self-hosted integration platform. The GitLab records land in the STRAX hub, a SQL Server database on your own servers, where your reports, portals and workflows read them. From there the hub delivers them to the other systems you connect, whether those run on SQL Server, MySQL, PostgreSQL or another API. STRAX signs in to GitLab with an API key that you provide, stored encrypted.

About this listing

Version1.0.1
AuthorSTRAX
CategoryConnectors
Published2026-07-15

What's inside

Connector profile 1

Free listing

Install it from Feature Marketplace inside STRAX

Open Feature Marketplace

In your STRAX installation, open Feature Marketplace from the navigation.

Find "GitLab Connector"

Search or browse to this listing and review the contents disclosure; every package shows what it contains before anything runs.

Install

Choose Install, or "Customise with AI" to adapt the package to your environment first. No licence is needed for free listings.

Back to the catalogue →

See it on your own systems.

A demo takes an hour, on your data landscape rather than ours.