Actions50
- Branch Actions
- Commit Actions
- Issue Actions
- Project Actions
- Pull Request Actions
- Repository Actions
- Tag Actions
- File Actions
- User Actions
- Webhook Actions
Overview
The Bitbucket Data Center node allows interaction with the Bitbucket Data Center API to manage various resources such as projects, repositories, pull requests, branches, commits, users, tags, files, webhooks, and issues. However, issue operations are not supported directly by this node because Bitbucket Data Center does not provide an API for issues; instead, it suggests using Jira integration for issue management.
Specifically, the Update Issue operation in this node is not implemented and will throw an error indicating that issue operations should be handled via Jira.
This node is beneficial when automating workflows involving Bitbucket Data Center resources like creating or updating repositories, managing pull requests, branches, tags, files, and webhooks within Bitbucket Data Center environments.
Practical Example
- Automate repository updates or branch creation after a successful build.
- Manage pull request lifecycle events such as approvals or merges.
- Create or update webhooks to trigger external services on repository events.
- Since issue operations are unsupported, integrate Jira nodes for issue tracking automation.
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 update (required). |
| Title | The new title of the issue (required). |
| Content | The content or description of the issue (optional). |
Output
- The node outputs JSON data representing the response from the Bitbucket Data Center API for the requested operation.
- For most resources, this includes detailed objects corresponding to the resource updated or retrieved.
- For the Issue Update operation, the node throws an error and does not produce output data.
- No binary data output is produced by this node.
Dependencies
- Requires access to a Bitbucket Data Center server URL.
- Requires credentials configured in n8n for either:
- Personal Access Token authentication, or
- Basic Authentication.
- The node uses these credentials to authenticate API requests to Bitbucket Data Center.
Troubleshooting
- Issue operations not supported: Attempting to perform any issue operation (including update) will result in an error:
"Issue operations are not directly supported in Bitbucket Data Center. Please use Jira integration instead."
To resolve, use Jira nodes for issue management. - API request failures: Errors like
"Bitbucket Data Center API request failed: <message>"indicate problems with connectivity, authentication, or permissions. Verify credentials and server URL. - Missing required parameters: Ensure all required fields such as Project Key, Repository Slug, and Issue ID are provided.
- Invalid operation for resource: If an unsupported operation is selected for a resource, the node throws an error specifying the unsupported operation.
Links and References
- Bitbucket Data Center REST API Documentation
- Jira Integration for Issue Management
- n8n Documentation on Credentials
Summary: The Bitbucket Data Center node supports many Bitbucket resources but does not support issue operations directly. For updating issues, users must rely on Jira integration. The node requires proper authentication and project/repository context to operate on other resources.