Zalo User

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

Actions12

Zalo User Actions

Overview

This node manages interactions with Zalo users, specifically allowing you to mark messages as read or unread within a conversation thread. It is useful in scenarios where you want to programmatically update the read status of messages in Zalo chats, for example, to automate message handling workflows or synchronize message states between systems.

Practical examples:

Automatically marking all messages in a specific chat as read after processing them.
Marking certain conversations as unread to remind users to follow up later.

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 chat, group chat).

Output

The node outputs a JSON object containing:

status: A string indicating success, typically "Thành công" (meaning "Success").
response: The raw response from the Zalo API confirming the action taken.

Example output JSON:

{
  "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, device 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 that the API key credential is correctly configured and contains valid cookie, IMEI, and user agent data.
- Errors related to invalid parameters usually indicate incorrect Thread ID or Thread Type. Double-check these inputs.
- If the node throws errors but continueOnFail is enabled, it will return error details per item instead of stopping execution.