Actions12
Overview
This node interacts with Zalo User services, allowing users to manage and query Zalo user information programmatically. Specifically, the "Tìm Kiếm Người Dùng" (Find User) operation enables searching for a Zalo user by their phone number. This is useful in scenarios where you want to verify if a phone number corresponds to a Zalo user or retrieve basic user details based on the phone number.
Practical examples include:
- Verifying customer phone numbers against Zalo user accounts before sending marketing messages.
- Integrating Zalo user lookup into CRM systems to enrich contact data.
- Automating friend requests or messaging workflows after identifying users by phone number.
Properties
| Name | Meaning |
|---|---|
| Phone Number | The phone number to search for the corresponding Zalo user. |
| Limit | The maximum number of results to return from the search. |
Output
The output JSON contains the result of the user search by phone number. It typically includes user details returned by the Zalo API for the matched phone number(s). The exact structure depends on the API response but generally includes user identifiers and profile information.
Example output structure (simplified):
{
"id": "user_id",
"name": "User Name",
"phoneNumber": "searched_phone_number",
"additionalInfo": { /* other user details */ }
}
If multiple users are found (depending on the API), the output may be an array or contain a list under a specific key.
No binary data output is produced by this operation.
Dependencies
- Requires valid Zalo API credentials including authentication tokens such as cookies, device IMEI, and user agent strings.
- The node uses an external Zalo SDK/library to perform API calls.
- Proper configuration of the Zalo API credential in n8n is necessary to authenticate requests.
Troubleshooting
- Invalid Credentials: If the node throws an error about missing or invalid API instance, ensure that the Zalo API credentials are correctly configured and valid.
- No Results Found: Searching by phone number might return empty results if the number is not registered on Zalo or privacy settings restrict access.
- API Rate Limits: Frequent searches might hit API rate limits; consider adding delays or handling errors gracefully.
- Network Issues: Connectivity problems can cause request failures; verify network access to Zalo API endpoints.
- Error Messages: Errors thrown by the node will include messages from the underlying API call. Use these messages to diagnose issues like invalid parameters or permission problems.
To resolve common errors:
- Double-check the phone number format.
- Verify that the API credentials have sufficient permissions.
- Enable "Continue On Fail" in the node settings to handle partial failures without stopping the workflow.