Zalo User icon

Zalo User

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

Overview

This node manages Zalo user interactions, specifically allowing you to unblock a user on the Zalo platform. It is useful in scenarios where you have previously blocked a user and want to restore communication with them. For example, if you manage customer relationships or social contacts via Zalo, this node can automate unblocking users based on certain triggers or workflows.

Practical example: Automatically unblock a user after resolving a support issue, enabling further messaging without manual intervention.

Properties

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

Output

The node outputs a JSON object containing:

  • status: A string indicating the operation result, 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's success or metadata.

Example output JSON:

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

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential to authenticate with the Zalo platform.
  • Uses stored credentials including cookie, device IMEI, and user agent strings to establish a session.
  • Depends on the external zca-js library to interact with the Zalo API.
  • Proper configuration of the Zalo API credentials within n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or expired credentials leading to failure in creating an API instance.
    • Missing or incorrect User ID parameter causing errors.
    • Network or API rate limiting issues from Zalo.
  • Error messages:

    • "No API instance found. Please make sure to provide valid credentials."
      This indicates that authentication failed; verify your API key and credential details.
    • Errors related to invalid user IDs or permissions will be returned from the API and surfaced as node errors.
  • Resolution tips:

    • Ensure credentials are up-to-date and correctly configured.
    • Validate the User ID input before running the node.
    • Use the "Continue On Fail" option to handle individual item errors gracefully in batch operations.

Links and References

Discussion