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
Webhook → Update a Webhook
AI-generatedOverview
This node operation updates an existing webhook in a Basecamp project. It allows users to modify the webhook's payload URL, event types that trigger the webhook, and its active status. This is useful for managing webhook configurations dynamically, such as changing the callback URL or adjusting which events should trigger notifications.
Use Case Examples
- Updating the payload URL of a webhook to a new HTTPS endpoint.
- Changing the event types that trigger the webhook to focus on specific project activities.
- Activating or deactivating a webhook without deleting it.
Properties
| Name | Meaning |
|---|---|
| Project ID | The ID of the Basecamp project (bucket) where the webhook exists. Used in the API endpoint path. |
| Webhook ID | The ID of the webhook to update. Used in the API endpoint path. |
| Payload URL | The HTTPS URL that Basecamp will call when a matching event occurs. This is the webhook's callback URL. |
| Webhook Fields | Additional fields for the webhook including event types that trigger it and whether it is active. |
| Return Full Response | Whether to return the full HTTP response (status code, headers, body) instead of only the response body. |
| Request Options | Additional request options such as batching, SSL certificate validation, proxy settings, and timeout configuration. |
Output
JSON
statusCode- HTTP status code of the response.headers- HTTP headers returned in the response.body- The main content of the response, typically the updated webhook data.
Dependencies
- Requires an OAuth2 API credential for Basecamp authentication.
Troubleshooting
- Ensure the Project ID and Webhook ID are correct and correspond to existing resources in Basecamp.
- Verify the Payload URL is a valid HTTPS URL as required by Basecamp.
- If the webhook update fails, check the API response for error messages indicating permission issues or invalid parameters.
- If SSL issues occur, consider enabling the option to ignore SSL certificate validation, but be cautious as this reduces security.
Links
- Basecamp API - Update a Webhook - Official Basecamp API documentation for updating a webhook.