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/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, or integrating Zalo user management into broader workflows. For example, you could automatically unblock users based on certain triggers or conditions in your workflow, enabling smoother communication and relationship management on the Zalo platform.

Properties

Name Meaning
User ID The ID of the Zalo 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 details about the unblocked user or confirmation data.

Example output JSON structure:

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

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, IMEI, and user agent strings to establish a session with Zalo.
  • The zca-js library is used internally 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 can cause authentication failures.
    • Missing or incorrect User ID input will prevent the unblock operation.
    • Network connectivity problems may lead to request timeouts or failures.

  • Error messages:

    • "No API instance found. Please make sure to provide valid credentials."
      This indicates that the node failed to create a valid API session, likely due to missing or invalid credentials. Verify your API key and credential setup.
    • Errors returned from the Zalo API will be passed through; check the error message for details such as invalid user IDs or permission issues.

  • To handle errors gracefully, enable the "Continue On Fail" option in the node settings to allow the workflow to proceed even if some items fail.

Links and References

Discussion