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 the Bitbucket Data Center API to manage pull requests, specifically allowing you to add a reviewer to an existing pull request. Adding reviewers is useful in collaborative development workflows where code changes need peer review before merging. For example, when a developer creates a pull request for a feature branch, this node can programmatically assign one or more team members as reviewers to ensure proper code quality checks.
Typical use cases include:
- Automating the assignment of reviewers based on project rules.
- Integrating with CI/CD pipelines to trigger reviews after automated tests pass.
- Managing review assignments dynamically from external systems or chatbots.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication: "Personal Access Token" or "Basic Auth". |
| Project | The key of the Bitbucket project containing the repository and pull request. |
| Pull Request ID | The numeric ID of the pull request to which a reviewer will be added. |
| Username | The username of the user to add as a reviewer to the specified pull request. |
Output
The output JSON contains the response from the Bitbucket Data Center API after adding the reviewer. This typically includes details about the updated pull request participants, including the newly added reviewer and their role.
If the operation succeeds, the output will reflect the updated participant list for the pull request. If it fails, an error message will be returned.
The node does not output binary data.
Dependencies
- Requires access to a Bitbucket Data Center instance with appropriate API permissions.
- Requires either a Personal Access Token or Basic Authentication credentials configured in n8n.
- The node uses Bitbucket's REST API endpoints under
/rest/api/1.0/projects/{projectKey}/repos/{repositorySlug}/pull-requests/{pullRequestId}/participants.
Troubleshooting
Common issues:
- Invalid or missing authentication credentials will cause API request failures.
- Incorrect project key, repository slug, or pull request ID will result in "not found" errors.
- Specifying a username that does not exist or has no access rights may cause errors.
- Insufficient permissions to modify pull request participants will lead to authorization errors.
Error messages:
"Bitbucket Data Center API request failed: ..."indicates a problem with the API call; check credentials and parameters."The operation "addReviewer" is not supported for resource "pullRequest"would indicate a misconfiguration but should not occur here since "addReviewer" is supported.- Network or connectivity issues may also cause request failures.
Resolution tips:
- Verify all input parameters are correct and correspond to existing entities in Bitbucket.
- Ensure the API credentials have sufficient permissions to update pull requests.
- Check network connectivity to the Bitbucket server.
- Enable "Continue On Fail" in the node settings to handle errors gracefully during batch operations.