Actions10
Overview
This node interacts with the Zalo platform to manage and retrieve information about Zalo users. Specifically, for the "Zalo User" resource and the "Lấy thông tin người dùng" (Get user information) operation, it fetches detailed information about a specified Zalo user by their user ID.
Common scenarios where this node is beneficial include:
- Retrieving profile details of a Zalo user for CRM or customer support purposes.
- Integrating Zalo user data into other systems or workflows.
- Automating user data retrieval in marketing or communication pipelines.
Practical example:
- Given a user ID, the node returns the full profile information of that user from Zalo, which can then be used to personalize messages or update records in a database.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the Zalo user whose information you want to retrieve. This is a required string input. |
Output
The output JSON contains the detailed information of the requested Zalo user as returned by the Zalo API. The structure depends on the API response but typically includes user profile fields such as name, avatar, status, and other personal details.
Example output structure (simplified):
{
"id": "123456789",
"name": "Nguyen Van A",
"avatar": "https://...",
"status": "Online",
"phoneNumber": "0123456789",
...
}
No binary data output is produced by this operation.
Dependencies
- Requires valid Zalo API credentials including an API key credential with cookie, IMEI, and user agent information.
- The node uses an external Zalo SDK library (
zca-js) to interact with the Zalo API. - Proper configuration of the Zalo API credentials in n8n is necessary for authentication and successful API calls.
Troubleshooting
Common issues:
- Invalid or expired credentials may cause authentication failures.
- Missing or incorrect User ID input will result in errors or empty responses.
- Network connectivity problems can prevent API calls from succeeding.
Error messages:
"No API instance found. Please make sure to provide valid credentials."
This indicates that the node could not authenticate with Zalo due to missing or invalid credentials. Verify your API key and credential setup.- Errors related to user not found or invalid user ID will come directly from the Zalo API. Ensure the User ID is correct.
- If the node is set to continue on fail, errors for individual items will be included in the output JSON under an
errorfield.
Links and References
- Zalo Official Developer Documentation
- Zalo API SDK (zca-js) GitHub Repository (for reference on SDK usage)