Actions12
Overview
This node interacts with the Zalo platform to manage user-related operations. Specifically, the "Đổi Tên Gợi Nhớ" (Change Alias Name) operation allows you to update the alias name (a nickname or a memorable name) of a Zalo user identified by their User ID. This is useful for personalizing contact lists or managing friend names programmatically.
Practical scenarios include:
- Automatically updating contact nicknames in bulk based on external data.
- Synchronizing user aliases from a CRM system into Zalo contacts.
- Customizing friend display names for better organization within Zalo.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the Zalo user whose alias name you want to change. |
| Alias Name | The new alias name (nickname) to assign to the specified user. |
Output
The node outputs a JSON object containing:
status: A string indicating the success status, typically"Thành công"(meaning "Success").response: The raw response from the Zalo API after attempting to change the alias name. This may contain additional details about the operation result.
Example output JSON structure:
{
"status": "Thành công",
"response": { /* API response details */ }
}
The node does not output binary data.
Dependencies
- Requires an active connection to the Zalo API via an API key credential configured in n8n.
- The node uses stored authentication information including cookies, device IMEI, and user agent strings to authenticate requests.
- No other external dependencies are required beyond the configured Zalo API credentials.
Troubleshooting
Common issues:
- Invalid or expired API credentials can cause authentication failures.
- Incorrect User ID or Alias Name inputs may lead to API errors or no changes applied.
- Network connectivity problems can prevent communication with the Zalo API.
Error messages:
- If the node throws an error related to authentication, verify that the API key credential is valid and has not expired.
- Errors mentioning missing parameters indicate that required fields like User ID or Alias Name were not provided.
- Unexpected API responses might require checking the Zalo API status or reviewing rate limits.
Resolution tips:
- Double-check input values for correctness.
- Refresh or reconfigure the API credentials if authentication fails.
- Ensure stable internet connection during execution.
Links and References
- Zalo Official Developer Documentation
- Zalo API Authentication Guide
- n8n Documentation on Creating Custom Nodes