Actions29
Overview
This node interacts with the Bitbucket Data Center API to perform various operations on Bitbucket resources. Specifically, for the Commit - Get operation, it retrieves detailed information about a specific commit in a repository within a project.
Common scenarios where this node is beneficial include:
- Automating retrieval of commit details for auditing or reporting.
- Integrating commit data into CI/CD pipelines or dashboards.
- Fetching commit metadata to trigger downstream workflows based on commit content or author.
For example, you can use this node to get the full details of a commit by its ID/hash in a given repository and project, enabling automated analysis or notifications when certain commits are made.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication: either "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 selected project. |
| Commit ID | The unique ID or hash of the commit to retrieve information for. |
Output
The output is a JSON object representing the commit details as returned by the Bitbucket Data Center API. This includes metadata such as commit message, author, date, parents, and other commit-specific information.
The output structure corresponds directly to the Bitbucket API response for a commit resource, typically including fields like:
id: Commit hash.author: Information about the commit author.message: Commit message.parents: Parent commits.authorTimestampandcommitterTimestamp: Timestamps related to the commit.- Other relevant commit metadata.
No binary data is output by this node.
Dependencies
- Requires access to a Bitbucket Data Center instance.
- Requires credentials configured in n8n for authentication, either via a personal access token or basic authentication.
- The node uses the Bitbucket Data Center REST API endpoints under
/rest/api/1.0.
Troubleshooting
- Authentication errors: Ensure that the provided credentials (personal access token or basic auth) have sufficient permissions to access the specified project and repository.
- Invalid Project or Repository: Verify that the project key and repository slug are correct and exist in your Bitbucket Data Center instance.
- Commit not found: If the commit ID does not exist in the specified repository, the API will return an error. Double-check the commit hash.
- API request failures: Network issues or incorrect server URL configuration may cause request failures. Confirm the Bitbucket server URL is correctly set in credentials.
- Unsupported operations: Only "get" and "getAll" operations are supported for commits; attempting other operations will result in errors.
Links and References
- Bitbucket Data Center REST API Documentation
- Bitbucket Commit Resource API (specific endpoint for commit details)