Actions82
- Client Actions
- Invoice Actions
- Payment Actions
- Receipt Actions
- Service Actions
- Team Actions
- User Actions
- Webhook Actions
- Descarga Masiva (SAT) Actions
Webhook → Update
AI-generatedOverview
This node operation updates an existing webhook in the Gigstack system. It allows users to modify webhook properties such as the URL that receives notifications, the events that trigger the webhook, its description, and its status (active or inactive). This is useful for managing webhook configurations dynamically without needing to recreate them, for example, changing the notification URL or updating the events to listen for.
Use Case Examples
- Updating a webhook's URL to a new endpoint to receive payment notifications.
- Changing the events that trigger the webhook to include invoice and customer updates.
- Setting the webhook status to inactive temporarily during maintenance.
Properties
| Name | Meaning |
|---|---|
| Webhook ID | The unique identifier of the webhook to update. |
| Update Fields | Fields to update on the webhook, including URL, events, description, and status. |
| Team ID | Optional team ID for multi-team access; leave empty to use the default team. |
Output
JSON
json- The updated webhook object returned from the Gigstack API after the update operation.
Dependencies
- Gigstack API with authentication via an API key credential
Troubleshooting
- Ensure the Webhook ID is correct and exists in the Gigstack system to avoid 'not found' errors.
- Verify that the URL provided is valid and reachable to prevent webhook delivery issues.
- Check that the events array contains valid event types supported by Gigstack.
- If updating the status, ensure the value is either 'active' or 'inactive' to avoid validation errors.
- Handle API errors gracefully, especially network or authentication failures, by checking credentials and connectivity.
Links
- Gigstack Webhooks API Documentation - Official documentation for managing webhooks via the Gigstack API.