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 interacts with GitLab's API to manage tags within a GitLab project. Specifically, the "Get" operation for the "Tag" resource retrieves detailed information about a specific tag in a repository. This is useful when you want to fetch metadata about a particular tag, such as its commit reference, message, or creation details.
Common scenarios include:
- Automating release workflows by fetching tag details before deployment.
- Integrating GitLab tag data into other systems or dashboards.
- Validating the existence and properties of a tag before performing further actions.
Example: You have a CI/CD pipeline that triggers on new tags. Before running deployment steps, you use this node to get the tag's details to verify it matches expected criteria.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose between using saved credentials ("Credential") or specifying 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. |
| Ref | The branch or commit SHA from which the tag was created. Defaults to "main". Required for some operations but not specifically for "Get". |
| Tag Name | The exact name of the tag to retrieve. This is required for the "Get" operation. |
Output
The output is a JSON object representing the tag's details as returned by the GitLab API. It typically includes fields such as:
name: The tag name.message: Optional message associated with the tag.target: The commit SHA the tag points to.commit: Detailed commit information including author, date, and message.- Other metadata related to the tag.
This output allows downstream nodes or workflows to consume tag information programmatically.
The node does not output binary data for this operation.
Dependencies
- Requires access to a GitLab instance via its REST API.
- Needs either saved credentials or custom authentication parameters including an API access token.
- No additional external services are required beyond GitLab itself.
- Proper permissions on the GitLab API token are necessary to read repository tags.
Troubleshooting
- Invalid or missing tag name: If the "Tag Name" property is empty or incorrect, the node will fail to find the tag. Ensure the tag exists and the name is spelled correctly.
- Authentication errors: Using invalid or expired tokens will cause authorization failures. Verify the access token has sufficient API scope.
- Project identification issues: When using custom authentication, ensure that either the numeric project ID is provided or both project owner and project name are correctly set.
- API rate limits: Frequent requests may hit GitLab API rate limits; consider adding delays or caching results.
- Network connectivity: Ensure the GitLab server URL is reachable from the n8n environment.
Common error messages:
- "404 Not Found": The specified tag or project does not exist.
- "401 Unauthorized": Invalid or missing authentication token.
- "400 Bad Request": Malformed request, possibly due to invalid parameters.
Resolving these usually involves verifying input parameters and authentication settings.