Actions29
- Sessions Actions
- Chats Actions
- Contacts Actions
- Groups Actions
- Messages Actions
Overview
This node integrates with a WhatsApp HTTP API to update the presence status of a group chat. It allows users to send a presence update (such as "available", "unavailable", or custom statuses) to a specified WhatsApp group identified by its JID (Jabber ID). This is useful for automating presence notifications in group conversations, for example, signaling availability or activity status within team chats or customer support groups.
Properties
| Name | Meaning |
|---|---|
| Phone | The session ID representing the phone number or account used to authenticate the request. Typically linked to the user's WhatsApp session. |
| To | The JID (Jabber ID) of the target WhatsApp group where the presence update will be sent. Format example: [email protected]. |
| Presence | The presence status message or state to post to the group. This could be values like "available", "unavailable", or any custom string indicating presence. |
Output
The node outputs JSON data reflecting the response from the WhatsApp HTTP API after attempting to post the presence update. This typically includes confirmation of success or details about the updated presence status. There is no indication that binary data is output by this node.
Dependencies
- Requires connection to a WhatsApp HTTP API service.
- Needs an API URL and authentication credentials configured in n8n (e.g., an API key or token).
- The node uses a credential containing the phone/session ID and base URL for the WhatsApp API.
Troubleshooting
- Invalid Session ID or Authentication Failure: If the session ID (Phone) is incorrect or expired, the API call will fail. Ensure the session ID is valid and the credentials are up to date.
- Incorrect Group JID: Providing an invalid or non-existent group JID will cause errors or no effect. Verify the group JID format and existence.
- Presence Value Issues: Sending unsupported or empty presence values might result in API errors. Use valid presence strings as expected by the WhatsApp API.
- API Connectivity Problems: Network issues or incorrect API URL configuration can prevent successful requests. Check connectivity and endpoint correctness.
Links and References
- WhatsApp Group JID Format Explanation
- Documentation for the specific WhatsApp HTTP API used (not provided here; refer to your API provider's docs).