Zalo User icon

Zalo User

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

Actions12

Zalo User → Lấy Danh Sách Bạn Bè

AI-generated

Overview

This node interacts with the Zalo social platform to manage user-related operations. Specifically, for the "Zalo User" resource and the "Lấy Danh Sách Bạn Bè" (Get All Friends) operation, it retrieves a list of friends from a Zalo user account.

Common scenarios where this node is beneficial include:

  • Synchronizing a user's Zalo friend list with another system.
  • Analyzing or processing social connections for marketing or CRM purposes.
  • Automating workflows that require access to a user's social graph on Zalo.

For example, you could use this node to fetch up to 50 friends of a user and then send them personalized messages or invitations through other nodes in your workflow.

Properties

Name Meaning
Limit The maximum number of friends to retrieve. This limits how many friends are returned by the operation. Default is 50.

Output

The output JSON contains a single field:

  • friends: An array of friend objects representing the user's friends on Zalo. Each object includes details about an individual friend (the exact structure depends on the Zalo API response).

Example output structure:

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

No binary data is output by this operation.

Dependencies

  • Requires valid Zalo API credentials including authentication cookies, device IMEI, and user agent strings.
  • The node uses an external Zalo SDK/library (zca-js) to interact with the Zalo API.
  • Credentials must be configured properly in n8n to provide necessary authentication tokens and session information.

Troubleshooting

  • Invalid or expired credentials: If the node fails to authenticate, ensure that the provided cookie, IMEI, and user agent are current and valid.
  • No API instance found error: This indicates missing or invalid credentials; recheck credential configuration.
  • Limit parameter issues: Providing a non-numeric or negative limit may cause unexpected behavior; always provide a positive integer.
  • API rate limits or network errors: These can cause failures; consider adding retry logic or handling errors gracefully using the node's "Continue On Fail" option.

Links and References

Discussion