GitLab

Manage projects, merge requests, and CI/CD pipelines via the GitLab API.

Detail	Value
Category	Dev Tools
Base URL	https://gitlab.com/api
Authentication	Bearer Token
Endpoints	6
Connector key	gitlab

Using GitLab in a workflow

1. Go to Connections and click New Connection.
2. Pick GitLab from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET /projects	List projects
GET /projects/{id}	Get a project
GET /projects/{id}/merge_requests	List merge requests
POST /projects/{id}/merge_requests	Create a merge request
GET /projects/{id}/issues	List project issues
GET /projects/{id}/pipelines	List CI/CD pipelines

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /projects

List projects

Detail	Value
Operation ID	devtools.listProjects
Method	GET
Path	/projects

Parameters

Name	Location	Type	Required
membership	query	boolean	No
per_page	query	integer	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your GitLab connection from the Connection dropdown.
3. In the Operation dropdown, select devtools.listProjects.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream GitLab API reference.

GET /projects/{id}

Get a project

Detail	Value
Operation ID	devtools.getProject
Method	GET
Path	/projects/{id}

Parameters

Name	Location	Type	Required
id	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your GitLab connection from the Connection dropdown.
3. In the Operation dropdown, select devtools.getProject.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream GitLab API reference.

GET /projects/{id}/merge_requests

List merge requests

Detail	Value
Operation ID	devtools.listMergeRequests
Method	GET
Path	/projects/{id}/merge_requests

Parameters

Name	Location	Type	Required
id	path	string	Yes
state	query	string	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your GitLab connection from the Connection dropdown.
3. In the Operation dropdown, select devtools.listMergeRequests.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream GitLab API reference.

POST /projects/{id}/merge_requests

Create a merge request

Detail	Value
Operation ID	devtools.createMergeRequest
Method	POST
Path	/projects/{id}/merge_requests

Parameters

Name	Location	Type	Required
id	path	string	Yes

Request Body

Field	Type
source_branch	string
target_branch	string
title	string

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your GitLab connection from the Connection dropdown.
3. In the Operation dropdown, select devtools.createMergeRequest.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream GitLab API reference.

GET /projects/{id}/issues

List project issues

Detail	Value
Operation ID	devtools.listIssues
Method	GET
Path	/projects/{id}/issues

Parameters

Name	Location	Type	Required
id	path	string	Yes
state	query	string	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your GitLab connection from the Connection dropdown.
3. In the Operation dropdown, select devtools.listIssues.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream GitLab API reference.

GET /projects/{id}/pipelines

List CI/CD pipelines

Detail	Value
Operation ID	devtools.listPipelines
Method	GET
Path	/projects/{id}/pipelines

Parameters

Name	Location	Type	Required
id	path	string	Yes
status	query	string	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your GitLab connection from the Connection dropdown.
3. In the Operation dropdown, select devtools.listPipelines.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream GitLab API reference.