Actions29
Overview
This node interacts with the Bitbucket Data Center API to manage pull requests within a specified project repository. Specifically, the "Get All" operation for the "Pull Request" resource retrieves multiple pull requests from a given repository in a project.
Common scenarios where this node is beneficial include:
- Automating the retrieval of all open or closed pull requests for reporting or auditing purposes.
- Integrating pull request data into dashboards or other workflow automations.
- Triggering downstream processes based on the list of pull requests, such as notifications or code quality checks.
For example, a user might configure this node to fetch all pull requests from a repository to analyze their status or merge readiness.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication: "Personal Access Token" or "Basic Auth". |
| Project | The key of the project containing the repository to work with. |
| Return All | Whether to return all pull requests or limit the number of results. |
| Limit | Maximum number of pull requests to return (applicable if "Return All" is false). |
Output
The output is a JSON array where each element represents a pull request object retrieved from the Bitbucket Data Center API. Each pull request object contains details such as ID, title, source and destination branches, author, state, and other metadata as provided by the API.
No binary data output is produced by this operation.
Dependencies
- Requires access to a Bitbucket Data Center instance.
- Requires either a personal access token or basic authentication credentials configured in n8n.
- The node uses the Bitbucket Data Center REST API endpoints under
/rest/api/1.0/projects/{projectKey}/repos/{repositorySlug}/pull-requests. - The "Project" and "Repository" must exist and be accessible with the provided credentials.
Troubleshooting
- Authentication errors: Ensure that the API credentials (personal access token or basic auth) are valid and have sufficient permissions to read pull requests.
- Empty results: Verify that the specified project key and repository slug are correct and contain pull requests.
- API request failures: Network issues or incorrect server URL configuration can cause request failures. Confirm the Bitbucket Data Center server URL is correctly set in credentials.
- Limit parameter ignored: If "Return All" is enabled, the "Limit" parameter is ignored; disable "Return All" to use the limit.
- Error message example:
Bitbucket Data Center API request failed: <error message>
This indicates an issue with the API call; check credentials, network connectivity, and input parameters.