Actions9
Overview
This node interacts with Zalo User accounts, providing various user management operations. Specifically, the "Tìm kiếm người dùng" (Find User) operation allows searching for a Zalo user by their phone number. This is useful in scenarios where you want to retrieve user details based on a known phone number, such as verifying user identity, enriching contact information, or automating friend requests.
Practical examples:
- Automatically find and add users to your Zalo friend list by their phone numbers.
- Retrieve user profile information for customer support or CRM integration.
- Filter or segment users based on phone number lookups.
Properties
| Name | Meaning |
|---|---|
| Phone Number | The phone number of the Zalo user you want to search for. Must be provided as a string. |
| Limit | The maximum number of results to return from the search. Must be a number. |
Output
The output JSON contains the data returned by the Zalo API's user search method. It typically includes user details matching the searched phone number. The exact structure depends on the API response but generally includes user identifiers and profile information.
Example output snippet (conceptual):
{
"userId": "123456789",
"name": "Nguyen Van A",
"phoneNumber": "0123456789",
"avatarUrl": "https://...",
...
}
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential to authenticate with the Zalo platform.
- Uses stored cookie, device IMEI, and user agent information from credentials or input data to establish a session.
- Depends on the external
zca-jslibrary to interact with the Zalo API.
Troubleshooting
- No API instance found: Indicates invalid or missing credentials. Ensure that the API key credential is correctly configured and contains valid cookie, IMEI, and user agent data.
- Empty or no results: If the phone number does not correspond to any user, the output will be empty. Verify the phone number format and existence.
- Rate limits or API errors: The Zalo API may impose rate limits or restrictions. Handle errors gracefully and consider retry logic or backoff strategies.
- Continue on Fail: If enabled, the node will continue processing other items even if one fails, returning error messages in the output JSON.