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 within a specified project and repository. The Update Pull Request operation allows users to modify an existing pull request's title and description.
Typical use cases include:
- Automating updates to pull request metadata as part of CI/CD pipelines.
- Synchronizing pull request information from external systems.
- Programmatically managing pull requests without manual intervention in the Bitbucket UI.
For example, you might update the title and description of a pull request after running automated tests or code analysis tools that generate new summary information.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication: "Personal Access Token" or "Basic Auth". |
| Project | The key of the Bitbucket project containing the repository. |
| Repository | The slug (identifier) of the repository within the project. |
| Pull Request ID | The numeric ID of the pull request to update. |
| Title | The new title for the pull request. |
| Description | The new description text for the pull request (optional). |
Output
The node outputs JSON data representing the updated pull request object returned by the Bitbucket Data Center API. This typically includes fields such as the pull request ID, title, description, state, author, reviewers, and other metadata reflecting the current state of the pull request after the update.
No binary data output is produced by this operation.
Dependencies
- Requires access to a Bitbucket Data Center instance with API enabled.
- Requires either a personal access token or basic authentication credentials configured in n8n.
- The node uses the Bitbucket REST API endpoints under
/rest/api/1.0/projects/{projectKey}/repos/{repositorySlug}/pull-requests/{pullRequestId}for updating pull requests.
Troubleshooting
- Authentication errors: Ensure the provided API token or basic auth credentials have sufficient permissions to update pull requests in the target project and repository.
- Invalid Pull Request ID: Verify that the pull request ID exists and belongs to the specified project and repository.
- Missing required parameters: The
titleandpullRequestIdare mandatory; missing these will cause errors. - API request failures: Network issues or incorrect server URLs can cause request failures. Check the Bitbucket server URL configuration and network connectivity.
- Version conflicts: The update payload includes a version number (hardcoded as 1 in this implementation). If the pull request has been updated concurrently, the API may reject the update due to version mismatch. Retrying with the correct version may be necessary.
Error messages from the node will generally indicate "Bitbucket Data Center API request failed" followed by the specific error message from the API.