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 creating a new tag in a GitLab repository. It is useful for automating versioning, marking releases, or labeling specific points in your project's history. For example, you can create tags to mark release versions like v1.0.0 or to label important commits for deployment.
Typical use cases include:
- Automatically tagging commits after successful CI/CD pipeline runs.
- Creating annotated tags with messages describing the tag purpose.
- Managing tags programmatically as part of a larger GitLab automation workflow.
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. 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 existing branch or commit SHA from which to create the new tag. Default is main. |
| Tag Name | The name of the tag to create (e.g., v1.0.0). |
| Message | Optional message describing the tag (annotated tag). |
Output
The node outputs JSON data representing the created tag object returned by the GitLab API. This typically includes fields such as:
name: The tag name.message: The tag message if provided.target: The commit SHA or branch the tag points to.- Other metadata about the tag creation.
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication token with appropriate permissions to create tags in the target GitLab project.
- Supports either stored credentials or custom authentication parameters.
- If using custom authentication, the user must provide the GitLab server URL, access token, and project identification (either by ID or owner/name).
Troubleshooting
- Invalid or missing project identification: Ensure that either a valid numeric project ID is provided or both project owner and project name are specified when using custom authentication.
- Insufficient permissions: The access token must have API rights to create tags in the project.
- Invalid tag name: The tag name must be a valid Git reference name; avoid special characters or empty strings.
- API errors: Network issues or incorrect GitLab server URLs can cause request failures. Verify the server URL and network connectivity.
- Malformed JSON in optional fields: Although not applicable here, other operations may require valid JSON inputs; ensure correct formatting.