Zalo User icon

Zalo User

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

Actions12

Zalo User → Bỏ Chặn Người Dùng

AI-generated

Overview

This node is designed to interact with the Zalo platform, specifically to unblock a user who was previously blocked. It is useful in scenarios where you want to restore communication or interaction capabilities with a particular Zalo user by removing any block restrictions.

Practical examples include:

  • Customer support workflows where a user was mistakenly blocked and needs to be unblocked automatically.
  • Social media management automation that manages user interactions on Zalo.
  • Re-enabling messaging or friend requests from a user after resolving an issue.

Properties

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

Output

The node outputs JSON data containing the status of the unblock operation and the response from the Zalo API or service. The structure typically looks like:

{
  "status": "success",
  "response": { /* detailed response object from Zalo API */ }
}

Each output item corresponds to one input item processed, paired by index.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the Zalo platform.
  • Uses an internal Zalo API client class instantiated with authentication cookies, device identifiers, and user agent strings.
  • The node expects these credentials and session details to be properly configured in n8n.

Troubleshooting

  • Common issues:

    • Invalid or expired authentication tokens may cause the unblock request to fail.
    • Incorrect or missing User ID input will prevent the operation from executing.
    • Network or API errors from Zalo can interrupt the process.

  • Error messages:

    • If the internal Zalo API client instance is not created successfully, the node throws an error indicating missing or invalid credentials.
    • Errors during the unblock call are caught and returned as JSON error objects per item if the node is set to continue on failure; otherwise, they cause the workflow to stop.

  • Resolutions:

    • Ensure valid and up-to-date API credentials are provided.
    • Verify the User ID is correct and exists on Zalo.
    • Check network connectivity and Zalo API status.

Links and References

Discussion