Zalo User icon

Zalo User

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

Overview

This node interacts with the Zalo platform to manage and retrieve information about Zalo users. Specifically, for the "Zalo User" resource and the "Lấy thông tin người dùng" (Get user information) operation, it fetches detailed information about a specified Zalo user by their user ID.

Common scenarios where this node is beneficial include:

  • Retrieving profile details of a Zalo user for CRM or customer support purposes.
  • Integrating Zalo user data into workflows that require user verification or personalization.
  • Automating user data collection from Zalo for analytics or marketing campaigns.

Practical example:

  • Given a user ID, the node fetches the user's profile information such as name, avatar, status, or other public details available via the Zalo API, enabling downstream nodes to process or store this data.

Properties

Name Meaning
User ID The unique identifier of the Zalo user whose information you want to retrieve. This is a required string input.

Output

The output JSON contains the full user information object returned by the Zalo API for the specified user ID. This typically includes various user profile fields such as name, avatar URL, gender, birthday, and other metadata provided by Zalo.

Example output structure (simplified):

{
  "id": "123456789",
  "name": "Nguyen Van A",
  "avatar": "https://example.com/avatar.jpg",
  "gender": "male",
  "birthday": "1990-01-01",
  ...
}

No binary data output is produced by this operation.

Dependencies

  • Requires valid Zalo API credentials including an API key credential with cookie, IMEI, and user agent information.
  • The node uses an external Zalo SDK library (zca-js) to interact with the Zalo API.
  • Proper configuration of the Zalo API credentials in n8n is necessary to authenticate requests.

Troubleshooting

  • Invalid Credentials: If the node throws an error indicating no API instance found or authentication failure, verify that the Zalo API credentials are correctly configured and valid.
  • User Not Found: If the specified User ID does not exist or is invalid, the API may return an error or empty response. Double-check the User ID input.
  • Rate Limits or API Errors: The Zalo API might enforce rate limits or return errors due to network issues. Implement retry logic or check API status if errors persist.
  • 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