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 updates an existing webhook in the Basecamp service. It allows users to modify the webhook's target URL, specify which event types trigger the webhook, and toggle its active status. This is useful for managing how Basecamp notifies external systems about events, enabling integration workflows such as syncing project updates, triggering notifications, or automating tasks based on Basecamp activity.
Practical examples include:
- Changing the destination URL where webhook payloads are sent after a project update.
- Adjusting the types of events (e.g., new messages, to-dos) that trigger webhook calls.
- Activating or deactivating a webhook without deleting it.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | Numeric identifier of the Basecamp bucket (project) where the webhook exists. |
| Webhook Id | Numeric identifier of the specific webhook to update within the given bucket. |
| Payload Url | HTTPS URL that Basecamp will call when the webhook is triggered. |
| Types | JSON array specifying which event types should trigger the webhook calls. |
| Active | Boolean flag indicating whether the webhook is currently active and matching events. |
Output
The node outputs JSON data representing the updated webhook object returned by the Basecamp API. This typically includes details such as the webhook ID, associated bucket, configured URL, event types, and active status.
If the webhook update involves binary data (not indicated here), it would represent related files or attachments, but this operation focuses on JSON data only.
Dependencies
- Requires an API authentication token credential for Basecamp with appropriate permissions.
- The node uses Basecamp’s REST API endpoint, constructed dynamically using the user's Basecamp account ID.
- No additional external dependencies beyond the Basecamp API and n8n's HTTP request capabilities.
Troubleshooting
- Invalid Bucket or Webhook Id: Errors may occur if the provided IDs do not exist or belong to another account. Verify the IDs are correct and accessible.
- Invalid Payload URL: The URL must be a valid HTTPS endpoint. Ensure the URL is correctly formatted and reachable.
- Malformed Types JSON: The
Typesproperty expects a valid JSON array. Invalid JSON syntax will cause errors; validate the JSON format before submission. - Inactive Webhook Not Triggering: If the webhook is set to inactive, no events will trigger it. Toggle the
Activeproperty accordingly. - Authentication Errors: Ensure the API key or OAuth token used has sufficient permissions and is not expired.
Links and References
- Basecamp API Documentation - Webhooks
- n8n Documentation - Creating Custom Nodes
- JSON Validator – Useful for validating the
TypesJSON input.