Overview
This node triggers workflows in n8n 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 actions based on the real-time status of WhatsApp users, such as notifying teams when a contact becomes available or starts typing.
Practical examples include:
- Sending alerts when a key contact goes online.
- Logging 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: online, offline, typing, etc.) |
Output
The node outputs JSON data representing the WhatsApp presence event received via the webhook. The output structure corresponds directly to the webhook payload and includes details about the presence event, such as the type of update and relevant metadata.
Example output JSON structure:
{
"event": "presence.update",
"body": {
// event-specific data fields here
}
}
No binary data is produced by this node.
Dependencies
- Requires a WhatsApp instance (either session-based or server) properly configured to send presence events to the node’s webhook URL.
- The webhook URL must be publicly accessible for WhatsApp to post events.
- No additional external API keys or credentials are managed within this node; authentication and setup are handled externally.
Troubleshooting
- No events triggering: Ensure that the WhatsApp instance is correctly configured to send presence events to the webhook URL exposed by this node.
- Webhook not reachable: Verify that the webhook URL is publicly accessible and not blocked by firewalls or network restrictions.
- Event filtering issues: Confirm that the selected event types in the node properties match the events being sent by WhatsApp.
- Empty workflow data: If the incoming event type is not included in the selected events list, the node will return no data.