Zalo User icon

Zalo User

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

Actions12

Overview

This node manages Zalo user interactions, specifically for the "Bỏ Chặn Người Dùng" (Unblock User) operation. It allows unblocking a previously blocked user on the Zalo platform by specifying their user ID. This is useful in scenarios where you want to restore communication with users who were blocked earlier, such as customer support reopening conversations or re-engaging contacts.

Practical example:

  • A business had blocked a user due to spam but later decides to unblock them to resume communication. Using this node, they provide the user's ID and unblock them programmatically within an automation 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 after attempting to unblock the user. This may include details about the unblock action's success or any returned metadata.

Example output JSON:

{
  "status": "Thành công",
  "response": {
    // API response details here
  }
}

No binary data is produced by this operation.

Dependencies

  • Requires valid Zalo API credentials including authentication tokens such as cookies, device IMEI, and user agent strings.
  • The node uses an external Zalo SDK library (zca-js) to interact with the Zalo API.
  • Credentials must be configured properly in n8n to allow authenticated API calls.

Troubleshooting

  • Common issues:

    • Invalid or expired credentials can cause authentication failures.
    • Providing an incorrect or non-existent User ID will likely result in an error from the API.
    • Network connectivity problems may prevent successful API calls.

  • Error messages:

    • "No API instance found. Please make sure to provide valid credentials."
      Means the node could not authenticate with Zalo API. Check that credentials are correctly set and valid.
    • Errors returned from the API (e.g., user not found, permission denied) will be thrown and can be caught if "Continue On Fail" is enabled.

  • Resolution tips:

    • Verify and refresh your Zalo API credentials.
    • Confirm the User ID exists and is correct.
    • Enable "Continue On Fail" to handle errors gracefully in workflows.

Links and References

Discussion