Actions10
Overview
The Zalo User node allows interaction with Zalo user accounts through various operations such as managing friend requests, blocking/unblocking users, updating profile settings, retrieving user information, and searching for users by phone number. Specifically, the "Tìm kiếm người dùng" (Find User) operation enables searching for a Zalo user by their phone number.
This node is beneficial in scenarios where you need to automate user management tasks on Zalo, such as integrating Zalo user data into your CRM, automating friend request handling, or verifying user identities by phone number.
Practical example:
You can use this node to find a Zalo user by their phone number to retrieve their profile details before sending a friend request or to verify if a user exists on Zalo based on contact information collected from another system.
Properties
| Name | Meaning |
|---|---|
| Phone Number | The phone number of the Zalo user you want to search for. |
| Limit | The maximum number of results to return when listing multiple users (used in other ops). |
Note: For the "findUser" operation, only Phone Number is required and used.
Output
- The output JSON contains the result of the user search by phone number.
- The structure depends on the response from the Zalo API's
findUsermethod, typically including user details matching the phone number. - Each output item corresponds to an input item, paired by index.
- No binary data output is produced by this operation.
Example output snippet (conceptual):
{
"userId": "123456789",
"name": "Nguyen Van A",
"phoneNumber": "0123456789",
"avatarUrl": "https://...",
...
}
Dependencies
- Requires valid Zalo API credentials, including authentication cookies, device IMEI, and user agent strings.
- These credentials must be configured in n8n beforehand.
- Uses the external
zca-jslibrary to interact with the Zalo API. - The node expects the credentials to provide necessary session info (
cookie,imei,userAgent) to authenticate API calls.
Troubleshooting
No API instance found error:
This occurs if the node cannot establish a connection to the Zalo API using provided credentials.
Resolution: Verify that the API credentials are correctly set up and contain valid cookie, IMEI, and user agent values.Operation-specific errors:
Errors thrown during API calls (e.g., invalid phone number format, user not found) will appear as error messages. If "Continue On Fail" is enabled, the node will output the error per item instead of stopping execution.Empty or unexpected results:
Ensure the phone number is correctly formatted and the user exists on Zalo. Also, check API rate limits or restrictions imposed by Zalo.
Links and References
- Zalo Official Developer Documentation (general reference for Zalo APIs)
- n8n Documentation (for configuring credentials and using custom nodes)