Skip to main content

​
Connection setup

Connect GitLab with a personal access token to use GitLab actions in Flow automations. The token’s scopes, the GitLab tier, and the account’s GitLab permissions determine which actions can succeed. This Preview connection supports GitLab.com, self-managed GitLab, and GitLab Dedicated instances. Flow verifies the connection with a read-only projects request before saving it.

​
Prerequisites

  • A GitLab instance reachable over HTTPS.
  • A Flow admin who can manage integrations.
  • A GitLab account with access to the projects that automations need.
  • A GitLab personal access token with the api scope.
  • The admin_mode scope if the selected GitLab instance requires Admin Mode for administrator API requests.
Use a token created for Flow. Do not reuse a personal token that also grants access for unrelated scripts or tools.

​
Provider setup

Create the token in GitLab before you connect Flow.
1

Open GitLab access tokens.

In GitLab, open your user preferences and select Access tokens.
2

Create a personal access token.

Give the token a name that identifies Flow and the automation environment.
3

Set an expiration date.

Choose a date that matches your organization’s credential rotation policy.
4

Select the required scopes.

Add api. If the selected GitLab instance requires Admin Mode for administrator API requests, also add admin_mode.
5

Create and copy the token.

GitLab shows the token once. Copy it and enter it only in the Flow connection form.
The api scope gives broad REST API access through the token owner’s GitLab permissions. Restrict the GitLab administrator account, project memberships, and instance settings to the automation work that Flow must perform.

​
Verify provider access

Before you connect Flow, confirm that the token can list projects on the selected GitLab instance. Replace the example host with your GitLab instance origin.
A 200 response with a JSON array means GitLab accepts the token and exposes the selected instance to the account. An empty array is valid. A 401, 403, or 404 response means Flow cannot verify the connection.

​
Connect in Flow

1

Open Integrations.

Search for GitLab. This connection is available to organizations with Preview access.
2

Select Connect.

Name the connection and choose which teams can access it.
3

Enter the GitLab instance URL.

Use the HTTPS origin for the instance, for example https://gitlab.example.com. Do not include /api/v4, a path, query, or fragment.
4

Enter the personal access token.

Paste the token you created in GitLab.
5

Complete verification.

Flow checks that the token can list projects on the selected instance.
6

Enable Automations for the intended team.

Open the connection and enable Automations for each team that needs it. Sharing a connection does not enable automations.
7

Select the permitted actions.

Review action access and approval requirements before using the connection in an automation.

​
Capabilities

Use the connection to manage GitLab issues, projects, merge requests, pipelines, users, group members, project members, vulnerabilities, and instance audit events. Each action still depends on the token owner’s GitLab permissions and the selected instance’s tier.

​
GitLab tier requirements

Most GitLab actions work on Free, Premium, and Ultimate tiers when the token owner has the required GitLab role. These actions require an upgraded tier:

​
Automation connector reference

Use the generated GitLab action reference for supported actions, inputs, and risk tiers.

​
Sync and behavior

This connection runs actions when an automation requests them. It does not sync Knowledge or Assets, or receive GitLab webhooks. Flow verifies the token with a read-only project list request during setup. That check proves only that the selected token can reach the selected GitLab instance. GitLab can still reject later actions when the token lacks a project, group, user, admin, or tier permission. To rotate the token, create a replacement token for the same GitLab instance and reconnect in Flow. Test the actions your automations need with the replacement before you revoke the old token.

​
Troubleshooting