GitLab Extended icon

GitLab Extended

Extended GitLab node
Join our community

Actions66

Overview

The node "GitLab Extended" integrates with GitLab's API to perform various operations on GitLab resources. Specifically, the Merge Request - Get Many operation allows users to retrieve a list of merge requests from a specified GitLab project. This is useful for scenarios such as monitoring active merge requests, generating reports, or automating workflows based on merge request data.

Practical examples include:

  • Fetching all open merge requests in a project to trigger notifications.
  • Retrieving a limited number of recent merge requests for review dashboards.
  • Automating status checks or analytics by processing merge request metadata.

Properties

Name Meaning
Authentication Choose between using saved credentials ("Credential") or specifying custom connection details ("Custom").
GitLab Server Base URL of your GitLab instance (e.g., https://gitlab.com). Used only if "Custom" authentication is selected.
Access Token Personal access token with API permissions. Used only if "Custom" authentication is selected.
Project Owner Namespace or owner of the project. Ignored if "Project ID" is set. Used only if "Custom" authentication is selected.
Project Name Project slug or name. Ignored if "Project ID" is set. Used only if "Custom" authentication is selected.
Project ID Numeric project ID. Takes precedence over owner and name if provided. Used only if "Custom" authentication is selected.
Return All Whether to return all merge requests or limit the number of results returned. Default is false (limit applies).
Limit Maximum number of merge requests to return when "Return All" is false. Default is 50.

Output

The output is an array of JSON objects representing merge requests retrieved from the GitLab API. Each object contains detailed information about a merge request, including but not limited to:

  • Merge request ID and IID
  • Title and description
  • Source and target branches
  • Author and assignee information
  • State (opened, closed, merged)
  • Labels applied
  • Timestamps (created, updated, merged dates)
  • Web URL to the merge request

This structured JSON output can be used downstream in workflows for filtering, notifications, reporting, or further API calls.

The node does not output binary data for this operation.

Dependencies

  • Requires access to a GitLab instance, either the public GitLab server (https://gitlab.com) or a self-hosted GitLab server.
  • Requires an API access token with appropriate permissions to read merge requests.
  • Supports two authentication modes: using stored credentials or custom parameters (server URL, access token, project identification).
  • No additional external dependencies beyond standard HTTP requests to GitLab API.

Troubleshooting

  • Invalid or missing project identification: If neither a valid project ID nor both project owner and project name are provided (when using custom authentication), the node may fail to locate the project. Ensure correct project identifiers are supplied.
  • Insufficient API permissions: The access token must have permission to read merge requests. Lack of permissions will cause authorization errors.
  • Rate limiting: GitLab API rate limits may cause errors if too many requests are made in a short time. Consider enabling "Return All" cautiously.
  • Invalid JSON in input fields: For other operations that accept JSON input, invalid JSON strings cause errors. For this operation, inputs are simple types, so less likely.
  • Network or server errors: Check connectivity to the GitLab server URL and validity of the access token.

Common error messages:

  • "Unknown resource" — indicates the resource parameter is incorrect or unsupported.
  • "tagName must not be empty" — specific to tag/release operations, not relevant here.
  • Authorization errors — check token validity and scopes.
  • Validation errors on numeric IDs — ensure positive integers where required.

Links and References

Discussion