Actions22
- Get Actions
- Message Actions
- Friend Actions
- Group Actions
- Tool Actions
Overview
This node operation "Get User Info" for the "Get" resource is designed to retrieve detailed information about a specific user from the Zalo platform by their User ID. It is useful in scenarios where you need to fetch profile details, status, or other metadata of a Zalo user within an n8n workflow.
Practical examples include:
- Enriching contact data by fetching additional user info before sending messages.
- Validating user existence or status before performing friend requests or group operations.
- Integrating Zalo user data into CRM or customer support systems.
Properties
| Name | Meaning |
|---|---|
| User Id | The unique identifier of the Zalo user whose information you want to retrieve. |
Output
The node outputs JSON data containing the user's information as returned by the Zalo API. This typically includes fields such as user name, avatar URL, gender, birthday, and other profile details. The exact structure depends on the Zalo API response for user info.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Zalo API with appropriate authentication (e.g., an API key or token).
- The node internally uses HTTP requests to communicate with the Zalo service.
- No additional external dependencies beyond standard n8n credentials and HTTP request capabilities are required.
Troubleshooting
- Invalid User Id: If the provided User Id does not exist or is malformed, the node may throw an error indicating that the user could not be found. Verify the User Id value.
- Authentication Errors: Ensure that the API credentials used have sufficient permissions and are valid.
- API Rate Limits: Excessive requests might lead to rate limiting by Zalo. Implement retry logic or reduce request frequency.
- Network Issues: Connectivity problems can cause failures; check network access and proxy settings if applicable.
- Error Messages: The node logs errors with details; review these logs to identify issues related to API responses or internal processing.
Links and References
Note: The analysis is based solely on static code inspection and provided property definitions without runtime execution or dynamic import resolution. Internal credential names and sensitive identifiers have been generalized.