WhatsApp Session Trigger
AI-generatedOverview
This node triggers workflows when there are changes in the WhatsApp session status. It listens for specific session events such as connection or disconnection updates from a configured WhatsApp instance. This is useful for monitoring the health and connectivity of your WhatsApp integration, enabling automated responses or alerts when the session state changes.
Practical examples include:
- Automatically notifying an admin or support team if the WhatsApp session disconnects.
- Logging session status changes for audit or troubleshooting purposes.
- Triggering reconnection attempts or fallback mechanisms when the session goes offline.
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" (updates like connected, disconnected, etc.) |
Output
The node outputs JSON data representing the event received from the WhatsApp session. The output structure corresponds directly to the webhook payload sent by the WhatsApp instance and includes details about the session event (e.g., status changes).
The output JSON is wrapped inside an array under the workflowData key, suitable for further processing in subsequent workflow nodes.
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 with the WhatsApp service to receive events.
Troubleshooting
- No events triggering: Ensure the WhatsApp instance is correctly configured to send session events to the webhook URL provided by this node.
- Empty output or no workflow execution: Verify that the event type sent matches one of the selected event types in the node’s "Events" property.
- Webhook not reachable: Confirm network accessibility and that the webhook path (
whatsapp-session) is correctly exposed and not blocked by firewalls or proxies.
Links and References
- WhatsApp Business API Documentation
- n8n Webhook Node Documentation (for understanding webhook setup and usage)