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 integrates with Bitbucket Data Center's API to perform various operations on different resources such as projects, repositories, pull requests, branches, commits, users, tags, files, webhooks, and issues. Specifically for the Issue resource, the node supports operations like creating, deleting, getting, and updating issues.
However, it is important to note that issue operations are not directly supported by the Bitbucket Data Center API itself. Instead, the node throws an error advising to use Jira integration for issue management. This means that while the node exposes issue-related operations in its interface, attempting to execute them will result in an error indicating that Bitbucket Data Center does not support these operations natively.
Practical Use Case
- For managing Bitbucket projects, repositories, pull requests, branches, commits, etc., this node can be used to automate workflows such as:
- Retrieving repository details.
- Creating or updating pull requests.
- Managing branches and tags.
- Handling webhooks.
- For issue tracking, users should integrate with Jira or another dedicated issue tracker instead of using this node's issue operations.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication: "Personal Access Token" or "Basic Auth". |
| Project | The project key to work with (required). |
| Repository | The repository slug within the project (required). |
| Issue ID | The numeric ID of the issue to get, update, or delete (required for those operations). |
Output
- The output is a JSON array containing the response data from the Bitbucket Data Center API for the requested operation.
- For most resources, the output reflects the structure returned by the Bitbucket API endpoints, such as project details, repository info, pull request data, etc.
- For the Issue Get operation specifically, the node will throw an error because Bitbucket Data Center does not support issue operations directly.
- No binary data output is produced by this node.
Dependencies
- Requires access to a Bitbucket Data Center server with API enabled.
- Requires credentials configured in n8n for either:
- Personal Access Token authentication, or
- Basic Authentication.
- The node uses the Bitbucket Data Center REST API endpoints under
/rest/api/1.0and other relevant paths.
Troubleshooting
Issue Operations Not Supported Error:
When performing any operation on the Issue resource, the node throws:"Issue operations are not directly supported in Bitbucket Data Center. Please use Jira integration instead."
This is expected behavior because Bitbucket Data Center does not provide native issue management APIs. To manage issues, integrate with Jira or another issue tracker.API Request Failures:
Errors like"Bitbucket Data Center API request failed: <message>"indicate problems with API calls. Common causes include:- Incorrect or missing credentials.
- Insufficient permissions for the authenticated user.
- Invalid project key or repository slug.
- Network connectivity issues.
To resolve:
- Verify credentials and permissions.
- Check that the project and repository exist.
- Ensure the Bitbucket Data Center server URL is correct and accessible.
Missing Required Parameters:
Operations require certain parameters (e.g., projectKey, repositorySlug, issueId). Missing these will cause errors. Make sure all required fields are provided.
Links and References
- Bitbucket Data Center REST API Documentation
- Jira Integration for Issue Tracking (recommended for issue management)