WhatsApp Message Trigger
AI-generatedOverview
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) to update user engagement metrics.
- Detecting when messages are revoked or deleted to maintain accurate records.
For example, a customer support workflow could be triggered whenever a new WhatsApp message arrives, enabling automated ticket creation or chatbot responses.
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 event types are selected, indicating which events are handled by the node. |
Output
The node outputs JSON data representing the full webhook payload received from the WhatsApp instance for the triggered event. The output structure includes all details sent by WhatsApp about the message event, such as message content, sender information, timestamps, and event type.
The output is provided as an array with one element per webhook call, where each element contains the entire body of the webhook request under the json field.
No binary data output is produced by this node.
Dependencies
- Requires a properly configured WhatsApp instance (either session-based or server-based) that can send webhook events to the URL exposed by this node.
- The user must configure the WhatsApp service to forward relevant message events to the node’s webhook endpoint.
- No additional external API keys or credentials are managed by this node itself; it relies on the WhatsApp instance setup.
Troubleshooting
- Webhook not triggering: Ensure the WhatsApp instance is correctly configured to send events to the exact webhook URL provided by this node.
- No data received: Verify that the selected event types in the "Events" property match those being sent by the WhatsApp instance.
- Unexpected empty output: If the incoming event type is not included in the selected events list, the node will ignore it and produce no output.
- Event format changes: If WhatsApp updates their webhook payload structure, the node will pass through the raw JSON, but downstream nodes may need adjustment.