GitLab ExtendedInstall

Overview

The node "GitLab Extended" provides extended integration with GitLab, allowing users to manage various GitLab resources programmatically within n8n workflows. Specifically for the Release - Get operation, this node fetches details of a specific release identified by its tag name from a GitLab project.

This operation is useful when you want to retrieve metadata about a particular release in your GitLab repository, such as its name, description, assets, and other related information. Practical scenarios include:

• Automating deployment pipelines that need to verify or log release details.
• Synchronizing release information with external systems like documentation sites or issue trackers.
• Triggering notifications or further workflow steps based on release data.

Properties

Output

The output JSON contains the detailed information of the requested GitLab release corresponding to the specified tag name. Typical fields returned include:

• tag_name: The tag associated with the release.
• name: The release name.
• description: Description text of the release.
• created_at, released_at: Timestamps related to the release.
• author: Information about the user who created the release.
• assets: Links and metadata about release assets (binaries, links, etc.).
• Other metadata fields as provided by the GitLab Releases API.

The node does not output binary data for this operation; it returns structured JSON data representing the release.

Dependencies

• Requires an active connection to a GitLab instance, either via saved credentials or custom parameters.
• Needs an API access token with sufficient permissions to read releases in the target project.
• The node uses internal helper functions to build the API request URL and handle pagination if needed.
• No additional external dependencies beyond standard n8n environment and GitLab API access.

Troubleshooting

• Common issues:

  • Invalid or missing tag name will cause the node to fail because the tag name is required.
  • Incorrect project identification (wrong project ID, owner, or name) can lead to "not found" errors.
  • Insufficient API permissions on the access token may result in authorization errors.
  • Malformed or missing authentication details when using custom authentication.

• Error messages:

  • "tagName must not be empty": Ensure the "Tag Name" property is provided and not blank.
  • HTTP 404 Not Found: Verify the project and tag exist in GitLab.
  • HTTP 401 Unauthorized or 403 Forbidden: Check that the access token has the necessary scopes/permissions.
  • "Invalid JSON in 'assets' parameter": Relevant for create/update operations, ensure JSON syntax is correct if assets are used.

• Resolution tips:

  • Double-check all input parameters, especially the tag name and project identifiers.
  • Confirm the access token's scopes include reading releases.
  • Use the default GitLab server URL unless connecting to a self-hosted instance.
  • When using custom authentication, verify all required fields are correctly filled.

Links and References

• GitLab Releases API Documentation
• GitLab Personal Access Tokens
• n8n Documentation - Creating Custom Nodes