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 operation updates an existing webhook in a Basecamp project. It allows users to modify the webhook's target URL, specify which event types trigger the webhook, and activate or deactivate it. This is useful for automating workflows that depend on real-time notifications from Basecamp, such as syncing data with other systems, triggering alerts, or logging events.
Practical examples:
- Changing the callback URL of a webhook after migrating your server.
- Updating the types of events you want to listen to without creating a new webhook.
- Activating or deactivating a webhook temporarily during maintenance.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the Basecamp project (bucket) where the webhook exists. |
| Webhook ID | The numeric ID of the webhook to update. |
| Payload URL | The HTTPS URL that Basecamp will call when one of the specified events occurs. |
| Webhook Fields | A collection of additional webhook settings: |
| - Event Types | The types of events that will trigger this webhook (string). |
| - Active | Boolean flag indicating whether the webhook should be active (true) or inactive (false). |
| Return Full Response | Whether to return the full HTTP response (status code, headers, body) instead of just the body. |
Output
The node outputs JSON data representing the updated webhook information returned by the Basecamp API. If "Return Full Response" is enabled, the output includes the full HTTP response details such as status code and headers along with the body.
No binary data output is involved in this operation.
Dependencies
- Requires an authenticated connection to the Basecamp API using OAuth2 credentials.
- The node uses the Basecamp API endpoint structured as
https://3.basecampapi.com/{accountId}where{accountId}is provided by the user's credentials. - Proper permissions on the Basecamp account to update webhooks are necessary.
Troubleshooting
- Invalid Project ID or Webhook ID: Ensure the IDs correspond to existing resources in Basecamp; otherwise, the API will return errors.
- Invalid Payload URL: The URL must be HTTPS and reachable by Basecamp; invalid URLs may cause webhook failures.
- Insufficient Permissions: The OAuth2 token must have rights to modify webhooks; otherwise, authorization errors will occur.
- API Rate Limits: Frequent updates might hit Basecamp API rate limits; handle errors gracefully and retry later.
- Return Full Response Misuse: Enabling full response output changes the output structure; downstream nodes must handle this accordingly.