Overview
This node triggers workflows when specific WhatsApp presence events occur. It listens for updates such as user presence changes (e.g., online, offline, typing) sent to a configured webhook URL. This is useful for automating responses or actions based on the real-time presence status of WhatsApp users.
Practical examples include:
- Notifying a support team when a customer becomes online.
- Logging user presence changes for analytics.
- Triggering follow-up messages when a user starts typing.
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 types of presence events to listen for. Options: "Presence Update" (user presence updated such as online, offline, typing). |
Output
The node outputs JSON data representing the event received from WhatsApp. The structure includes the full body of the webhook request under the json field. This typically contains details about the presence event, such as the user's current status.
No binary data output is produced by this node.
Dependencies
- Requires a properly configured WhatsApp instance (either session-based or server) that sends presence events to the node’s webhook URL.
- The webhook path is fixed as
/whatsapp-presence. - No additional external services or API keys are required within the node itself, but the WhatsApp instance must be set up externally to forward events.
Troubleshooting
- No events triggering: Ensure the WhatsApp instance is correctly configured to send presence events to the webhook URL exposed by n8n.
- Event not recognized: Verify that the event type sent matches one of the selected events in the node properties.
- Webhook URL unreachable: Confirm that the webhook URL is publicly accessible and correctly registered with the WhatsApp instance.
- Empty workflow data: If the event is filtered out because it is not included in the selected events, no data will be passed to the workflow.