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 profile data of 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.
- Enriching customer profiles with up-to-date Zalo user information.
- Automating support processes that require fetching user details from Zalo.
Practical example:
- Given a user ID, the node retrieves the user's profile information such as name, avatar, status, or other public details available via the Zalo API, enabling downstream nodes to use this data for personalized messaging or record updates.
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 various profile fields such as name, avatar URL, gender, birthday, and other metadata related to the user.
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 output is produced by this operation.
Dependencies
- Requires valid Zalo API credentials including an API key credential with cookie, device IMEI, and user agent information.
- The node uses an external Zalo SDK library (
zca-js) to interact with the Zalo API. - Proper configuration of these credentials in n8n is necessary for 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 communication.
Error messages:
"No API instance found. Please make sure to provide valid credentials."
Means the node could not authenticate with Zalo API. Check your credentials and ensure they are correctly set.- Errors thrown during execution will include the specific message from the Zalo API or SDK. If
continueOnFailis enabled, errors for individual items will be returned in the output JSON under anerrorfield.
Resolution tips:
- Verify that the API key credential is current and has all required fields (cookie, IMEI, user agent).
- Confirm the user ID exists and is correct.
- Enable
continueOnFailif you want the workflow to proceed despite some failed items.
Links and References
- Zalo Official Developer Documentation
- Zalo SDK (zca-js) GitHub Repository (for reference on API methods)
- n8n Documentation on Credentials and Creating Custom Nodes