Actions82
- Client Actions
- Invoice Actions
- Payment Actions
- Receipt Actions
- Service Actions
- Team Actions
- User Actions
- Webhook Actions
- Descarga Masiva (SAT) Actions
Webhook → Delete
AI-generatedOverview
This node interacts with the Gigstack API to manage webhooks, specifically supporting the deletion of a webhook by its ID. It is useful in scenarios where you need to programmatically remove webhooks that are no longer needed or valid, such as cleaning up integrations or managing event subscriptions.
Use Case Examples
- Deleting a webhook by providing its unique webhook ID to stop receiving events from a specific source.
- Automating webhook lifecycle management in a workflow to ensure only active webhooks are maintained.
Properties
| Name | Meaning |
|---|---|
| Webhook ID | The unique identifier of the webhook to be deleted. |
| Team ID | Optional team identifier for multi-team access in Gigstack Connect. If left empty, the default team is used. |
Output
JSON
json- The response from the Gigstack API after attempting to delete the specified webhook, typically indicating success or failure.
Dependencies
- Requires an API key credential for authenticating requests to the Gigstack API.
Troubleshooting
- Ensure the provided Webhook ID is correct and exists; otherwise, the API will return an error indicating the webhook was not found.
- Verify that the API key credential has sufficient permissions to delete webhooks.
- If using Team ID, confirm it is valid and the user has access to that team.
- Common error messages include 'Webhook not found' or 'Unauthorized', which indicate issues with the webhook ID or API credentials respectively.
Links
- Gigstack API Webhooks Documentation - Official documentation for managing webhooks via the Gigstack API, including deletion.