GitLab ExtendedInstall

Overview

This node interacts with GitLab's API to manage and retrieve information about releases within a GitLab project. Specifically, the "Get Many" operation under the "Release" resource fetches multiple release records from a specified project.

Typical use cases include:

• Listing all releases of a project for reporting or auditing.
• Automating workflows that depend on release data, such as deployment pipelines or notifications.
• Integrating GitLab release information into other systems or dashboards.

For example, you might use this node to fetch all releases of a project to display them in a custom dashboard or to trigger downstream automation based on new releases.

Properties

Output

The node outputs an array of JSON objects representing GitLab releases. Each object corresponds to a single release and contains fields as returned by the GitLab API for releases, typically including:

• tag_name: The tag associated with the release.
• name: The name of the release.
• description: Description text of the release.
• created_at, released_at: Timestamps related to the release.
• assets: Links and other asset information attached to the release.

If the node is configured to return all releases, it will paginate through all available pages and output the complete list.

No binary data is output 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 appropriate permissions to read releases from the target project.
• 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's REST API.

Troubleshooting

• Invalid or missing project identification: If neither a valid numeric project ID nor both project owner and project name are provided (when using custom authentication), the node may fail to locate the project. Ensure these parameters are correctly set.
• Authentication errors: Using an invalid or expired access token will cause authorization failures. Verify the token has sufficient API scope and is active.
• Invalid JSON in assets parameter: When creating or updating releases, if the assets field contains malformed JSON, the node throws an error indicating invalid JSON. Correct the JSON format before retrying.
• API rate limits: Fetching many releases repeatedly may hit GitLab API rate limits. Consider enabling "Return All" judiciously or limiting the number of results.
• Network issues: Connectivity problems to the GitLab server will cause request failures. Check network access and server availability.

Common error messages:

• "tagName must not be empty": Occurs if the required tag name parameter is missing during create/update operations.
• "Unknown resource": Indicates an unsupported resource was requested; ensure the resource is set to "release" for this operation.

Links and References

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