Zalo User icon

Zalo User

Quản lý người dùng Zalo - Kết bạn, chặn, đổi tên, lấy thông tin và quản lý danh sách bạn bè

Actions12

Overview

This node interacts with the Zalo messaging platform to mark messages in a conversation thread as read or unread. It is useful for automating message management tasks such as acknowledging receipt of messages or resetting their read status programmatically.

Common scenarios include:

  • Automatically marking all messages from a specific user or group as read after processing them.
  • Resetting the read status of messages to unread for follow-up or reminders.
  • Integrating with workflows that require message state synchronization between Zalo and other systems.

For example, you could use this node to mark all messages in a customer support chat as read once the ticket is closed, ensuring agents see only new incoming messages.

Properties

Name Meaning
Thread ID The unique identifier of the conversation thread (user or group) whose messages will be marked.
Thread Type The type/category of the thread (e.g., individual user, group chat).

Output

The node outputs JSON data containing the status of the operation and the response from the Zalo API. The typical structure is:

{
  "status": "Thành công",
  "response": { /* API response object */ }
}
  • status: A string indicating success ("Thành công") or failure.
  • response: Contains detailed information returned by the Zalo API about the marking operation.

The node does not output binary data.

Dependencies

  • Requires an active connection to the Zalo API via an API key credential configured in n8n.
  • Uses stored authentication details including cookies, device IMEI, and user agent strings to authenticate requests.
  • Relies on an internal Zalo API client library bundled with the node for communication.

Troubleshooting

  • Common issues:

    • Invalid or expired authentication credentials may cause failures.
    • Incorrect Thread ID or Thread Type can result in errors or no effect.
    • Network connectivity problems can prevent successful API calls.

  • Error messages:

    • If the node throws an error about missing or invalid credentials, verify that the API key and authentication details are correctly set up.
    • Errors related to "NodeOperationError" typically indicate API call failures; check the provided error message for specifics.
    • If the response indicates failure, confirm that the Thread ID corresponds to an existing conversation and that the user has permission to modify it.

  • Resolution tips:

    • Refresh or reauthenticate your Zalo API credentials if authentication errors occur.
    • Double-check input parameters for correctness.
    • Ensure network access to Zalo's API endpoints is available.

Links and References

Discussion