Actions12
Overview
This node interacts with the Zalo messaging platform, specifically targeting user-related operations. The selected operation "Đánh Dấu Tin Nhắn Chưa Đọc" (Mark Message As Unread) allows users to mark messages in a conversation thread as unread. This can be useful for managing message notifications or reminding oneself to revisit certain conversations later.
Practical scenarios include:
- Automatically marking important messages as unread to ensure follow-up.
- Managing message states programmatically in bulk for customer support workflows.
- Integrating Zalo messaging status updates into broader automation pipelines.
Properties
| Name | Meaning |
|---|---|
| Thread ID | The unique identifier of the conversation thread where the message(s) will be marked. |
| Thread Type | The type/category of the user or thread (e.g., individual chat, group chat). |
Output
The node outputs JSON data containing the status and response from the Zalo API after attempting to mark messages as unread. The structure is:
{
"status": "success",
"response": { /* API response object */ }
}
status: A string indicating the success of the operation, typically "success".response: Contains detailed information returned by the Zalo API about the operation result.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Zalo API via an API key credential configured in n8n.
- Uses stored authentication details such as cookies, device IMEI, and user agent strings to authenticate requests.
- Relies on an internal Zalo API client library bundled within the node's codebase.
Troubleshooting
Common Issues:
- Invalid or expired authentication credentials may cause failures.
- Incorrect Thread ID or Thread Type values can lead to errors or no effect.
- Network connectivity issues with the Zalo API endpoint.
Error Messages:
- Errors thrown by the node typically contain the API error message.
- If the node cannot initialize the Zalo API client due to missing or invalid credentials, it throws a generic operation error.
Resolutions:
- Verify that the API key credential is correctly set up and valid.
- Double-check the Thread ID and Thread Type inputs for correctness.
- Ensure stable internet connectivity and access to the Zalo API.
Links and References
- Zalo Official Developer Documentation
- Zalo Messaging API Reference
- n8n Documentation on Creating Custom Nodes