Actions80
- Card Tables Actions
- Forwards Actions
- Events Actions
- Recordings 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
- Todo Sets Actions
- Todo Lists Actions
- Todos Actions
Overview
This node operation allows users to delete (destroy) a specific webhook from a given bucket in the Basecamp service. It is useful when you want to stop receiving event notifications for a particular webhook, such as when cleaning up unused webhooks or managing integrations dynamically.
Practical examples include:
- Removing a webhook that was set up for a project or bucket that is no longer active.
- Managing webhook lifecycle programmatically to avoid unnecessary callbacks and reduce resource usage.
- Automating cleanup of webhooks during deployment or integration updates.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The numeric identifier of the bucket where the webhook exists. This specifies the scope or container of the webhook. |
| Webhook Id | The numeric identifier of the webhook to be destroyed. This uniquely identifies which webhook to delete within the specified bucket. |
Output
The node outputs JSON data representing the result of the webhook deletion request. Typically, this will confirm whether the webhook was successfully deleted or provide error information if the operation failed.
No binary data output is expected from this operation.
Dependencies
- Requires an API authentication token credential to authorize requests against the Basecamp API.
- The node uses the Basecamp API endpoint constructed with the user's Basecamp account ID.
- Proper network access to the Basecamp API service is necessary.
Troubleshooting
- Invalid Bucket Id or Webhook Id: If either ID is incorrect or does not exist, the API will return an error indicating the resource was not found. Verify the IDs before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key or OAuth token is correctly configured.
- Network Issues: Connectivity problems can lead to timeouts or unreachable errors. Check your network connection and firewall settings.
- Permission Denied: The authenticated user must have sufficient permissions to delete webhooks in the specified bucket.