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 triggers the workflow when specific message events occur. This is useful for automating responses, logging messages, or integrating WhatsApp communication 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 (e.g., emoji reactions).
- Detecting when messages are revoked or deleted.
For example, a user could set up this node to trigger a workflow that sends an automated reply whenever a new WhatsApp message arrives.
Properties
| Name | Meaning |
|---|---|
| Remember to configure WhatsApp instance (session or server) to send events to Webhook URL | Informational notice reminding users to properly configure their WhatsApp instance to forward events to the webhook URL provided by this node. |
| 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 is:
[
{
"body": { /* Full webhook event data from WhatsApp */ }
}
]
Each output item corresponds to one webhook event. The body field contains all details of the WhatsApp event, including message content, sender info, timestamps, and event type.
No binary data is output by this node.
Dependencies
- Requires a WhatsApp instance (either session-based or server-based) configured to send webhook events to the URL exposed by this node.
- No additional external API keys or credentials are managed by this node itself; however, proper setup of the WhatsApp service and its webhook forwarding is necessary.
- The node expects to receive HTTP POST requests at the specified webhook path (
whatsapp-message).
Troubleshooting
- Webhook not triggering: Ensure the WhatsApp instance is correctly configured to send events to the exact webhook URL provided by n8n. Check network connectivity and firewall settings.
- No data received despite events occurring: Verify that the selected event types in the node’s properties match the actual events sent by WhatsApp.
- Empty output: If the incoming event type is not included in the selected events list, the node will ignore it and produce no output.
- Malformed webhook data: Confirm that the WhatsApp instance sends data in the expected format. Unexpected changes in the webhook payload structure may cause issues.