Overview
This node acts as a trigger for WhatsApp group-related events. It listens for specific group events sent to a configured webhook URL and activates the workflow when those events occur. This is useful for automating responses or processes based on changes in WhatsApp groups, such as welcoming new members, tracking when users leave, or monitoring participant updates.
Practical examples include:
- Sending a welcome message automatically when a user joins a WhatsApp group.
- Logging or notifying administrators when someone leaves a group.
- Updating internal records or triggering workflows when group participants change.
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 WhatsApp group events to listen for. Options: Group Join, Group Leave, Group Participants Update |
Output
The node outputs JSON data representing the event received from WhatsApp. The structure of the output JSON corresponds directly to the body of the incoming webhook request, containing details about the triggered group event.
If the event type received is not among the selected events, the node produces no output.
No binary data output is involved.
Dependencies
- Requires a properly configured WhatsApp instance (either session-based or server-based) that sends group event notifications to the node’s webhook URL.
- The webhook path is fixed as
whatsapp-groupand expects POST requests with event data. - No additional external API keys or credentials are managed by this node itself; it relies on the WhatsApp instance setup.
Troubleshooting
- No events triggering: Ensure that your WhatsApp instance is correctly configured to send group event webhooks to the node’s webhook URL.
- Unexpected empty output: Verify that the event types sent by WhatsApp match the selected events in the node configuration.
- Webhook not reachable: Confirm that the n8n webhook URL is publicly accessible and correctly registered in the WhatsApp instance.
- Incorrect event data format: The node expects the event data in the request body under an
eventproperty; mismatches may cause the node to ignore the event.