Actions37
- Instance Actions
- Message Actions
- Group Actions
- Contact Actions
- Chat Actions
- Campaign Actions
- Chatbot Actions
Overview
The node integrates with the UazAPI service, providing automation capabilities for WhatsApp through over 90 endpoints. Specifically, for the Chat resource and the Mark as Read operation, this node marks a specified chat as read in WhatsApp.
This is useful in scenarios where you want to programmatically update the read status of chats, such as automating customer support workflows, marking messages as handled after processing, or syncing read statuses across systems.
Example use case:
After processing incoming messages from a chat, you can mark that chat as read automatically to keep your WhatsApp interface organized and indicate that no further action is needed on those messages.
Properties
| Name | Meaning |
|---|---|
| Chat Number | The phone number of the chat to mark as read, including country code (e.g., 5511999999999) |
Output
The output is a JSON object containing the response from the UazAPI endpoint that marks the chat as read. This typically includes confirmation of the action's success or failure details.
No binary data is output by this operation.
Example output structure (simplified):
{
"success": true,
"message": "Chat marked as read"
}
or in case of error:
{
"error": "Description of the error"
}
Dependencies
- Requires an active connection to the UazAPI service.
- Requires valid API credentials configured in n8n for authentication with UazAPI.
- The base URL for the UazAPI must be set in the credentials.
- The node uses HTTP POST requests to the
/chat/readendpoint of the UazAPI.
Troubleshooting
Common issues:
- Invalid or missing chat number format may cause the API call to fail.
- Authentication errors if API credentials are incorrect or expired.
- Network connectivity issues preventing access to the UazAPI endpoint.
- The chat number might not exist or be recognized by WhatsApp, leading to failure.
Error messages:
"Unauthorized"or similar indicates credential problems; verify API key/token."Chat not found"means the specified chat number does not correspond to an active chat."Invalid number format"suggests the chat number is incorrectly formatted; ensure it includes country code without "+".
Resolution tips:
- Double-check the chat number input format.
- Confirm API credentials and permissions.
- Test connectivity to the UazAPI service outside n8n.
- Use the "Check Number" operation to verify if the chat number exists before marking as read.
Links and References
- UazAPI Documentation (hypothetical link, replace with actual if available)
- WhatsApp Business API concepts for message and chat management
- n8n HTTP Request node documentation for understanding underlying request mechanics