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 interacts with the Bitbucket Data Center API to perform various operations related to pull requests within a specified project and repository. Specifically, the "Get" operation for the "Pull Request" resource retrieves detailed information about a single pull request identified by its ID.
Common scenarios where this node is beneficial include:
- Automating workflows that require fetching the status or details of a specific pull request.
- Integrating Bitbucket pull request data into other systems or dashboards.
- Triggering downstream processes based on pull request metadata.
For example, you might use this node to get the current state of a pull request before deciding whether to merge it automatically or notify a team.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate API requests. Options: Personal Access Token, 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 retrieve. |
Output
The output is a JSON object representing the pull request's details as returned by the Bitbucket Data Center API. This includes fields such as title, description, source and destination branches, author, reviewers, status, and other metadata associated with the pull request.
No binary data is output by this operation.
Dependencies
- Requires access to a Bitbucket Data Center instance.
- Requires credentials for authentication, either via a personal access token or basic authentication.
- The node expects the Bitbucket server URL to be configured in the credentials.
- Uses the Bitbucket REST API endpoints under
/rest/api/1.0/projects/{projectKey}/repos/{repositorySlug}/pull-requests/{pullRequestId}.
Troubleshooting
- Authentication errors: Ensure that the provided personal access token or basic auth credentials are valid and have sufficient permissions to access the project and repository.
- Invalid project or repository: Verify that the project key and repository slug are correct and exist in your Bitbucket instance.
- Pull Request not found: Confirm that the pull request ID exists in the specified repository.
- API request failures: Network issues or incorrect server URLs can cause failures. Check connectivity and credential configuration.
- Error message format: Errors from the API are wrapped and presented as
Bitbucket Data Center API request failed: <message>. Review the message for specifics.