GitLab Extended

Extended GitLab node

Actions18

Branch Actions
File Actions
- Get
- List
Issue Actions
- Create
- Get
Merge Request Actions
Pipeline Actions
Raw API Actions
- Request

Overview

This node interacts with GitLab's API to manage merge requests and other GitLab resources. Specifically, the "Get Many" operation for the "Merge Request" resource retrieves a list of merge requests from a specified GitLab project.

Common scenarios where this node is beneficial include:

Automating retrieval of all or a subset of merge requests for reporting or monitoring.
Integrating GitLab merge request data into workflows for further processing or notifications.
Fetching merge requests in bulk to analyze their status, authors, or related metadata.

For example, you might use this node to fetch the latest 50 merge requests on a project to generate a dashboard showing open and recently closed merge requests.

Properties

Name	Meaning
Return All	Whether to return all merge requests or only up to a given limit. Options: `true` or `false`.
Limit	Maximum number of merge requests to return when "Return All" is set to `false`. Must be at least 1. Default is 50.

Output

The node outputs an array of JSON objects representing merge requests retrieved from GitLab. Each object corresponds to a single merge request and contains fields as returned by the GitLab API, such as merge request ID, title, description, state, author, creation date, and more.

No binary data output is produced by this operation.

Dependencies

Requires an API key credential for authenticating with GitLab.
The node expects configuration of the GitLab project either by numeric project ID or by owner and project name.
Uses internal helper functions to make authenticated HTTP requests to GitLab's REST API.

Troubleshooting

Common issues:
- Incorrect or missing API credentials will cause authentication failures.
- Providing an invalid project identifier (ID or owner/name) will result in errors fetching merge requests.
- Setting "Return All" to false but not specifying a valid "Limit" may cause unexpected results or errors.
Error messages:
- "Unknown resource: mergeRequest": This indicates the resource parameter was not recognized; ensure it is correctly set to "mergeRequest".
- "The "oldLine" parameter must be a non-negative number.": Although not relevant for "Get Many", this error can appear if parameters for other operations are misconfigured.
- Network or API errors from GitLab will typically propagate; verify network connectivity and API token permissions.