Overview
This node is a trigger that activates when WhatsApp presence events occur. It listens for specific presence-related updates such as when a user goes online, offline, or starts typing. This is useful for workflows that need to react in real-time to changes in user presence on WhatsApp, for example, to update a dashboard, notify a team member, or log activity.
A practical example would be triggering a workflow whenever a contact's presence status changes, allowing automated responses or logging of user availability.
Properties
| Name | Meaning |
|---|---|
| Remember to configure WhatsApp instance (session or server) to send events to Webhook URL | Informational notice reminding the user to set up their 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 - online, offline, typing, etc.) |
Output
The node outputs JSON data representing the event received from WhatsApp. The output structure contains the full body of the webhook request under the json field. This includes details about the presence event such as the type of presence update and associated metadata.
No binary data is output by this node.
Example output JSON structure:
{
"event": "presence.update",
"body": {
// detailed presence event data from WhatsApp
}
}
Dependencies
- Requires a configured WhatsApp instance (either session-based or server) that sends presence events to the webhook URL exposed by this node.
- The webhook path is
/whatsapp-presence, which must be accessible externally for WhatsApp to post events. - No additional API keys or credentials are handled directly by this node; it relies on external WhatsApp infrastructure setup.
Troubleshooting
- No events triggering: Ensure your WhatsApp instance is correctly configured to send presence events to the webhook URL provided by this node.
- Webhook not reachable: Verify that the webhook URL is publicly accessible and properly registered with the WhatsApp instance.
- Event filtering: If no workflows trigger, check that the selected event types in the "Events" property match those sent by your WhatsApp instance.
- Unexpected payloads: Confirm that the incoming webhook payload matches expected WhatsApp presence event formats.