Overview
This node acts as a trigger for WhatsApp message-related events. It listens for incoming webhook POST requests from a configured WhatsApp instance and activates the workflow when specified message events occur. This is useful for automating responses, logging messages, or integrating WhatsApp communications into broader business processes.
Common scenarios include:
- Automatically processing new incoming WhatsApp messages.
- Reacting to any type of message event for analytics or monitoring.
- Handling message reactions (like emoji reactions) to update user engagement metrics.
- Detecting when messages are revoked or deleted to maintain accurate conversation records.
Properties
| Name | Meaning |
|---|---|
| Remember to configure WhatsApp instance (session or server) to send events to Webhook URL | Informational notice reminding users to set up their WhatsApp instance to forward events to this node's webhook URL. |
| Events | The types of WhatsApp message events to listen for. Options: - Message: New message received - Message Any: Any message event - Message Reaction: Message reaction events - Message Revoked: Message revoked/deleted events |
| Events Handled | Informational notice displayed when any of the above events are selected, indicating which events the node will handle. |
Output
The node outputs JSON data representing the full webhook payload received from the WhatsApp instance. The output structure includes an event field indicating the event type and other relevant message details as provided by the WhatsApp webhook.
Example output JSON structure:
[
{
"event": "message",
"body": {
// Full webhook payload content here
}
}
]
No binary data is output by this node.
Dependencies
- Requires a properly configured WhatsApp instance (either session-based or server-based) that sends webhook events to the node’s webhook URL.
- The webhook URL must be publicly accessible for WhatsApp to deliver events.
- No additional API keys or credentials are managed within this node; authentication and setup are handled externally.
Troubleshooting
- No events triggering: Ensure the WhatsApp instance is correctly configured to send events to the webhook URL exposed by this node.
- Webhook not reachable: Verify that the webhook URL is publicly accessible and not blocked by firewalls or network restrictions.
- Selected events not firing: Confirm that the WhatsApp instance actually emits the selected event types and that they match the node’s configured event filters.
- Empty or unexpected payloads: Check the WhatsApp webhook configuration and payload format to ensure compatibility with this node’s expected input.