Overview
This node configures webhooks for the DinastiAPI WhatsApp API. It allows users to manage webhook settings such as setting a new webhook URL, subscribing to specific event types, updating existing webhook configurations, retrieving current webhook details, or deleting the webhook configuration.
Common scenarios where this node is beneficial include:
- Automatically receiving WhatsApp message events and presence updates in real-time.
- Synchronizing message history or media download retries via webhook notifications.
- Managing webhook subscriptions dynamically based on application needs.
For example, you can use this node to set a webhook URL that listens for incoming messages and read receipts, enabling your workflow to react instantly when a user sends a message or reads one.
Properties
| Name | Meaning |
|---|---|
| Webhook URL | The URL that will receive webhook events. |
| Events | Event types to subscribe to. Options include: All, Chat Presence, History Sync, Media Retry, Message, Presence, Read Receipt, Receipt. |
Output
The node outputs JSON data representing the response from the DinastiAPI WhatsApp API related to webhook operations. This includes details of the webhook configuration after get, set, update, or delete operations. The output structure depends on the operation performed but generally contains webhook URLs, subscribed events, and status information.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the DinastiAPI WhatsApp API.
- The node uses HTTP requests to the DinastiAPI endpoints
/webhookwith methods GET, POST, PUT, DELETE depending on the operation. - Proper network access to the specified webhook URL is necessary for receiving events.
Troubleshooting
Common issues:
- Invalid or unreachable webhook URL may cause webhook setup failures.
- Selecting incompatible or unsupported event types could result in errors.
- Network connectivity problems between n8n and DinastiAPI servers.
- Insufficient permissions or invalid API credentials leading to authentication errors.
Error messages:
- Errors returned from the API are captured and output as JSON with an
errorfield containing the message. - If the node is configured to continue on failure, it will return error details per item instead of stopping execution.
- Errors returned from the API are captured and output as JSON with an
Resolutions:
- Verify the webhook URL is publicly accessible and correctly formatted.
- Ensure the API key credential is valid and has required permissions.
- Confirm selected event types are supported by the API.
- Check network connectivity and firewall settings.
Links and References
- DinastiAPI WhatsApp API Documentation (example link, replace with actual)
- n8n Webhook Nodes Documentation: https://docs.n8n.io/nodes/trigger/webhook/