Actions12
Overview
This node interacts with the Zalo platform to manage and retrieve information about Zalo users. Specifically, the "Lấy Thông Tin Người Dùng" (Get User Information) operation fetches detailed information about a specified Zalo user by their user ID.
Common scenarios where this node is beneficial include:
- Integrating Zalo user data into CRM or marketing automation workflows.
- Fetching user profile details for customer support or personalization.
- Automating user data retrieval in multi-channel communication setups.
For example, you can input a Zalo user ID to get their profile information such as name, avatar, status, and other public details, which can then be used downstream in your workflow.
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 full user information object returned by the Zalo API for the specified user ID. This typically includes fields such as the user's name, avatar URL, gender, birthday, and other profile details available via the API.
Example output structure (simplified):
{
"id": "123456789",
"name": "Nguyen Van A",
"avatar": "https://example.com/avatar.jpg",
"gender": "male",
"birthday": "1990-01-01",
"status": "active",
...
}
No binary data is produced by this operation.
Dependencies
- Requires valid Zalo API credentials including an API key credential that provides 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.
Troubleshooting
- Invalid Credentials: If the node throws an error indicating no API instance found, verify that the Zalo API credentials are correctly configured and valid.
- User Not Found: If the specified User ID does not exist or is invalid, the API may return an error or empty response. Double-check the User ID input.
- Network Issues: Connectivity problems with the Zalo API endpoint can cause failures. Ensure network access and API availability.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error messages in the output JSON under the
errorfield.