Actions10
- User Action Actions
- Message Action Actions
Overview
The node "Zalo Web" integrates with the Zalo messaging platform, enabling various user-related and messaging operations. Specifically, the Search User operation under the User Action resource allows users to find a Zalo user by their phone number. This is useful for scenarios where you want to retrieve detailed information about a user based on their unique phone number identifier.
Practical examples include:
- Looking up a user's profile details before sending a message.
- Verifying if a phone number corresponds to an active Zalo user.
- Automating workflows that require fetching user info dynamically from phone numbers.
Properties
Name | Meaning |
---|---|
Phone Number | The unique phone number of the target user to search for. This is required to identify the user. |
Output
The output JSON contains a data
field holding the detailed user information retrieved from Zalo. This includes user identifiers and profile details as returned by the Zalo API.
Example structure (simplified):
{
"data": {
"uid": "user_unique_id",
"name": "User's full name",
"avatar": "URL to user's avatar",
"phoneNumber": "User's phone number",
...
}
}
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Zalo Web API.
- The node depends on internal session management (
accountID
) which caches login sessions. - Uses external libraries for HTTP requests and file handling internally.
- Requires proper configuration of the Zalo Web API credentials within n8n.
Troubleshooting
Common issues:
- Invalid or expired API credentials will cause authentication failures.
- Providing an incorrect or malformed phone number may result in no user found or errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
"Thao tác không được hỗ trợ"
(Operation not supported) indicates an unsupported action or failure in downloading resources.- Errors related to fetching user info usually mean the phone number does not correspond to any user or the session is invalid.
Resolutions:
- Verify and refresh API credentials.
- Ensure the phone number format matches expected input.
- Check network access and retry the operation.