Actions9
Overview
This node interacts with the Zalo platform to retrieve user information. Specifically, for the "Zalo User" resource and the "Lấy thông tin người dùng" (Get user information) operation, it fetches detailed data 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.
- Enriching contact records with up-to-date user details from Zalo.
- Automating customer support processes by fetching user profiles dynamically.
For example, you might use this node to get profile information of a user who just interacted with your chatbot on Zalo, then personalize follow-up messages based on that data.
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 node outputs JSON data containing:
status: A string indicating the success status of the API call (e.g.,"success").response: An object containing the detailed user information returned from the Zalo API.
The output is paired with the input item index to maintain correspondence in batch operations.
No binary data output is produced by this node.
Example output structure:
{
"status": "success",
"response": {
"id": "123456789",
"name": "Nguyen Van A",
"gender": "male",
"birthday": "1990-01-01",
"phone": "0123456789",
...
}
}
Dependencies
- Requires valid credentials for the Zalo API, typically an API key or token configured in n8n credentials.
- Uses an external Zalo API client library (
zca-js) to communicate with the Zalo platform. - The node expects proper authentication and network access to the Zalo API endpoints.
Troubleshooting
- No API instance found error: Indicates missing or invalid credentials. Ensure that the Zalo API credentials are correctly set up in n8n.
- Invalid User ID: If the provided User ID does not exist or is malformed, the API may return an error or empty response. Verify the User ID before running.
- Network issues: Connectivity problems can cause timeouts or failures. Check your network and firewall settings.
- Continue On Fail: If enabled, the node will continue processing other items even if one fails, returning error details in the output JSON.
Links and References
- Zalo Official Developer Documentation
- Zalo API Client Library (zca-js) (used internally by the node)