Actions80
- Todos Actions
- 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
Overview
This node allows updating an existing webhook in the Basecamp service. It is useful when you need to modify the configuration of a webhook, such as changing the URL that receives event notifications, adjusting which event types trigger the webhook, or toggling its active status.
Practical scenarios include:
- Changing the destination URL for webhook callbacks after migrating your receiving service.
- Updating the types of events that should trigger the webhook to better filter notifications.
- Temporarily disabling or re-enabling 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 triggering the webhook. |
| Types | JSON array specifying which event types will 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's ID, associated bucket, payload URL, subscribed event types, active status, and timestamps.
No binary data output is involved.
Dependencies
- Requires an API authentication token credential configured in n8n to access the Basecamp API.
- The node uses the Basecamp API endpoint constructed with the user's Basecamp account ID.
- Network connectivity to Basecamp's API service is necessary.
Troubleshooting
- Invalid Bucket Id or Webhook Id: If these IDs do not correspond to existing resources, the API will return errors. Verify the IDs are correct.
- Invalid Payload URL: The URL must be HTTPS and reachable; otherwise, webhook delivery may fail.
- Malformed Types JSON: Ensure the "Types" property contains valid JSON array syntax.
- Authentication Errors: Check that the API key or OAuth token is valid and has sufficient permissions.
- Inactive Webhook Not Triggering: If the "Active" flag is false, the webhook will not receive events.