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 repositories and related resources within a specified project. The "Get All" operation for the "Repository" resource retrieves multiple repositories from a given project, either returning all available repositories or limiting the number of results.
Common scenarios where this node is beneficial include:
- Automating repository management workflows by fetching lists of repositories in a project.
- Integrating Bitbucket repository data into other systems or dashboards.
- Performing batch operations on repositories after retrieving their details.
Practical example:
- You want to list all repositories under a specific project to generate reports or trigger further automation based on repository metadata.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate API requests. Options: Personal Access Token, Basic Auth. |
| Project | The key of the project whose repositories you want to retrieve. |
| Return All | Whether to return all repositories or limit the number of results. |
| Limit | Maximum number of repositories to return if "Return All" is false (1 to 500). |
Output
The output is a JSON array where each item represents a repository object retrieved from the Bitbucket Data Center API. Each repository object typically includes properties such as repository slug, name, description, visibility (public/private), and other metadata provided by the API.
No binary data output is produced by this operation.
Dependencies
- Requires access to a Bitbucket Data Center instance with appropriate API credentials.
- Needs an API authentication token configured in n8n, either as a personal access token or basic authentication credentials.
- The node uses the Bitbucket Data Center REST API endpoints under
/rest/api/1.0/projects/{projectKey}/repos.
Troubleshooting
- Authentication errors: Ensure that the API credentials (personal access token or basic auth) are correctly configured and have sufficient permissions to access the project repositories.
- Project not found or empty results: Verify that the specified project key exists and contains repositories.
- Limit exceeded: The "Limit" property must be between 1 and 500; setting values outside this range may cause errors.
- API request failures: Network issues or incorrect server URLs can cause request failures. Check connectivity and server configuration.
- Error message example:
Bitbucket Data Center API request failed: <error message>indicates an issue with the API call; review the error message for details.