Zalo User icon

Zalo User

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

Zalo User → Lấy danh sách bạn bè

AI-generated

Overview

This node manages Zalo user data by connecting to the Zalo platform using provided credentials. Specifically, the "Lấy danh sách bạn bè" (Get friends list) operation retrieves a list of friends for a Zalo user account. This is useful in scenarios where you want to automate interactions with a user's social network on Zalo, such as exporting friend lists, analyzing social connections, or integrating Zalo contacts into other workflows.

Practical examples include:

  • Exporting a limited number of friends from a Zalo account for marketing or CRM purposes.
  • Automating friend list retrieval to sync contacts with another system.
  • Building custom reports or notifications based on a user's social graph.

Properties

Name Meaning
Limit The maximum number of friends to retrieve. Default is 50.

Output

The output JSON contains a field named friends which holds an array of friend objects retrieved from the Zalo user account. Each friend object represents a single friend in the user's friend list.

Example structure of the output JSON:

{
  "friends": [
    {
      // friend details here
    },
    {
      // friend details here
    }
    // up to the specified limit
  ]
}

No binary data output is produced by this operation.

Dependencies

  • Requires valid Zalo API credentials including a cookie, IMEI, and user agent string to authenticate requests.
  • The node uses an internal Zalo API client class to perform login and fetch friend data.
  • Proper configuration of these credentials in n8n is necessary before use.

Troubleshooting

  • Authentication errors: If the node fails to log in, ensure that the provided credentials (cookie, IMEI, user agent) are correct and have not expired.
  • Empty friend list: Verify that the user account actually has friends and that the limit parameter is set appropriately.
  • API rate limits or changes: Since this node depends on Zalo's private API, any changes or restrictions on their side may cause failures.
  • Error handling: If an error occurs during execution, the node will either continue processing remaining items (if configured to continue on failure) or throw an error stopping the workflow.

Common error message example:

  • "Login failed": Indicates invalid or expired credentials; reauthenticate or update credentials.
  • "Request failed" or similar: Could indicate network issues or API changes; check connectivity and Zalo API status.

Links and References

  • Zalo Official Website
  • No official public API documentation is available; this node uses reverse-engineered or private APIs. Use with caution respecting Zalo's terms of service.

Discussion