GitLab Extended icon

GitLab Extended

Extended GitLab node

Overview

The node "GitLab Extended" provides extended integration with GitLab's API, allowing users to manage various GitLab resources programmatically within n8n workflows. Specifically, the Release - Update operation enables updating an existing release in a GitLab project by modifying its name, description, and associated assets.

This operation is useful when you want to automate release management tasks such as correcting release notes, adding or updating asset links (e.g., binaries, documentation), or renaming releases without manually interacting with the GitLab UI.

Practical example:

  • Automatically update release descriptions after a CI/CD pipeline completes testing.
  • Add new downloadable assets to an existing release when new build artifacts are available.
  • Rename a release tag for clarity or consistency across projects.

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 for authentication. 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.
Tag Name The tag name identifying the release to update. Required.
Name The new name for the release. Required.
Description Release description text. Optional field to provide detailed release notes or information.
Assets JSON string representing asset links associated with the release. Optional. Should be valid JSON.

Output

The output is a JSON array containing the updated release data returned from the GitLab API. Each item corresponds to one input item processed and includes all standard fields of a GitLab release object, such as:

  • tag_name: The release tag name.
  • name: The release name.
  • description: The release description.
  • assets: Object containing asset links related to the release.

If multiple input items are processed, the output contains multiple such objects.

No binary data is produced by this operation.


Dependencies

  • Requires access to a GitLab instance, either the public https://gitlab.com or a self-hosted GitLab server.
  • Requires an API access token with sufficient permissions to update releases in the target project.
  • The node supports two authentication modes:
    • Using saved credentials configured in n8n.
    • Providing custom connection parameters including server URL, access token, and project identification.
  • No additional external dependencies beyond the GitLab API.

Troubleshooting

  • Invalid JSON in 'Assets' parameter:
    If the JSON string provided for assets is malformed, the node throws an error indicating invalid JSON. Ensure the JSON is correctly formatted before running the workflow.

  • Missing required parameters:
    The tagName and name properties are mandatory. Omitting these will cause the node to throw an error.

  • Authentication errors:
    If the access token is invalid or lacks necessary permissions, the API request will fail. Verify that the token has appropriate scopes for release management.

  • Project identification issues:
    When using custom authentication, ensure that either the numeric project ID is provided or both project owner and project name are specified correctly. Incorrect or missing project identifiers will cause API errors.

  • API rate limits or network issues:
    Network connectivity problems or hitting GitLab API rate limits can cause failures. Check network access and consider retry logic if needed.


Links and References

Discussion