Skip to main content
The GitLab toolkit lets EKB agents and workflows work with GitLab projects through a Personal Access Token (PAT). You can inspect projects, manage merge requests and issues, view branches and repository files, review commit history, and monitor CI/CD pipelines and jobs.

Prerequisites

  • An active GitLab account on GitLab.com or a self-hosted GitLab instance.
  • Permission to create a GitLab Personal Access Token.
  • A Personal Access Token with the api scope.
  • Access to at least one GitLab project.
  • An EKB project where you can configure an agent or workflow.
  • GitLab permissions appropriate for the actions you intend to run.
Never place the Personal Access Token in workflow inputs, prompts, screenshots, tickets, logs, or documentation. The toolkit does not grant additional GitLab permissions; all actions run with the access level of the account that owns the configured token.

Setup

1

Open GitLab

Sign in to GitLab.com or your organization’s self-hosted GitLab instance.
2

Create a Personal Access Token

Go to User Settings → Access Tokens, create a token with the api scope, and copy it securely.
3

Identify a GitLab project

Open the project you want to use. You can use its numeric project ID or URL-encoded project path. You can also use List Projects or Search Projects to find accessible projects.
4

Add GitLab in EKB

Open the required EKB agent or workflow, add the GitLab toolkit, and select a GitLab action.
5

Create a GitLab connection

Enter the GitLab Instance URL for self-hosted GitLab, then securely provide the Personal Access Token. Leave the Instance URL empty when using GitLab.com.
6

Configure an action

Start with List Projects to confirm access. Use the returned project ID in later actions such as Get Project, List Merge Requests, or List Issues.
7

Run and verify

Run the agent or workflow step and confirm that GitLab project data is returned successfully.

Available tools

Project Management

Merge Request Management

Issue Management

Branch and File Management

CI/CD Pipelines

Use cases

  • Find an accessible GitLab project and use its project ID in subsequent actions.
  • Review an open merge request by retrieving its details, diffs, and commits, then posting review feedback.
  • Create and update issues automatically from monitoring or deployment workflows.
  • Inspect repository branches, files, and commit history to understand recent changes.
  • Investigate failed CI/CD pipelines by identifying the pipeline, its status, and affected jobs.

Troubleshooting