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 for this node include automating social interactions on Zalo, managing friend lists, and updating user account details programmatically. For example, you can unblock a user who was previously blocked, enabling communication again without manual intervention in the Zalo app.

Properties

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

Output

The output JSON contains:

  • status: A string indicating the success of the operation, typically "Thành công" (Success).
  • response: The raw response from the Zalo API related to the unblock action, which may include confirmation details or status codes.

Example output JSON:

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

No binary data is output by this operation.

Dependencies

  • Requires an API key credential to authenticate with the Zalo API.
  • The node uses stored credentials including cookie, device IMEI, and user agent strings to establish a session.
  • The external library zca-js is used to interact with the Zalo API.
  • Proper configuration of the Zalo API credentials within n8n is necessary for successful execution.

Troubleshooting

  • Common issues:

    • Invalid or expired credentials may cause login failure.
    • Missing or incorrect User ID input will prevent the unblock operation.
    • 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 returned from the Zalo API will be passed through; check the error message for details.

  • Resolution tips:

    • Ensure the API credentials are correctly configured and up to date.
    • Validate that the User ID provided exists and is correct.
    • Use the "Continue On Fail" option if you want the workflow to proceed despite individual errors.

Links and References

Discussion