Zalo User icon

Zalo User

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

Actions12

Overview

This node manages interactions with Zalo users, specifically focusing on marking messages as read or unread within a conversation thread. It is useful in scenarios where automated message status updates are needed, such as managing customer support chats or personal message organization. For example, after processing incoming messages, the node can mark them as read to keep track of handled conversations, or mark certain threads as unread to flag them for follow-up.

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 ("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. This node does not output binary data.

Example output JSON structure:

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

Dependencies

  • Requires an API key credential to authenticate with the Zalo platform.
  • Uses stored cookie, device IMEI, and user agent information for session management.
  • Depends on the external zca-js library for interacting with the Zalo API.
  • Node configuration must include valid Zalo credentials with appropriate permissions.

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."
      Resolution: Verify that the Zalo API credentials are correctly configured and have not expired.
    • Errors related to invalid parameters typically indicate incorrect Thread ID or Thread Type. Double-check these inputs.
    • If the node throws errors but continueOnFail is enabled, error details will appear in the output JSON under the error field.

Links and References

Discussion