WhatsApp Presence Trigger
AI-generatedOverview
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 a team when a contact becomes available or starts typing.
Practical examples include:
- Sending alerts when a key contact comes online.
- Logging presence changes for analytics.
- Triggering follow-up messages when a user stops 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 webhook. |
| 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 structure includes the full body of the webhook request under the json field. This typically contains details about the presence update 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-based) that sends presence events to the webhook URL exposed by this node.
- No additional external services or API keys are required within the node itself, but the WhatsApp instance must be authenticated and authorized to send these events.
Troubleshooting
- No events triggering: Ensure the WhatsApp instance is correctly configured to send presence events to the webhook URL provided by this node.
- Empty workflow data: If the selected event types do not match incoming events, the node will not trigger. Verify that the "Events" property includes the event types your WhatsApp instance sends.
- Webhook URL unreachable: Confirm that the webhook URL is publicly accessible and correctly registered with the WhatsApp instance.
- Unexpected payload format: The node expects the event data in a specific structure; if the WhatsApp instance sends a different format, the node may not process it correctly.