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 profile data of a specified Zalo user by their user ID.

Common scenarios where this node is beneficial include:

  • Integrating Zalo user data into CRM or marketing automation workflows.
  • Fetching user details dynamically during customer support processes.
  • Enriching contact records with up-to-date Zalo profile information.

Practical example:

  • Given a user ID, the node retrieves that user's profile information such as name, avatar, status, or other public details available via the Zalo API, enabling downstream nodes to use this data for personalized messaging or analytics.

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 profile fields such as name, avatar URL, gender, birthday, and other publicly accessible user details.

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

  • Common issues:

    • Invalid or expired credentials may cause authentication failures.
    • Providing an incorrect or non-existent user ID will result in errors or empty responses.
    • Network connectivity problems can prevent successful API calls.
  • Error messages:

    • "No API instance found. Please make sure to provide valid credentials."
      Means the node could not initialize the Zalo API client due to missing or invalid credentials. Verify your API key and credential setup.
    • Errors thrown from the API (e.g., user not found) will be surfaced. If Continue On Fail is enabled, these errors will appear in the output JSON under an error field.
  • Resolution tips:

    • Double-check the user ID format and existence.
    • Ensure the Zalo API credentials are correctly configured and have not expired.
    • Enable "Continue On Fail" if you want the workflow to proceed despite individual item errors.

Links and References

Discussion