Actions66
- Branch Actions
- File Actions
- Group Actions
- Issue Actions
- Merge Request Actions
- Pipeline Actions
- Project Actions
- Raw API Actions
- Release Actions
- Tag Actions
Overview
This node enables interaction with GitLab's Releases resource, specifically supporting the deletion of a release by its tag name. It is useful in scenarios where you want to automate the management of project releases on GitLab, such as cleaning up outdated or incorrect releases programmatically.
For example, you might use this node to delete a release identified by a specific tag after a failed deployment or when a release is no longer relevant.
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 for GitLab. 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) The tag name of the release to delete. This identifies which release will be removed. |
Output
The node outputs JSON data representing the response from the GitLab API after attempting to delete the specified release. Typically, a successful deletion returns an empty response or confirmation status. If the deletion fails, error information will be included.
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 manage releases in the target project.
- If using saved credentials, the node expects those credentials to be configured properly in n8n.
- For custom authentication, the user must provide the GitLab server URL, access token, and project identification details.
Troubleshooting
Common Issues:
- Invalid or missing tag name: The "Tag Name" property must be provided and correspond to an existing release tag.
- Insufficient permissions: The access token used must have API rights to delete releases in the project.
- Incorrect project identification: When using custom authentication, ensure that the project is correctly identified by either Project ID or both Project Owner and Project Name.
- Network or URL errors: Verify the GitLab server URL is correct and accessible.
Error Messages:
"tagName must not be empty": Indicates the required tag name parameter was not provided.- HTTP 404 Not Found: The specified release tag does not exist.
- HTTP 401 Unauthorized or 403 Forbidden: Authentication failed or insufficient permissions.
Resolution Steps:
- Double-check the tag name spelling and existence in the project.
- Confirm the access token has the necessary scopes.
- Validate project identifiers and server URL.
- Test connectivity to the GitLab server outside n8n to rule out network issues.