GitLab Extended icon

GitLab Extended

Extended GitLab node
Join our community

Actions66

Overview

The node "GitLab Extended" provides extended integration with GitLab's API, allowing users to manage various GitLab resources programmatically within n8n workflows. Specifically for the Release - Create operation, this node enables creating a new release in a GitLab project by specifying details such as the release tag, name, description, and optional assets.

This is beneficial in scenarios where automated deployment pipelines or release management processes are needed. For example, after a successful build or merge, you can automatically create a release in GitLab with relevant metadata and asset links, streamlining your DevOps workflow.

Properties

Name Meaning
Authentication Choose between using saved credentials ("Credential") or providing 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.
Tag Name (Required) Release tag name identifying the release version.
Name (Required) The display name of the release.
Description Optional detailed description of the release.
Assets Optional JSON string defining asset links associated with the release (e.g., binaries, URLs). Must be valid JSON if provided.

Output

The node outputs an array of JSON objects representing the created release(s) returned from the GitLab API. Each object contains all standard GitLab release fields, including but not limited to:

  • tag_name: The tag associated with the release.
  • name: The release name.
  • description: The release description.
  • assets: An object containing asset links related to the release.
  • Other metadata such as creation date, author, and commit information.

No binary data output 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 create releases on the target project.
  • If using saved credentials, the node expects a configured API key credential in n8n.
  • If using custom authentication, the user must provide the GitLab server URL, access token, and project identification parameters manually.

Troubleshooting

  • Invalid JSON in 'Assets' parameter: If the assets field contains malformed JSON, the node will throw an error indicating invalid JSON. Ensure that the JSON string is correctly formatted.
  • Missing required parameters: The tagName and name properties are mandatory. Omitting these will cause the node to fail.
  • Authentication errors: If the access token lacks necessary permissions or is invalid, API requests will fail. Verify token scopes and validity.
  • Project identification issues: When using custom authentication, ensure that either a valid numeric project ID is provided or both project owner and project name are specified correctly.
  • API rate limits or network issues: Standard GitLab API limitations apply; handle retries or check connectivity if requests fail unexpectedly.

Links and References

Discussion