Actions20
- Zalo Send Message Actions
- Gửi tin nhắn
- Gửi trạng thái tin nhắn
- Lấy danh sách sticker
- Lấy chi tiết sticker
- Gửi sticker
- Thả Reaction
- Gửi tin nhắn thoại
- Gửi danh thiếp
- Gửi Video
- Gửi Link
- Chuyển Tiếp Tin Nhắn
- Thêm Tin Nhắn Nhanh
- Lấy Danh Sách Tin Nhắn Nhanh
- Cập Nhật Tin Nhắn Nhanh
- Xóa Tin Nhắn Nhanh
- Đánh Dấu Chưa Đọc
- Bỏ Đánh Dấu Chưa Đọc
- Lấy Danh Sách Đánh Dấu Chưa Đọc
- Zalo Text To Speech Actions
Zalo Send Message → Bỏ Đánh Dấu Chưa Đọc
AI-generatedOverview
This node interacts with the Zalo API to manage message read status in conversations. Specifically, for the 'Bỏ Đánh Dấu Chưa Đọc' (Remove Unread Mark) operation, it removes the unread mark from a specified chat thread, either a personal or group conversation. This is useful in scenarios where you want to programmatically mark messages as read after processing or viewing them, ensuring the conversation no longer appears as unread in the Zalo app.
Use Case Examples
- Automatically mark a chat as read after a customer support bot processes the messages.
- Clear unread marks on group chats after a scheduled review of messages.
Properties
| Name | Meaning |
|---|---|
| ID cuộc trò chuyện / Thread ID | The ID of the chat thread from which to remove the unread mark. This identifies the specific conversation to update. |
| Loại cuộc trò chuyện | The type of the chat thread, either personal (Cá nhân) or group (Nhóm). This determines how the API treats the thread ID. |
Output
JSON
success- Indicates if the operation to remove the unread mark was successful.response- The response data returned from the Zalo API after attempting to remove the unread mark.
Dependencies
- Zalo API credentials with cookie-based authentication
Troubleshooting
- Ensure the Zalo API credentials are correctly set and valid, as the node requires successful login to the Zalo API.
- If the node throws an error about API initialization, verify the cookie and other credential details.
- The thread ID must be valid and correspond to an existing conversation; otherwise, the API call may fail.
- If the operation fails, check network connectivity and API rate limits or restrictions.