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 integrates with the Bitbucket Data Center API to manage webhooks among other resources. Specifically, for the Webhook - Delete operation, it allows users to delete an existing webhook from a specified repository within a project.
Common scenarios where this node is beneficial include:
- Automating the cleanup of outdated or unused webhooks in Bitbucket repositories.
- Managing webhook lifecycle as part of CI/CD pipelines or repository maintenance workflows.
- Removing webhooks that are no longer needed to prevent unnecessary external calls or notifications.
For example, if you have a webhook set up to notify a service on repository changes but want to remove it programmatically when it's no longer required, this node can perform that deletion by specifying the webhook ID.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate API requests. Options: Personal Access Token, Basic Auth. |
| Webhook ID | The numeric identifier of the webhook to delete. This is required to specify which webhook to remove. |
Output
The output JSON contains a simple confirmation object indicating success:
{
"success": true
}
This confirms that the webhook was successfully deleted. No additional data or binary content is returned.
Dependencies
- Requires access to a Bitbucket Data Center instance with appropriate permissions to manage webhooks.
- Needs an API authentication credential configured in n8n, either via a personal access token or basic authentication.
- The node uses the Bitbucket Data Center REST API endpoint
/rest/api/1.0/projects/{projectKey}/repos/{repositorySlug}/webhooks/{webhookId}with HTTP DELETE method.
Troubleshooting
Common issues:
- Invalid or missing webhook ID: Ensure the webhook ID provided exists and is correct.
- Insufficient permissions: The API credentials must have rights to delete webhooks in the target repository.
- Incorrect project key or repository slug: These must be correctly set in the node parameters (not shown here but required for the webhook resource context).
- Network or connectivity problems to the Bitbucket server.
Error messages:
Bitbucket Data Center API request failed: ...indicates an issue with the API call, such as authentication failure, invalid parameters, or server errors.The operation "delete" is not supported for resource "webhook"would indicate a misconfiguration or unsupported operation, but this should not occur if parameters are set correctly.
Resolution tips:
- Verify all input parameters, especially webhook ID, project key, and repository slug.
- Check API credentials and their permissions.
- Confirm network connectivity to the Bitbucket Data Center server.
- Enable "Continue On Fail" in n8n workflow settings to handle errors gracefully if desired.