Overview
This node acts as a trigger for WhatsApp group-related events. It listens for specific group events such as when a user joins a group, leaves a group, or when group participants are updated. When one of the selected events occurs, the node activates and passes the event data to the workflow.
Common scenarios where this node is beneficial include:
- Automating welcome messages or onboarding processes when new users join a WhatsApp group.
- Tracking group membership changes for analytics or moderation purposes.
- Reacting to participant updates to maintain synchronized records or notify administrators.
For example, you could use this node to automatically send a greeting message whenever someone joins a WhatsApp group or to log participant changes in an external database.
Properties
| Name | Meaning |
|---|---|
| Remember to configure WhatsApp instance (session or server) to send events to Webhook URL | Informational notice reminding to set up the WhatsApp instance to forward events to this node's webhook URL. |
| Events | The WhatsApp group events to listen for. Options: "Group Join" (user joined group), "Group Leave" (user left group), "Group Participants Update" (group participants updated). Multiple can be selected. |
Output
The node outputs JSON data representing the WhatsApp group event that triggered it. The output structure corresponds directly to the body of the incoming webhook request from the WhatsApp instance. This typically includes details about the event type, group information, and participant data.
No binary data output is produced by this node.
Dependencies
- Requires a 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 containing event data. - No additional external services or API keys are required within the node itself, but proper WhatsApp integration setup is necessary.
Troubleshooting
Issue: The node does not trigger on expected group events.
- Cause: The WhatsApp instance may not be correctly configured to send events to the webhook URL.
- Resolution: Ensure the WhatsApp instance’s event forwarding is set to the exact webhook URL provided by n8n for this node.
Issue: No data appears in the workflow after an event.
- Cause: The event type received might not be included in the selected "Events" property.
- Resolution: Verify that the event types you want to listen for are selected in the node’s properties.
Error: Invalid or missing webhook payload.
- Cause: Incoming requests do not contain the expected event data structure.
- Resolution: Confirm that the WhatsApp instance sends properly formatted event data matching the node’s expectations.
Links and References
- WhatsApp Business API Documentation
- n8n Webhook Node Documentation
- WhatsApp Group Event Types Explained (for understanding event payloads)