Actions25
- 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 user's Zalo profile when they provide their phone number in a form.
- Enriching customer records with Zalo user data for marketing or support purposes.
- Validating if a phone number corresponds to an existing Zalo user before sending friend requests or messages.
Properties
| Name | Meaning |
|---|---|
| Phone Number | The phone number of the Zalo user to find. This is a required string input property. |
Output
The node outputs JSON data representing the found user's information from Zalo. The structure typically includes user profile details such as user ID, display name, avatar URL, and other relevant metadata returned by the Zalo API.
If the node supports binary data output (not explicitly shown here), it would represent media or attachments related to the user, but this node primarily focuses on JSON user data.
Dependencies
- Requires access to the Zalo API, which means the node depends on valid API credentials (an API key or authentication token) configured within n8n.
- The node uses external libraries for HTTP requests and possibly file system operations (e.g.,
fsmodule) for handling attachments or caching. - Proper network connectivity to Zalo's servers is necessary.
Troubleshooting
Common Issues:
- Invalid or missing phone number input will cause the node to fail.
- Incorrect or expired API credentials will result in authentication errors.
- Network issues or Zalo API downtime can cause request failures.
- Rate limiting by Zalo API may lead to temporary blocking.
Error Messages:
- Errors indicating invalid phone number format: Ensure the phone number is correctly formatted and includes country code if required.
- Authentication errors: Verify that the API credentials are correctly set up in n8n.
- Timeout or connection errors: Check internet connectivity and Zalo API status.
- Unexpected response or parsing errors: May indicate changes in Zalo API; check for updates or contact support.
Links and References
Note: The source code provided was heavily obfuscated, so the summary is based on static analysis of the exposed properties and typical usage patterns for a "Find User" operation by phone number in a Zalo integration node.