Actions12
Zalo User → Lấy Thông Tin Người Dùng
AI-generatedOverview
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 profile data of a specified Zalo user by their user ID. This is useful in scenarios where you need to integrate Zalo user data into workflows, such as customer support automation, user verification, or personalized marketing campaigns.
For example, you can use this node to:
- Retrieve profile details of a user who just sent a message.
- Enrich your CRM system with up-to-date Zalo user information.
- Automate responses based on user attributes fetched from Zalo.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the Zalo user whose information you want to retrieve. |
Output
The output JSON contains the full user information object returned by the Zalo API for the specified user ID. This typically includes profile details such as name, avatar, gender, birthday, and other public user data available via the API.
Example output structure (simplified):
{
"id": "123456789",
"name": "Nguyen Van A",
"avatar": "https://...",
"gender": "male",
"birthday": "1990-01-01",
...
}
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 set up and contain valid cookie, IMEI, and user agent values.
- User Not Found: If the user ID does not exist or is invalid, the API may return an error or empty response. Double-check the user ID input.
- API Rate Limits: Frequent calls to the Zalo API might hit rate limits; consider adding delays or handling errors gracefully.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error messages in the output JSON.