GitLab Extended icon

GitLab Extended

Extended GitLab node
Join our community

Actions66

Overview

This node operation manages labels on a GitLab merge request. It allows users to add or remove one or more labels from a specified merge request within a project. This is useful for automating issue tracking, categorizing merge requests, or triggering workflows based on label changes.

Practical examples include:

  • Automatically adding a "reviewed" label when a merge request passes automated tests.
  • Removing a "needs work" label once the requested changes are addressed.
  • Managing labels in bulk as part of a CI/CD pipeline or project management automation.

Properties

Name Meaning
Authentication Choose between using saved credentials ("Credential") or entering custom connection details ("Custom").
GitLab Server Base URL of your GitLab instance (only shown if using Custom authentication). Default: https://gitlab.com.
Access Token Personal access token with API permissions (only for Custom authentication).
Project Owner Namespace or owner of the project; ignored if Project ID is set (Custom authentication).
Project Name Project slug or name; ignored if Project ID is set (Custom authentication).
Project ID Numeric project ID; takes precedence over owner and name if provided (Custom authentication).
Merge Request IID The internal ID (IID) of the merge request to modify labels on. Must be a positive number.
Labels Comma-separated list of label names to add or remove.
Action Whether to add or remove the specified labels. Options: Add, Remove. Default: Add.

Output

The node outputs JSON data representing the updated state of the merge request's labels after the operation. This typically includes the full merge request object returned by the GitLab API, reflecting the current labels applied.

No binary data output is involved.

Dependencies

  • Requires access to a GitLab instance, either via saved credentials or custom connection parameters.
  • Needs an API access token with sufficient permissions to read and modify merge requests and their labels.
  • No additional external services beyond GitLab are required.

Troubleshooting

  • Invalid Merge Request IID: If the IID is missing or not positive, the node will error. Ensure the IID corresponds to an existing merge request.
  • Authentication Errors: Using incorrect or expired tokens will cause authorization failures. Verify the access token and permissions.
  • Project Identification Issues: If both Project ID and Project Owner/Name are missing or incorrect, the node cannot locate the merge request. Provide valid project identification.
  • Label Format: Labels must be comma-separated strings. Incorrect formatting may cause API errors.
  • API Rate Limits: Frequent label updates might hit GitLab API rate limits; consider handling retries or delays.

Links and References

Discussion