Actions29
Overview
This node interacts with the Bitbucket Data Center API to retrieve commit information from repositories within specified projects. Specifically, the "Commit - Get All" operation fetches multiple commits from a given repository and project.
Common scenarios where this node is beneficial include:
- Auditing or reviewing recent changes in a repository.
- Automating reports on commit history for development teams.
- Integrating commit data into dashboards or other tools for monitoring codebase activity.
For example, you can use this node to get the latest 50 commits from a repository to analyze recent development progress or trigger workflows based on commit metadata.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication: "Personal Access Token" or "Basic Auth". |
| Project | The key of the project containing the repository to query commits from. |
| Return All | Whether to return all commits or limit the number of results. |
| Limit | Maximum number of commits to return if "Return All" is false (1 to 500). |
Output
The output is a JSON array where each element represents a commit object retrieved from the Bitbucket Data Center API. Each commit object typically includes details such as commit ID, author, message, date, and other metadata provided by the API.
No binary data is output by this node.
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}/commits.
Troubleshooting
Error: "Bitbucket Data Center API request failed"
This indicates an issue with the API call, possibly due to incorrect credentials, insufficient permissions, or network issues. Verify your authentication credentials and ensure the Bitbucket server URL is correct and accessible.Empty results or missing commits
Ensure that the specified project key and repository slug are correct and that the repository contains commits. Also, check if the "Return All" and "Limit" parameters are set appropriately.Operation not supported errors
If you attempt operations other than "get" or "getAll" on commits, the node will throw an error because only these operations are implemented for the Commit resource.