Actions50
- Branch Actions
- Commit Actions
- Issue Actions
- Project Actions
- Pull Request Actions
- Repository Actions
- Tag Actions
- File Actions
- User Actions
- Webhook Actions
Overview
This node interacts with the Bitbucket Data Center API to retrieve all tags from a specified project repository. It is useful for scenarios where you need to list or process all tags in a repository, such as automating release workflows, auditing tags, or synchronizing tag data with other systems.
For example, you might use this node to:
- Fetch all tags in a repository to trigger deployment pipelines based on tag names.
- Generate reports of all tags created in a project repository.
- Synchronize tags with an external system for version tracking.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate API requests. Options: "Personal Access Token", "Basic Auth" |
| Return All | Whether to return all tag results or limit the number returned |
| Limit | Maximum number of tag results to return (only applicable if "Return All" is false). Range: 1-500 |
Output
The output is a JSON array where each element represents a tag object retrieved from the Bitbucket Data Center API. Each tag object typically contains details such as the tag name, start point (commit or branch it points to), and optional message associated with the tag.
If multiple tags are returned, they are flattened into a single array.
No binary data output is produced by this operation.
Dependencies
- Requires access to a Bitbucket Data Center instance.
- Requires either a Personal Access Token or Basic Authentication credentials configured in n8n.
- The node uses the Bitbucket Data Center REST API endpoints under
/rest/api/1.0/projects/{projectKey}/repos/{repositorySlug}/tags.
Troubleshooting
- Authentication errors: Ensure that the provided API token or basic auth credentials have sufficient permissions to read tags in the target repository.
- Empty results: Verify that the specified project key and repository slug are correct and that tags exist in the repository.
- API request failures: Network issues or incorrect server URLs can cause failures. Confirm the Bitbucket Data Center server URL is correctly set in credentials.
- Limit vs Return All: If you expect more than the default limit (50) tags, enable "Return All" to fetch all tags; otherwise, increase the "Limit" property up to 500.
Common error messages include:
Bitbucket Data Center API request failed: ...ā Indicates an issue with the API call, often due to authentication or endpoint problems.The operation "getAll" is not supported for resource "tag"ā Should not occur here since "getAll" is supported; if seen, verify node configuration.