Zalo User icon

Zalo User

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

Actions9

Overview

This node allows users to interact with Zalo's user management features, specifically focusing on unblocking a user by their User ID. It is useful in scenarios where you have previously blocked a user on Zalo and want to programmatically remove that block, restoring communication or interaction capabilities.

Practical examples include:

  • Automatically unblocking users after a certain condition is met (e.g., after a cooldown period).
  • Managing user blocks/unblocks in bulk via workflows.
  • Integrating Zalo user management into customer support or CRM systems.

Properties

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

Output

The node outputs JSON data containing two main fields:

  • status: A string indicating the success status of the unblock operation, typically "success".
  • response: The detailed response from the Zalo API regarding the unblock request, which may include confirmation or additional metadata.

The output is paired with the input item index for traceability in batch operations.

No binary data output is involved.

Example output structure:

{
  "status": "success",
  "response": {
    // API response details here
  }
}

Dependencies

  • Requires an API authentication token credential to connect to Zalo's API.
  • Uses a Zalo API client internally that requires valid session cookies, device identifiers, and user agent strings, all managed within the node.
  • No external environment variables are explicitly required beyond the configured credentials.

Troubleshooting

  • Common issues:

    • Invalid or expired API credentials leading to authentication failures.
    • Incorrect User ID format causing API errors.
    • Network connectivity problems preventing API calls.

  • Error messages:

    • If the node cannot establish a connection or authenticate, it throws an error indicating failure to connect to Zalo.
    • If the User ID is missing or invalid, the API may return an error that will be surfaced in the node output.
    • When running in batch mode, individual item errors are captured per item; enabling "Continue On Fail" allows processing other items despite some failures.

  • Resolutions:

    • Verify and update the API authentication token credential.
    • Ensure the User ID is correctly provided and corresponds to a valid Zalo user.
    • Check network access and firewall settings.

Links and References

Discussion