Actions29
Overview
This node integrates with the Bitbucket Data Center API, enabling users to automate and manage various aspects of their Bitbucket Data Center instance directly within n8n workflows. It supports multiple resources such as projects, repositories, pull requests, branches, commits, issues, and users, allowing for operations like creating, updating, deleting, retrieving single or multiple items, and specific actions like merging pull requests or forking repositories.
Common scenarios where this node is beneficial include:
- Automating repository management tasks (e.g., creating or updating repositories).
- Managing project lifecycles by creating or deleting projects.
- Handling pull request workflows such as creating, merging, or declining pull requests.
- Retrieving commit histories or branch information for audit or reporting purposes.
- Fetching user information for integration with other systems.
Practical example:
- Automatically create a new repository in a specified project when a new product is launched.
- Retrieve all open pull requests for a repository and trigger notifications or further automation.
- Merge approved pull requests automatically after passing CI/CD checks.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: "Personal Access Token" or "Basic Auth". |
Output
The node outputs JSON data representing the response from the Bitbucket Data Center API corresponding to the requested resource and operation. The structure varies depending on the resource and operation but generally includes detailed information about projects, repositories, pull requests, branches, commits, or users.
If multiple items are retrieved (e.g., "Get All" operations), the output is an array of objects each representing an individual item.
No binary data output is produced by this node.
Dependencies
- Requires access to a Bitbucket Data Center instance.
- Requires credentials configured in n8n for authentication, either via a personal access token or basic authentication.
- The node uses HTTP requests to interact with the Bitbucket Data Center REST API endpoints.
- No additional external services beyond Bitbucket Data Center are required.
Troubleshooting
Issue: "Bitbucket Data Center API request failed" errors.
- Cause: Could be due to incorrect credentials, network issues, or insufficient permissions.
- Resolution: Verify that the API URL and credentials are correct and have the necessary permissions for the requested operations.
Issue: Operations on "issue" resource throw an error stating they are not supported.
- Cause: Bitbucket Data Center does not support issue operations directly; Jira integration is recommended instead.
- Resolution: Use Jira nodes or integrations for issue tracking functionality.
Issue: Empty results or missing data when fetching projects or repositories.
- Cause: Possibly due to incorrect project keys or repository slugs.
- Resolution: Use the node's load options to select valid projects and repositories to avoid typos.
Issue: Limits on number of returned items.
- Cause: By default, the node may limit results unless "Return All" is enabled.
- Resolution: Enable "Return All" or increase the "Limit" parameter as needed.