Overview
This node triggers workflows in n8n 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 deleted chats, or updating CRM systems when chats are unarchived.
Practical examples:
- Automatically log archived chats to a database.
- Send notifications to a Slack channel when a chat is deleted.
- Update customer status in a CRM 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 include: - Chat Archive (chat.archive) - Chat Unarchive (chat.unarchive) - Chat Delete (chat.delete) |
Output
The node outputs JSON data representing the event payload received from WhatsApp. The output structure contains the full body of the webhook request under the json field. This includes details about the chat event that triggered the workflow.
If multiple events are selected, the node filters incoming webhook calls and only triggers when the event type matches one of the selected events.
No binary data output is produced by this node.
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 API keys or credentials are managed directly by this node; however, proper setup of the WhatsApp environment to forward events is necessary.
Troubleshooting
- Common issues:
- The node does not trigger if the WhatsApp instance is not correctly configured to send events to the webhook URL.
- Incoming events not matching the selected event types will be ignored silently.
- Error messages:
- No explicit error messages are thrown by the node itself during execution. If no workflows trigger, verify the WhatsApp instance configuration and ensure the correct events are selected.
- Resolution tips:
- Double-check the webhook URL configuration in your WhatsApp instance.
- Confirm that the event types you want to listen for are selected in the node’s properties.
- Use n8n’s webhook test tools or logs to verify that events are being received.