Zalo User icon

Zalo User

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

Actions10

Overview

This node manages Zalo user interactions, specifically for the "Zalo User" resource. The "Bỏ chặn người dùng" (Unblock User) operation allows you to unblock a previously blocked user on Zalo by specifying their user ID. This is useful in scenarios where you want to restore communication with users you had blocked before.

Practical examples:

  • Unblocking a user who was mistakenly blocked.
  • Automating the process of unblocking users after a certain condition or time period.
  • Managing user relationships programmatically within a workflow.

Properties

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

Output

The output JSON contains two main fields:

  • status: A string indicating the result status, typically "Thành công" meaning "Success".
  • response: The raw response from the Zalo API for the unblock action, which may include details about the unblock operation.

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, device IMEI, and user agent strings to establish a session.
  • The external dependency is the zca-js library, which provides the interface to interact with Zalo's API.

Troubleshooting

  • Common issues:

    • Invalid or expired credentials can cause login failure.
    • Missing or incorrect user ID will prevent the unblock operation.
    • Network or API errors from Zalo service.

  • Error messages:

    • "No API instance found. Please make sure to provide valid credentials."
      Means the node could not authenticate with Zalo API. Check your API key and credential details.
    • Errors thrown during the unblock call will be reported with the specific message from the API. If Continue On Fail is enabled, the error will be returned in the output JSON under error.

  • Resolution tips:

    • Verify that the API credentials are correct and have not expired.
    • Ensure the user ID provided exists and is currently blocked.
    • Enable "Continue On Fail" to handle errors gracefully in batch operations.

Links and References

Discussion