Actions22
- Get Actions
- Message Actions
- Friend Actions
- Group Actions
- Tool Actions
Overview
This node is designed to find a user on the Zalo platform using their phone number. It is useful in scenarios where you need to retrieve user information based on a known phone number, such as verifying user identity, fetching profile details, or integrating Zalo user data into workflows.
Practical examples include:
- Automatically looking up a Zalo user when a phone number is provided in a CRM system.
- Validating if a phone number corresponds to an existing Zalo user before sending friend requests or messages.
- Enriching contact data with Zalo user details for marketing or support automation.
Properties
| Name | Meaning |
|---|---|
| Phone Number | The phone number of the Zalo user to find. This is a required string input. |
Output
The node outputs JSON data containing the found user's information retrieved from Zalo. The exact structure depends on the Zalo API response but typically includes user identifiers, display names, and other profile details.
If the node supports binary data output (not explicitly shown here), it would represent media or attachments related to the user, but this is not indicated in the provided code.
Dependencies
- Requires an API key credential for authenticating with the Zalo platform.
- Uses external libraries for HTTP requests and file system operations.
- Depends on the Zalo API service being accessible and the provided phone number being valid.
Troubleshooting
Common issues:
- Invalid or missing phone number input will cause the node to fail.
- Network or authentication errors with the Zalo API can prevent successful user lookup.
- If the phone number does not correspond to any user, the node may return an empty result or error.
Error messages:
- Errors indicating invalid credentials suggest checking the configured API key.
- Timeout or connection errors imply network issues or Zalo API downtime.
- Validation errors about the phone number format require ensuring the input matches expected patterns.
To resolve these, verify the phone number input, ensure correct API credentials are set up in n8n, and check network connectivity.