Actions12
Zalo User → Đánh Dấu Tin Nhắn Đã Đọc
AI-generatedOverview
This node operation allows users to mark messages as read or unread in a Zalo user conversation thread. It is useful for managing message statuses programmatically, such as automating the process of marking notifications as read after processing them or toggling message states based on user actions.
Practical examples include:
- Automatically marking all messages in a specific chat thread as read once they have been processed by another workflow.
- Marking messages as unread to remind users to revisit certain conversations.
- Integrating with customer support workflows where message read status affects ticket handling.
Properties
| Name | Meaning |
|---|---|
| Thread ID | The unique identifier of the user or conversation thread whose messages will be marked. |
| Thread Type | The type/category of the user or thread (e.g., individual, group). |
Output
The output JSON contains at least two fields:
status: A string indicating the result status of the operation (e.g., "success").response: The detailed response from the underlying API call confirming the action taken.
The node does not explicitly output binary data.
Dependencies
- Requires an active authenticated session with Zalo's API, including necessary cookies, device identifiers, and user agent strings.
- The node depends on an internal Zalo API client class that handles communication with Zalo services.
- Proper credentials must be configured in n8n to provide authentication tokens or cookies required by the Zalo API.
Troubleshooting
Common issues:
- Authentication failures due to expired or invalid cookies or tokens.
- Invalid or missing Thread ID or Thread Type parameters.
- Network connectivity problems when reaching Zalo's API endpoints.
Error messages:
- Errors related to missing authentication will prompt users to check their credential setup.
- If the thread ID is incorrect or does not exist, the API may return an error which the node surfaces.
- Unexpected errors during API calls are caught and returned per item; ensure proper error handling in workflows.
Resolutions:
- Verify and refresh API credentials or cookies.
- Confirm the correctness of Thread ID and Thread Type values.
- Check network access and firewall settings.
Links and References
- Zalo Official Developer Documentation
- Zalo Messaging API Reference
- n8n documentation on Creating Custom Nodes
Note: The source code was obfuscated, but key logic and property usage were extracted through static analysis without executing or deobfuscating runtime behavior.