Zalo User icon

Zalo User

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

Actions12

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, such as automating message handling workflows, managing notifications, or syncing message states between systems.

For example, you could use this node to:

  • Mark all messages in a specific chat as read after processing them.
  • Mark certain conversations as unread to remind yourself or others 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 for each input item processed, containing:

  • status: A string indicating success ("Thành công" means "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 node.

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

  • Invalid Credentials: If the node throws an error about no API instance found, verify that the provided API key credential contains valid cookie, IMEI, and user agent values.
  • Missing Required Parameters: Ensure that both "Thread ID" and "Thread Type" are provided; otherwise, the API call will fail.
  • API Errors: Any errors returned by the Zalo API will be surfaced. Use the error message to check if the thread ID is correct or if the user has permission to modify the message status.
  • Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.

Links and References

Discussion