Actions119
- Campfire Actions
- Card Table Actions
- Chatbot Actions
- Client Approval Actions
- Client Correspondence Actions
- Client Reply Actions
- Client Visibility Actions
- Comment Actions
- Document Actions
- Event Actions
- Forward Actions
- Inbox Actions
- Inbox Reply Actions
- Lineup Marker Actions
- Message Actions
- Message Board Actions
- Message Type Actions
- Person Actions
- Project Actions
- Question Actions
- Question Answer Actions
- Questionnaire Actions
- Recording Actions
- Schedule Actions
- Schedule Entry Actions
- Template Actions
- Todo Actions
- Todolist Actions
- Todolist Group Actions
- Todoset Actions
- Upload Actions
- Vault Actions
- Webhook Actions
Overview
This node allows users to interact with the Basecamp API, specifically to delete a webhook associated with a project (referred to as a "bucket" in Basecamp terminology). Deleting a webhook is useful when you want to stop receiving event notifications or callbacks from Basecamp for a particular webhook that is no longer needed or valid.
Common scenarios include:
- Cleaning up unused or obsolete webhooks after project changes.
- Managing webhook lifecycle programmatically within automation workflows.
- Ensuring security by removing webhooks that might be compromised or no longer authorized.
Example: A user has set up multiple webhooks for different projects and wants to automate the removal of a webhook when a project is archived or deleted.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project (bucket) where the webhook exists. Used in the API endpoint path. |
| Webhook ID | The numeric ID of the webhook to delete. Used in the API endpoint path. |
| Return Full Response | Boolean option to return the full HTTP response including status code, headers, and body instead of just the response body. |
Output
The output JSON contains the response from the Basecamp API after attempting to delete the specified webhook. If the "Return Full Response" property is enabled, the output will include the full HTTP response details such as status code, headers, and body. Otherwise, it returns only the response body.
No binary data is involved in this operation.
Dependencies
- Requires an API authentication token credential configured in n8n to authenticate requests against the Basecamp API.
- The node uses the Basecamp API base URL constructed dynamically using the account ID from credentials.
- No additional external dependencies are required beyond the Basecamp API access.
Troubleshooting
- Invalid Project ID or Webhook ID: If either ID is incorrect or does not exist, the API will likely return a 404 Not Found error. Verify the IDs before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key or OAuth token is correctly configured.
- Permission Issues: The authenticated user must have sufficient permissions to delete webhooks on the specified project.
- Network Issues: Connectivity problems can cause request failures; check network access to the Basecamp API endpoint.
- Return Full Response Confusion: If enabled, the output includes more detailed HTTP info which may require parsing to extract relevant data.