Zalo User icon

Zalo User

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

Actions10

Overview

This node manages Zalo user interactions through various operations such as blocking or unblocking users, managing friend requests, updating profile settings, and retrieving user information. It is particularly useful for automating social management tasks on the Zalo platform, such as moderating contacts by blocking unwanted users or handling friend requests programmatically.

For example, the "Chặn người dùng" (Block User) operation allows you to block a specific Zalo user by their user ID, which can be used in scenarios where you want to automate moderation or privacy controls within your Zalo account.

Properties

Name Meaning
User ID The ID of the Zalo user to block

Output

The output JSON contains:

  • status: A string indicating the result status, typically "Thành công" meaning "Success".
  • response: The raw response from the Zalo API related to the block user action, which may include confirmation details or metadata about the blocked user.

Example output JSON:

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

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential with valid Zalo API authentication, including cookie, IMEI, and user agent information.
  • Uses the external zca-js library to interact with the Zalo API.
  • Node configuration must include proper credentials to authenticate and authorize API calls.

Troubleshooting

  • Common issues:

    • Invalid or expired credentials will cause the node to fail to instantiate the API client.
    • Missing or incorrect User ID input will result in errors when attempting to block a user.

  • Error messages:

    • "No API instance found. Please make sure to provide valid credentials." indicates that the node could not authenticate with Zalo due to missing or invalid credentials. To resolve, verify and update the API key credential.
    • Errors thrown during the block user call will include the API error message; enabling "Continue On Fail" allows processing subsequent items despite individual failures.

Links and References

Discussion