Zalo User icon

Zalo User

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

Actions12

Overview

This node manages Zalo user interactions, specifically for marking 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 management workflows or integrating Zalo messaging status updates into other systems.

For example, you can use this node to:

  • Mark all messages in a specific chat thread as read after processing them.
  • Flag certain conversations as unread to remind users to revisit them 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., personal 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 confirming the action taken (marking messages as read or unread).

The output is paired with the input item index to maintain data consistency.

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 for interacting with the Zalo API.

Troubleshooting

  • Common issues:
    • Invalid or expired credentials may cause login failure.
    • Incorrect Thread ID or Thread Type values can result in errors or no effect.
  • Error messages:
    • "No API instance found. Please make sure to provide valid credentials." — indicates missing or invalid authentication details.
    • Errors thrown during execution typically include the error message from the Zalo API; enabling "Continue On Fail" allows processing subsequent items despite individual failures.

To resolve these:

  • Verify that the API key credential is correctly configured and active.
  • Ensure the Thread ID and Thread Type correspond to existing conversations.
  • Check that the cookie, IMEI, and user agent are properly set either in credentials or incoming data.

Links and References

Discussion