Zalo User icon

Zalo User

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

Actions9

Overview

This node interacts with the Zalo platform to retrieve user information based on a given User ID. It is designed for scenarios where you need to fetch detailed data about a specific Zalo user, such as in customer support automation, user verification processes, or social media analytics workflows.

For example, you might use this node to:

  • Automatically pull profile details of a user who has interacted with your chatbot.
  • Verify user identity by fetching their public information.
  • Aggregate user data for marketing or engagement analysis.

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 node outputs JSON data containing the status and the response from the Zalo API regarding the requested user's information. The structure typically looks like:

{
  "status": "Thành công",
  "response": {
    // user information fields returned by Zalo API
  }
}
  • status: A string indicating the success of the operation (e.g., "Thành công" means "Success").
  • response: An object containing detailed user information as provided by the Zalo service.

The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating requests to the Zalo platform.
  • Uses stored cookies, IMEI, and user agent strings from credentials or previous executions to authenticate and interact with the Zalo API.
  • Relies on an internal Zalo API client class to perform operations.

Troubleshooting

  • Common issues:

    • Invalid or expired API credentials can cause authentication failures.
    • Incorrect or missing User ID will result in errors or empty responses.
    • Network connectivity problems may prevent successful API calls.

  • Error messages:

    • If the node cannot instantiate the Zalo API client due to missing credentials or invalid data, it throws an error indicating failure to create the client.
    • Errors during API calls are caught and either returned as part of the output (if the node is set to continue on failure) or thrown as operation errors with item index information.

  • Resolutions:

    • Ensure that valid API credentials are configured in n8n.
    • Verify that the User ID input is correctly provided and corresponds to an existing Zalo user.
    • Check network access and firewall settings to allow outbound connections to Zalo's API endpoints.

Links and References

Discussion