Zalo User icon

Zalo User

Quản lý người dùng Zalo - Kết bạn, chặn, đổi tên, lấy thông tin và quản lý danh sách bạn bè

Actions12

Overview

This node integrates with the Zalo platform to manage user-related operations, specifically focusing on interactions with a user's friends list. The "Lấy Danh Sách Bạn Bè" (Get All Friends) operation retrieves a list of friends for the authenticated Zalo user. This is useful in scenarios where you want to automate social interactions, analyze friend networks, or synchronize contacts from Zalo into other systems.

Practical examples include:

  • Fetching a limited number of friends to display in a dashboard.
  • Exporting friend lists for marketing or CRM purposes.
  • Automating messaging or notifications to friends retrieved from Zalo.

Properties

Name Meaning
Limit Maximum number of friends to retrieve.

The "Limit" property controls how many friends are fetched from the user's friend list, allowing users to restrict the volume of data returned.

Output

The output JSON contains a field named friends, which is an array of friend objects. Each object represents a friend of the authenticated user. The exact structure of each friend object depends on the Zalo API response but typically includes identifiers and profile information.

Example output structure:

{
  "friends": [
    {
      "id": "123456789",
      "name": "Friend Name",
      "avatar": "https://example.com/avatar.jpg",
      ...
    },
    ...
  ]
}

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Zalo API.
  • The node uses stored authentication details such as cookies, IMEI, and user agent strings to establish sessions with Zalo.
  • No additional external dependencies beyond the Zalo API and its authentication mechanism.

Troubleshooting

  • Common Issues:

    • Authentication failures due to expired or invalid credentials.
    • Exceeding API rate limits imposed by Zalo.
    • Network connectivity problems preventing API calls.

  • Error Messages:

    • If the session cannot be established, the node throws an error indicating failure to create a client instance.
    • Errors during API calls return messages that can be captured and optionally continue processing if configured.

  • Resolutions:

    • Ensure valid and up-to-date API credentials are provided.
    • Check network connectivity and firewall settings.
    • Handle errors gracefully by enabling the node's option to continue on failure if partial results are acceptable.

Links and References

Discussion