N8N Tools - Uazapi icon

N8N Tools - Uazapi

Complete Uazapi integration - Premium WhatsApp API with advanced messaging and automation

Actions37

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 event notifications or need to reset webhook settings.

Practical scenarios include:

  • Disabling webhook callbacks temporarily or permanently.
  • Cleaning up webhook configurations during testing or migration.
  • Managing webhook lifecycle programmatically within automation workflows.

Properties

Name Meaning
Additional Fields Optional extra parameters for the request. For this operation, no additional fields are used but the collection is available for consistency. Options include:
- Reply to Message ID (string)
- Delay (seconds) (number)
- Disable Link Preview (boolean)
- Mention Users (string, comma-separated phone numbers)

Note: The "Additional Fields" property is present as a generic input collection but does not affect the Delete Webhook operation.

Output

The node outputs a JSON object representing the response from the Uazapi API after attempting to delete the webhook configuration. The structure typically includes status information about the deletion request.

Example output JSON structure:

{
  "status": "success",
  "message": "Webhook deleted successfully"
}

If an error occurs, the output will contain an error field with the error message.

No binary data is produced by this operation.

Dependencies

  • Requires an active Uazapi WhatsApp API account.
  • Needs credentials including:
    • An API key credential for authenticating requests to the proxy service.
    • API token and instance ID for the WhatsApp instance.
  • The node sends HTTP requests via a proxy endpoint (https://n8ntools.io/api/v1/proxy/uazapi) which requires the API key.
  • Proper configuration of these credentials in n8n is necessary for successful execution.

Troubleshooting

  • Common issues:

    • Invalid or missing credentials can cause authentication failures.
    • Attempting to delete a webhook when none is set may return an error or no-op response.
    • Network connectivity problems to the proxy or Uazapi endpoints.

  • Error messages:

    • "Unauthorized" or "Invalid API key": Check that the API key and tokens are correctly configured.
    • "Instance not found": Verify the instance ID is correct and active.
    • "Webhook not configured": Indicates there is no webhook to delete; confirm webhook existence before deleting.

  • Resolution tips:

    • Ensure all required credentials are valid and have proper permissions.
    • Confirm the webhook URL is currently set if expecting a deletion.
    • Use the Get Webhook operation to verify current webhook status before deleting.

Links and References

Discussion