Zalo User icon

Zalo User

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

Overview

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

Practical examples include:

  • Automatically unblocking users who meet certain criteria in your workflow.
  • Managing user relationships dynamically based on external triggers or data changes.
  • Integrating Zalo user management into broader automation processes.

Properties

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

Output

The node outputs JSON data containing the status of the unblock operation and the response from the Zalo API. The structure is:

{
  "status": "success",
  "response": { /* API response object */ }
}
  • status: Indicates whether the unblock action was successful.
  • response: Contains detailed information returned by the Zalo API about the unblock request.

No binary data output is produced by this node.

Dependencies

  • Requires valid Zalo API credentials configured in n8n to authenticate requests.
  • Uses an internal Zalo API client library to perform operations such as unblocking users.
  • The node depends on proper configuration of authentication tokens or cookies to establish API sessions.

Troubleshooting

  • Common issues:

    • Invalid or expired API credentials can cause authentication failures.
    • Providing an incorrect or non-existent User ID will result in errors from the Zalo API.
    • Network connectivity problems may prevent the node from reaching the Zalo service.
  • Error messages:

    • "No API instance found. Please make sure to provide valid credentials."
      Means the node could not initialize the API client due to missing or invalid credentials. Verify your credential setup.
    • Errors returned from the Zalo API are passed through; check the error message for details such as invalid user ID or permission issues.
    • If the node is set to continue on fail, errors for individual items will be included in the output JSON under an error field.

Links and References

Discussion