Actions15
Overview
This node interacts with the ZapSign API to manage webhooks related to digital signature events. Specifically, the Delete Webhook operation allows users to remove an existing webhook by its ID. This is useful for cleaning up or disabling webhook notifications that are no longer needed.
Common scenarios include:
- Removing outdated or unused webhook URLs to prevent receiving unnecessary event notifications.
- Managing webhook lifecycle programmatically as part of automation workflows.
- Ensuring security by deleting webhooks that might expose sensitive information.
Example: You have a webhook set up to listen for document completion events, but you want to stop receiving these notifications. Using this node's Delete Webhook operation, you provide the webhook ID and delete it from ZapSign.
Properties
| Name | Meaning |
|---|---|
| Webhook ID | The unique identifier of the webhook to delete |
Output
The output is a JSON object representing the response from the ZapSign API after attempting to delete the webhook. Typically, this will confirm successful deletion or provide error details if the operation failed.
The json output field contains the API response data. There is no binary output for this operation.
Example output JSON structure (simplified):
{
"id": "webhook-id",
"url": "https://example.com/webhook",
"events": ["document.completed"],
"deleted": true
}
Dependencies
- Requires an active API key credential for authenticating with the ZapSign API.
- The node uses the ZapSign API endpoint
/v1/webhooks/{webhookId}with HTTP DELETE method. - No additional environment variables are required beyond the API authentication setup in n8n.
Troubleshooting
Error: Invalid Webhook ID or Not Found
This occurs if the provided webhook ID does not exist or has already been deleted. Verify the webhook ID is correct.Authentication Errors
If the API key is missing, invalid, or expired, the request will fail. Ensure the API credential is correctly configured and valid.Network or API Unavailability
Temporary network issues or ZapSign service downtime can cause failures. Retry after some time or check ZapSign status.Permission Denied
The API key used may lack permissions to delete webhooks. Confirm the API key has sufficient rights.
To resolve errors, verify input parameters, credentials, and network connectivity.