Bitbucket Data CenterInstall

Overview

This node integrates with the Bitbucket Data Center API to manage webhooks associated with repositories. Specifically, the "Webhook" resource with the "Get All" operation allows users to retrieve a list of all webhooks configured for a given repository within a project.

Common scenarios where this node is beneficial include:

• Auditing or monitoring existing webhook configurations in a repository.
• Automating workflows that depend on webhook setups by fetching current webhook details.
• Integrating Bitbucket webhook data into other systems or dashboards.

For example, a user might want to fetch all webhooks for a repository to verify which external services are notified on repository events or to synchronize webhook configurations across multiple repositories.

Properties

Output

The output is a JSON array where each item represents a webhook object retrieved from the Bitbucket Data Center API. Each webhook object typically includes details such as:

• id: The unique identifier of the webhook.
• name: The name assigned to the webhook.
• url: The URL to which webhook notifications are sent.
• events: An array of event types that trigger the webhook.
• active: A boolean indicating whether the webhook is currently active.

If no webhooks exist, the output will be an empty array.

The node does not output binary data for this operation.

Dependencies

• Requires access to a Bitbucket Data Center instance.
• Requires authentication credentials, either a personal access token or basic authentication credentials.
• The node expects the Bitbucket server URL to be provided via credentials.
• No additional environment variables are required beyond standard n8n credential setup.

Troubleshooting

• Authentication Errors: If the node fails due to authentication issues, verify that the provided personal access token or basic auth credentials are correct and have sufficient permissions to read webhooks.
• API Request Failures: Errors like "Bitbucket Data Center API request failed" indicate network issues, incorrect server URLs, or insufficient permissions. Check connectivity and credential configuration.
• Empty Results: If no webhooks are returned, ensure that the specified project key and repository slug are correct and that webhooks exist for that repository.
• Limit Parameter Ignored: If you expect fewer results but get more, confirm that "Return All" is set to false and the "Limit" parameter is properly configured.

Links and References

• Bitbucket Data Center REST API Documentation - Webhooks
• n8n Documentation - Creating Custom Nodes
• Bitbucket Data Center Authentication