Zalo User icon

Zalo User

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

Actions9

Overview

This node manages Zalo user interactions through various operations such as accepting friend requests, sending friend requests, blocking or unblocking users, changing account settings, and retrieving user information. Specifically, the "Bỏ chặn người dùng" (Unblock User) operation allows you to remove a block on a specified Zalo user by their user ID.

Common scenarios where this node is beneficial include automating social interactions on Zalo, managing friend lists programmatically, or integrating Zalo user management into broader workflows. For example, after temporarily blocking a user due to inappropriate behavior, you can automate unblocking them later based on certain conditions.

Properties

Name Meaning
User ID The ID of the user to unblock.

Output

The output JSON contains:

  • status: A string indicating the result status, e.g., "Thành công" meaning "Success".
  • response: The raw response from the Zalo API for the unblock operation, which may include details about the unblock action.

Example output JSON structure:

{
  "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 to authenticate with the Zalo API.
  • The node uses stored credentials including a cookie, device IMEI, and user agent string to establish a session with Zalo.
  • The external dependency is the zca-js library, which provides the interface to interact with Zalo's API.

Troubleshooting

  • Invalid Credentials: If the node throws an error like "No API instance found," it usually means the provided credentials are invalid or expired. Ensure that the API key credential and associated cookie, IMEI, and user agent are correctly configured.
  • User ID Not Found: Providing an incorrect or non-existent user ID may cause the unblock operation to fail. Verify the user ID before running the node.
  • API Rate Limits: Frequent calls to the Zalo API might hit rate limits; consider adding delays or handling errors gracefully.
  • Continue On Fail: If enabled, the node will continue processing other items even if one fails, returning error messages in the output JSON under the error field.

Links and References

Discussion