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 manage projects and other related resources. Specifically, for the Project resource with the Get All operation, it retrieves a list of all projects available in the Bitbucket Data Center instance.
Common scenarios where this node is beneficial include:
- Automating project inventory retrieval for reporting or auditing.
- Integrating Bitbucket projects into other workflows or dashboards.
- Synchronizing project data with external systems.
For example, you could use this node to fetch all projects and then iterate over them to trigger builds, update permissions, or generate documentation automatically.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate API requests. Options: "Personal Access Token", "Basic Auth" |
| Return All | Whether to return all projects or limit the number of results |
| Limit | Maximum number of projects to return (only applicable if "Return All" is false). Range: 1-500 |
Output
The output is a JSON array where each element represents a project object retrieved from the Bitbucket Data Center API. Each project object typically includes fields such as project key, name, description, and other metadata as provided by the API.
Example structure of one project item (simplified):
{
"key": "PROJ",
"name": "Project Name",
"description": "Description of the project",
// ... other project details
}
No binary data is output by this operation.
Dependencies
- Requires access to a Bitbucket Data Center instance.
- Requires an API authentication credential configured in n8n, either:
- A personal access token credential, or
- Basic authentication credentials.
- The node uses the Bitbucket Data Center REST API endpoint specified in the credentials configuration.
Troubleshooting
- Authentication errors: Ensure that the API credentials are correctly configured and have sufficient permissions to read projects.
- API request failures: Network issues or incorrect server URL in credentials can cause failures. Verify connectivity and correct server address.
- Limit and pagination: If not returning all results, ensure the limit is set appropriately. To get all projects, enable "Return All".
- Unexpected empty results: Confirm that the authenticated user has access to projects in the Bitbucket Data Center instance.
Common error message example:
Bitbucket Data Center API request failed: <error message>
This indicates an issue with the API call, possibly due to invalid credentials, insufficient permissions, or network problems.