Overview
This node triggers workflows when specific WhatsApp chat events occur. It listens for events such as chat archiving, unarchiving, and deletion sent to a configured webhook URL. This is useful for automating responses or actions based on changes in WhatsApp chats, such as logging chat archives, notifying teams about chat deletions, or updating CRM systems when chats are unarchived.
Practical examples:
- Automatically log archived chats to a database for record-keeping.
- Send notifications to support agents when a chat is deleted.
- Trigger follow-up workflows when a chat is unarchived.
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 the webhook URL provided by this node. |
| Events | The WhatsApp chat events to listen for. Options: Chat Archive, Chat Unarchive, Chat Delete. Users can select one or multiple events to trigger the workflow. |
Output
The node outputs JSON data representing the event payload received from WhatsApp. The output contains the full body of the webhook request under the json field, allowing downstream nodes to access detailed information about the chat event.
No binary data is output by this node.
Example output structure:
[
{
"event": "chat.archive",
"body": {
/* full event details as received */
}
}
]
Dependencies
- Requires a WhatsApp instance (either session-based or server-based) configured to send chat event notifications to the webhook URL exposed by this node.
- No additional external services or API keys are required within the node itself.
- The user must ensure that the WhatsApp system is properly set up to forward events to the node’s webhook endpoint.
Troubleshooting
- No events triggering: Ensure that the WhatsApp instance is correctly configured to send events to the webhook URL provided by this node.
- Selected events not firing: Verify that the event types selected in the node’s properties match those being sent by WhatsApp.
- Empty or missing payload: Confirm that the webhook receives valid POST requests with the expected event data.
- Webhook URL inaccessible: Make sure the n8n instance is publicly accessible or tunneled properly so WhatsApp can reach the webhook.
Common error messages are not explicitly thrown by this node but may arise from misconfiguration or network issues related to webhook delivery.