Bitbucket Data Center

Overview

This node interacts with the Bitbucket Data Center API to manage repositories within projects. Specifically, the Repository - Get operation retrieves detailed information about a single repository in a specified project.

Common scenarios where this node is beneficial include:

• Automating retrieval of repository metadata for reporting or auditing.
• Integrating repository details into CI/CD pipelines or dashboards.
• Fetching repository info as part of larger workflows involving multiple Bitbucket resources.

For example, you can use this node to get the current settings and status of a repository before triggering deployment steps or to verify repository existence and properties during automated project setup.

Properties

Output

The output is a JSON object representing the repository's details as returned by the Bitbucket Data Center API. It typically includes fields such as repository name, slug, description, visibility (public/private), project association, and other metadata.

No binary data is output by this operation.

Example output structure (simplified):

{
  "slug": "my-repo",
  "name": "My Repository",
  "description": "Repository description",
  "public": false,
  "project": {
    "key": "PROJ",
    "name": "Project Name"
  },
  ...
}

Dependencies

• Requires access to a Bitbucket Data Center instance with API enabled.
• Needs 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}.

Troubleshooting

• Error: "Bitbucket Data Center API request failed"
  This indicates an issue with the API call, possibly due to incorrect credentials, insufficient permissions, or wrong project/repository identifiers.
  Resolution: Verify that the API credentials are correct and have appropriate access rights. Confirm that the project key and repository slug exist and are spelled correctly.

• Empty or missing repository data
  Could be caused by specifying a non-existent repository slug or project key.
  Resolution: Use the node's load options to select valid projects and repositories to avoid typos.

• Authentication failures
  Ensure that the selected authentication method matches the provided credentials and that tokens/passwords are valid.

Links and References

• Bitbucket Data Center REST API Documentation
• Bitbucket Data Center Authentication
• n8n Documentation on Credentials