Overview
The ZuckZapGo Chat node enables various chat-related operations using the ZuckZapGo WhatsApp API. It is designed to interact with WhatsApp chats programmatically, allowing users to manage messages and presence indicators efficiently.
For the Mark as Read operation specifically, this node marks one or more specified messages in a given chat as read. This is useful for automating message status updates, such as confirming that certain messages have been seen without manual intervention.
Practical examples:
- Automatically marking incoming messages as read after processing them in a workflow.
- Syncing message read status across multiple devices or systems.
- Managing customer support chats by marking handled messages as read.
Properties
| Name | Meaning |
|---|---|
| Message IDs | Comma-separated list of message IDs to mark as read (e.g., AABBCC11223344,DDEEFF55667788). |
| Chat JID | The unique identifier (JID) of the chat containing the messages (e.g., 5491155553934.0:1@s.whatsapp.net). |
| Sender JID | (Optional) The JID of the message sender (e.g., 5491155553111.0:1@s.whatsapp.net). |
Output
The node outputs JSON data representing the response from the ZuckZapGo WhatsApp API after attempting to mark the specified messages as read. The structure typically includes confirmation details about the operation's success or failure.
No binary data output is produced for this operation.
Dependencies
- Requires an active connection to the ZuckZapGo WhatsApp API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The node uses the
/chat/markreadendpoint of the ZuckZapGo API.
Troubleshooting
Common issues:
- Invalid or malformed message IDs can cause the API request to fail.
- Incorrect or missing Chat JID will prevent the node from identifying the target chat.
- If the API key or authentication token is invalid or expired, requests will be rejected.
Error messages:
- Errors returned from the API usually include descriptive messages indicating the problem (e.g., "Invalid message ID", "Chat not found").
- Network or connectivity errors may occur if the API service is unreachable.
Resolutions:
- Verify that all message IDs are correct and properly formatted.
- Ensure the Chat JID corresponds exactly to the intended chat.
- Confirm that the API credentials are valid and have sufficient permissions.
- Check network connectivity and API service status.
Links and References
- ZuckZapGo WhatsApp API Documentation (hypothetical link for reference)
- WhatsApp JID Format Explanation (general info on JIDs)