Actions68
- Recordings Actions
- Card Tables Actions
- Forwards Actions
- Events Actions
- Projects Actions
- People Actions
- Chatbots Actions
- Webhooks Actions
- Attachments Actions
- Templates Actions
- Uploads Actions
- Documents Actions
- Lineup Markers Actions
- Subscriptions Actions
- Schedules Actions
- Schedule Entries Actions
Overview
This node operation allows users to delete (destroy) a specific webhook from a Basecamp project by specifying the bucket and webhook identifiers. It is useful for managing webhooks lifecycle, such as cleaning up unused or obsolete webhooks to prevent unwanted callbacks or notifications.
Practical examples include:
- Removing a webhook that was set up for a temporary integration.
- Cleaning up webhooks after a project or integration is deprecated.
- Managing webhook subscriptions programmatically within automation workflows.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The numeric identifier of the Basecamp bucket (project) where the webhook exists. This specifies the scope of the webhook to be deleted. |
| Webhook Id | The numeric identifier of the webhook to be destroyed. This uniquely identifies which webhook to remove within the specified bucket. |
Output
The node outputs JSON data representing the result of the webhook deletion request. Typically, this will confirm successful deletion or provide error details if the operation failed.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential with appropriate permissions to manage Basecamp webhooks.
- The node uses the Basecamp API endpoint constructed dynamically using the authenticated user's Basecamp ID.
- Proper network access to Basecamp's API service is necessary.
Troubleshooting
Common issues:
- Invalid or missing Bucket Id or Webhook Id can cause the operation to fail.
- Insufficient permissions on the API key may result in authorization errors.
- Network connectivity problems can prevent reaching the Basecamp API.
Error messages:
- "Not Found" or similar indicates the specified webhook or bucket does not exist or is inaccessible.
- "Unauthorized" suggests invalid or expired API credentials.
- "Bad Request" may indicate malformed input parameters.
Resolutions:
- Verify that the Bucket Id and Webhook Id are correct and correspond to existing resources.
- Ensure the API key has the required scopes/permissions.
- Check network connectivity and Basecamp service status.