Overview
This node manages webhook configurations for the Wuzapi WhatsApp API. It allows users to set, update, get, or delete webhook URLs and specify which event types the webhook should subscribe to. This is useful for integrating WhatsApp messaging events into workflows, enabling real-time processing of messages, presence updates, read receipts, and more.
Practical examples include:
- Setting a webhook URL to receive incoming WhatsApp messages and presence updates.
- Updating an existing webhook to change subscribed event types or activate/deactivate it.
- Retrieving current webhook configuration to verify settings.
- Deleting a webhook when no longer needed.
Properties
| Name | Meaning |
|---|---|
| Webhook URL | The URL that will receive webhook events from Wuzapi WhatsApp API. |
| Events | Event types to subscribe to. Options: All, Chat Presence (typing indicators), History Sync (message history), Message (incoming messages), Presence (user online/offline status), Read Receipt (message read confirmations). |
Output
The node outputs JSON data representing the response from the Wuzapi API regarding webhook configuration. This includes details such as the currently set webhook URL, subscribed events, and status information depending on the operation performed (get, set, update, delete).
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Wuzapi WhatsApp API.
- The node uses HTTP requests to the
/webhookendpoint of the Wuzapi API. - Proper network access to the specified webhook URL is necessary for receiving events.
Troubleshooting
Common issues:
- Invalid or unreachable webhook URL may cause failures in setting or updating the webhook.
- Incorrect event type selections could result in missing expected webhook events.
- Network or authentication errors when communicating with the Wuzapi API.
Error messages:
- Errors returned from the API are passed through; typical messages might indicate invalid URL format, unauthorized access due to missing/invalid API key, or server errors.
- To resolve, verify the webhook URL is correct and publicly accessible, ensure the API key credential is valid, and check network connectivity.
Links and References
- Wuzapi WhatsApp API Documentation (example placeholder link)
- n8n Webhook Node Concepts: https://docs.n8n.io/nodes/n8n-nodes-base.webhook/