Zalo User icon

Zalo User

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

Actions9

Overview

This node interacts with the Zalo platform to manage and retrieve information about Zalo users. It is useful for automating user-related tasks such as fetching user details, managing friend requests, blocking/unblocking users, updating account settings, and more.

A practical example is using this node to get detailed information about a specific Zalo user by their User ID, which can be helpful in customer support workflows or CRM integrations where you need to enrich contact data with Zalo profile information.

Properties

Name Meaning
User ID The ID of the Zalo user whose information you want to retrieve

Output

The output JSON contains the detailed information of the requested Zalo user. The structure corresponds directly to the data returned by the Zalo API's getUserInfo method, typically including user profile fields such as name, avatar, status, and other relevant user metadata.

Example output snippet (simplified):

{
  "id": "123456789",
  "name": "Nguyen Van A",
  "avatar": "https://example.com/avatar.jpg",
  "status": "Online",
  ...
}

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential to authenticate with the Zalo platform.
  • The node depends on a third-party library (zca-js) to interact with the Zalo API.
  • Proper configuration of credentials including cookie, IMEI, and user agent values is necessary for successful API calls.

Troubleshooting

  • Common issues:

    • Invalid or expired credentials may cause authentication failures.
    • Missing or incorrect User ID input will result in errors or empty responses.
    • Network connectivity problems can prevent API communication.

  • Error messages:

    • "No API instance found. Please make sure to provide valid credentials."
      This indicates that the node could not establish a connection to the Zalo API due to missing or invalid credentials. Verify your API key and related authentication parameters.
    • Errors thrown during execution are paired with the input item index for easier debugging.
    • If "Continue On Fail" is enabled, errors will be returned in the output JSON under an error field instead of stopping the workflow.

Links and References

Discussion