Actions37
- Message Actions
- Media Actions
- Contact Actions
- Group Actions
- Instance Actions
- Webhook Actions
Overview
This node integrates with the Uazapi WhatsApp API to manage webhook configurations among other WhatsApp-related operations. Specifically, the Delete Webhook operation under the Webhook resource allows users to remove an existing webhook configuration from their WhatsApp instance. This is useful when you want to stop receiving webhook events or need to reset webhook settings.
Common scenarios include:
- Disabling webhook event notifications temporarily or permanently.
- Cleaning up webhook configurations during testing or migration.
- Resetting webhook URLs before setting a new one.
Example: If you previously set a webhook URL to receive message events and now want to disable it, you can use this operation to delete that webhook configuration.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | Optional extra parameters for the request. Includes: |
| - Reply to Message ID: ID of message to reply to | |
| - Delay (seconds): Delay before sending message | |
| - Disable Link Preview: Whether to disable link previews in messages (true/false) | |
| - Mention Users: Comma-separated phone numbers to mention |
Note: For the Delete Webhook operation, only "Additional Fields" are available as input properties, but typically no additional fields are required for deleting the webhook.
Output
The node outputs a JSON object representing the response from the Uazapi API after attempting to delete the webhook configuration. The structure depends on the API's response but generally includes status information about the deletion request.
Example output JSON might look like:
{
"success": true,
"message": "Webhook deleted successfully"
}
No binary data is involved in this operation.
Dependencies
- Requires an active Uazapi WhatsApp API account.
- Needs credentials including:
- An API key credential for authenticating requests.
- API token and instance ID for identifying the WhatsApp instance.
- The node sends HTTP requests to the Uazapi API endpoint configured in the credentials.
- No additional environment variables are needed beyond the credential setup.
Troubleshooting
Common issues:
- Invalid or missing credentials will cause authentication failures.
- Attempting to delete a webhook when none is set may return an error or a no-op response.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication errors: Check that the API key, token, and instance ID are correctly configured.
- "Unknown resource" error: Ensure the resource parameter is set to "webhook".
- HTTP errors from the API: Review the API response message for details; verify the instance ID and API URL.
Resolution tips:
- Verify all credential fields are correct and have necessary permissions.
- Confirm the webhook exists before attempting deletion.
- Use the Get Webhook operation to check current webhook status.
Links and References
- Uazapi Official Documentation (for detailed API endpoints and webhook management)
- WhatsApp Business API Webhooks Guide (general webhook concepts)
- n8n documentation on Creating Custom Nodes