Actions9
Overview
This node interacts with the Zalo platform to manage and retrieve information about Zalo users. It is useful for automating user-related tasks such as fetching user details, managing friend requests, blocking/unblocking users, updating account settings, and more.
A practical example is retrieving detailed information about a specific Zalo user by their User ID, which can be used in customer support workflows or CRM integrations to personalize communication based on user data.
Properties
| Name | Meaning |
|---|---|
| User ID | The ID of the Zalo user whose information you want to retrieve |
Output
The output JSON contains the detailed information of the requested Zalo user as returned by the Zalo API. The structure depends on the API response but typically includes user profile fields such as name, avatar, status, and other personal details.
Example output snippet (simplified):
{
"id": "123456789",
"name": "Nguyen Van A",
"avatar": "https://example.com/avatar.jpg",
"status": "Online",
...
}
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 cookies, device IMEI, and user agent strings from credentials or input data to establish a session with the Zalo API.
- The
zca-jslibrary is used internally to interact with the Zalo API.
Troubleshooting
Common issues:
- Invalid or expired credentials may cause authentication failures.
- Missing or incorrect User ID input will result in errors or empty responses.
- Network connectivity problems can prevent API calls from succeeding.
Error messages:
"No API instance found. Please make sure to provide valid credentials."
This indicates that the node could not authenticate with Zalo. Verify that the API key credential is correctly configured and valid.- Errors related to invalid User ID or parameters will be thrown by the API and surfaced by the node. Ensure the User ID exists and is correctly formatted.
To handle errors gracefully, enable the "Continue On Fail" option in the node settings to allow processing of subsequent items even if one fails.