Zalo User icon

Zalo User

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

Actions9

Overview

This node interacts with the Zalo platform to manage user-related actions, specifically for the "Zalo User" resource. The operation "Bỏ chặn người dùng" (Unblock User) allows unblocking a previously blocked user by their User ID. This is useful in scenarios where you want to restore communication or interaction capabilities with a user who was blocked before.

Practical examples include:

  • Unblocking a user who was mistakenly blocked.
  • Re-enabling interactions with a user after resolving conflicts.
  • Managing user access dynamically based on business logic or user requests.

Properties

Name Meaning
User ID The unique identifier of the user to unblock

Output

The output JSON contains the following structure:

{
  "status": "Thành công",
  "response": { /* response data from the unblock action */ }
}
  • status: A string indicating the success of the operation, typically "Thành công" (Success).
  • response: Contains the detailed response returned by the Zalo API after attempting to unblock the user.

The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the Zalo platform.
  • Uses cookies, IMEI, and user agent strings as part of the authentication/session management.
  • Depends on an external Zalo API client library internally to perform the unblock operation.
  • The node expects proper configuration of credentials within n8n to access the Zalo API.

Troubleshooting

  • Common issues:

    • Invalid or expired API credentials can cause authentication failures.
    • Incorrect User ID input may result in errors or no action taken.
    • Network connectivity problems can prevent successful API calls.

  • Error messages:

    • If the node throws an error related to missing or invalid credentials, verify that the API key and session details are correctly configured.
    • Errors indicating "cookie" or "userAgent" missing suggest incomplete credential setup.
    • API errors returned from Zalo will be included in the output's error field if the node is set to continue on failure.

  • Resolution tips:

    • Double-check the User ID format and ensure it corresponds to a valid Zalo user.
    • Refresh or re-enter API credentials if authentication fails.
    • Enable "Continue on Fail" in the node settings to handle individual item errors gracefully.

Links and References

Discussion