Zalo User icon

Zalo User

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

Overview

This node manages interactions with Zalo users, specifically allowing operations such as accepting friend requests, sending friend requests, blocking/unblocking users, changing alias names, retrieving user info, and more. It is useful for automating social interactions on the Zalo platform, such as managing contacts or moderating friend lists.

A practical example is automatically accepting incoming friend requests from a list of user IDs, which can streamline community management or customer engagement workflows.

Properties

Name Meaning
User ID The unique identifier of the user to perform the operation on.

For the "Chấp nhận lời mời kết bạn" (Accept Friend Request) operation, only the User ID property is required.

Output

The output JSON structure typically contains:

  • status: A string indicating the result status, e.g., "Thành công" meaning "Success".
  • response: The raw response data returned by the Zalo API for the performed operation.

Example output JSON for accepting a friend request:

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

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential to authenticate with the Zalo platform.
  • Uses stored cookies, IMEI, and user agent strings from credentials or input data for authentication.
  • Depends on the external zca-js library to interact with the Zalo API.

Troubleshooting

  • Common issues:

    • Invalid or expired credentials may cause login failure.
    • Missing or incorrect User ID will prevent the operation from succeeding.
    • Network connectivity problems can interrupt API calls.
  • Error messages:

    • "No API instance found. Please make sure to provide valid credentials."
      This indicates that authentication failed; verify your API key and credential setup.
    • Errors thrown during API calls will be reported with their message; enabling "Continue On Fail" allows processing subsequent items despite errors.

Links and References

Discussion