Zalo User icon

Zalo User

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

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, and updating account settings or avatars.

A practical example is retrieving detailed information about a specific Zalo user by their User ID, which can be used in customer support workflows or CRM integrations to personalize communication based on user data.

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 as returned by the Zalo API. The structure depends on the API response but typically includes user profile fields such as name, avatar, status, and other personal details.

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 uses stored cookies, device IMEI, and user agent strings from credentials or input data to establish a session with the Zalo API.
  • The zca-js library is used internally to interact with the Zalo API.

Troubleshooting

  • Invalid Credentials or Session: If the node throws an error indicating no API instance found, ensure that valid Zalo API credentials are provided, including a valid cookie, IMEI, and user agent.
  • User Not Found: If the specified User ID does not exist or is invalid, the API may return an error or empty response. Verify the User ID before running the node.
  • Rate Limits or API Errors: The Zalo API might impose rate limits or return errors due to request volume or malformed requests. Check API usage policies and ensure parameters are correct.
  • Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error messages in the output JSON under the error field.

Links and References

Discussion