GitLab ExtendedInstall

Overview

This node enables managing GitLab tags with extended capabilities. Specifically, the Delete Tag operation allows users to remove a tag from a GitLab project repository. This is useful for cleaning up obsolete or incorrect tags, maintaining repository hygiene, or automating release workflows where tags need to be programmatically deleted.

Practical examples include:

• Automatically deleting a tag after a release rollback.
• Removing tags that were created by mistake during CI/CD pipelines.
• Cleaning up old tags as part of repository maintenance scripts.

Properties

Output

The output is a JSON array containing the response from the GitLab API after attempting to delete the specified tag. Typically, a successful deletion returns an empty object or confirmation status. If the deletion fails, error information will be included in the output.

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 delete tags in the target project.
• The node supports two authentication modes:
  • Using saved credentials configured in n8n.
  • Providing custom connection details including server URL and personal access token directly in the node parameters.

Troubleshooting

• Common Issues:

  • Invalid or insufficient permissions on the access token can cause authorization errors.
  • Incorrect project identification (wrong project ID, owner, or name) may lead to "not found" errors.
  • Specifying a non-existent tag name will result in an error indicating the tag does not exist.

• Error Messages:

  • "404 Not Found" — The tag or project could not be found. Verify the project and tag names/IDs.
  • "401 Unauthorized" or "403 Forbidden" — The access token lacks required permissions. Ensure the token has API scope and rights to delete tags.
  • "Invalid JSON" — Not applicable here since no JSON input is required for deletion, but ensure other parameters are correctly formatted.

• Resolution Tips:

  • Double-check the project identification parameters.
  • Confirm the tag name is correct and exists in the project.
  • Use a personal access token with api scope or equivalent permissions.
  • Test connectivity and permissions outside n8n (e.g., via curl or Postman) to isolate issues.

Links and References

• GitLab API Documentation - Delete a repository tag
• GitLab Personal Access Tokens
• n8n Documentation - Creating Custom Nodes