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 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 reduce clutter in the system.
Practical examples include:
- Removing a webhook that was set up for a temporary integration.
- Cleaning up webhooks after a project or feature is deprecated.
- Managing webhook subscriptions programmatically within automation workflows.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The unique numeric identifier of the Basecamp bucket (project container) where the webhook exists. |
| Webhook Id | The unique numeric identifier of the webhook to be destroyed 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. There is no binary output associated with this operation.
Dependencies
- Requires an API authentication token credential configured in n8n to access the Basecamp API.
- The node uses the Basecamp API endpoint constructed dynamically based on the authenticated user's Basecamp account ID.
- Network connectivity 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.
- Permission Issues: The authenticated user must have sufficient permissions to delete webhooks in the specified bucket.
- API Rate Limits: Excessive requests may trigger rate limiting; handle retries or backoff accordingly.