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:
- Automating friend requests by first finding users via their phone numbers.
- Syncing contact lists with Zalo user profiles.
- Validating if a phone number corresponds to an existing Zalo user before sending messages or invitations.
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 representing the found user's information from Zalo. The exact structure depends on the API response but typically includes user identifiers, profile details, and status information.
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 an active connection to the Zalo API.
- Needs an API key credential configured in n8n for authentication with Zalo services.
- The node internally uses helper classes and methods to interact with the Zalo API, handle responses, and manage errors.
Troubleshooting
Common Issues:
- Invalid or missing phone number input will cause the node to fail.
- Authentication failures due to incorrect or expired API credentials.
- Network issues preventing communication with the Zalo API.
- Unexpected API response formats or rate limiting by Zalo.
Error Messages:
- Errors indicating failure to authenticate usually mean the API key needs to be checked or refreshed.
- Validation errors about the phone number suggest ensuring the input is correctly formatted and provided.
- Timeout or network errors require checking internet connectivity and API endpoint availability.
Resolution Tips:
- Verify that the phone number is entered correctly and matches the expected format.
- Confirm that the API key credential is valid and has necessary permissions.
- Check n8n's credential configuration and update if needed.
- Review Zalo API documentation for any changes or limitations.