WAHA WhatsApp Session Trigger
AI-generatedOverview
This node acts as a trigger that activates when the status of a WhatsApp session changes. It listens for specific session events, such as connection or disconnection updates, and initiates workflow execution upon receiving these events. This is particularly useful for workflows that need to respond dynamically to the state of a WhatsApp session, for example, to log session activity, alert users about connection issues, or manage session lifecycle events.
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 session events to listen for. Options: "Session Status" (e.g., connected, disconnected). |
Output
The node outputs JSON data representing the event received from the WhatsApp session. The output structure corresponds directly to the body of the incoming webhook request, containing details about the session event. The output is provided as an array with one element per event, enabling downstream nodes to process session status updates.
No binary data is produced by this node.
Dependencies
- Requires a properly configured WhatsApp instance (either session-based or server-based) that sends session event notifications to the node’s webhook URL.
- The user must ensure the webhook URL exposed by this node is accessible and correctly registered in the WhatsApp instance configuration to receive events.
Troubleshooting
Common Issue: No workflow trigger despite WhatsApp session changes.
- Cause: The WhatsApp instance may not be configured to send events to the correct webhook URL.
- Resolution: Verify that the WhatsApp instance is set up to forward session events to the webhook URL provided by this node.
Common Issue: Workflow triggers but no data appears.
- Cause: The event type sent by WhatsApp does not match any selected in the "Events" property.
- Resolution: Ensure the "Events" property includes the event types you expect to receive.
Error Messages: The node does not explicitly throw errors but silently ignores events not matching the selected types.
Links and References
- WhatsApp Business API Documentation
- n8n Webhook Node Documentation: https://docs.n8n.io/nodes/n8n-nodes-base.webhook/