Actions9
Overview
This node, named "Zalo User," manages interactions with Zalo user accounts through various operations such as managing friend requests, blocking/unblocking users, changing account settings, and retrieving user information. Specifically, the operation "Lấy danh sách bạn bè" (Get all friends) fetches a list of friends for the authenticated Zalo user.
Common scenarios where this node is beneficial include:
- Automating social media workflows involving Zalo contacts.
- Integrating Zalo user data into CRM or marketing platforms.
- Managing friend lists programmatically for outreach or analysis.
- Synchronizing Zalo contacts with other systems.
For example, you can use this node to retrieve up to a specified number of friends from a Zalo account and then process or export that list for further use.
Properties
| Name | Meaning |
|---|---|
| Limit | The maximum number of friends to retrieve from the user's friend list. Default is 50. |
Output
The output JSON contains a single field:
friends: An array of friend objects representing the retrieved friends from the Zalo account. Each object corresponds to a friend’s details as returned by the Zalo API.
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 to authenticate with the Zalo platform.
- The node uses stored credentials including a cookie, device IMEI, and user agent string to establish a session with Zalo's API.
- The external library
zca-jsis used internally to interact with the Zalo API.
Troubleshooting
- Invalid Credentials or Session: If the node cannot create an API instance, it will throw an error indicating no API instance was found. Ensure that valid Zalo API credentials are provided, including a valid cookie, IMEI, and user agent.
- Rate Limits or API Errors: The Zalo API may impose rate limits or restrictions; if errors occur, verify API usage limits and permissions.
- Empty Friend List: If the friend list is empty, confirm that the authenticated user has friends and that the API credentials have sufficient access rights.
- Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error messages in the output JSON under the
errorfield.