Zalo User

Quản lý người dùng Zalo

Actions12

Zalo User Actions

Overview

This node manages interactions with Zalo users, a popular messaging platform. Specifically, the "Đánh Dấu Tin Nhắn Chưa Đọc" (Mark Message as Unread) operation allows users to mark messages in a conversation thread as unread. This can be useful for workflows that need to flag certain conversations for follow-up or review later.

Practical examples include:

Automatically marking important messages as unread to remind a user to respond.
Managing message states in bulk based on external triggers or conditions.
Integrating with other systems to synchronize message read/unread status.

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 conversation thread (e.g., individual chat, group chat).

Output

The node outputs a JSON object containing:

status: A string indicating success ("Thành công").
response: The raw response from the Zalo API after attempting to mark the message as unread.

Example output JSON structure:

{
  "status": "Thành công",
  "response": { /* API response details */ }
}

No binary data is produced by this operation.

Dependencies

Requires an API key credential to authenticate with the Zalo platform.
Uses stored cookie, IMEI, and user agent information from credentials or input data to establish a session.
Depends on the external zca-js library to interact with the Zalo API.

Troubleshooting

Common issues:
- Invalid or expired credentials may cause authentication failures.
- Incorrect Thread ID or Thread Type values can lead to errors or no effect.
- Network connectivity problems might prevent successful API calls.
Error messages:
- "No API instance found. Please make sure to provide valid credentials."
  Means the node could not authenticate with Zalo. Verify your API key and credential details.
- Errors returned from the Zalo API will be passed through; check the error message for specifics.
Resolution tips:
- Ensure all required properties (Thread ID, Thread Type) are correctly set.
- Confirm that the API credentials are up to date and have necessary permissions.
- Use the node's "Continue On Fail" option to handle errors gracefully in workflows.