Actions10
Overview
This node manages Zalo user interactions, specifically allowing operations related to a Zalo user's contacts and profile. The "Đổi tên gợi nhớ" (Change Alias Name) operation lets you update the alias name (a nickname or memorable name) for a specific user in your Zalo contact list.
Common scenarios where this node is useful include:
- Personalizing contact names in your Zalo friend list for easier recognition.
- Automating updates of friend nicknames based on external data or CRM systems.
- Managing large contact lists by programmatically setting meaningful aliases.
For example, if you have a CRM with customer nicknames, you can use this node to sync those nicknames as alias names in Zalo automatically.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the Zalo user whose alias name you want to change. |
| Alias Name | The new alias (nickname) to assign to the specified user. |
Output
The output JSON contains:
status: A string indicating the result 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 details about the updated alias or confirmation data.
Example output JSON:
{
"status": "Thành công",
"response": {
// API response details here
}
}
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Zalo API via credentials that provide:
- A valid cookie for authentication.
- Device identifiers such as IMEI and user agent strings.
- The node uses an external Zalo API client library (
zca-js) to perform actions. - Proper configuration of the Zalo API credential in n8n is necessary before using this node.
Troubleshooting
- Invalid Credentials or Authentication Failure: If the node throws an error about missing or invalid API instance, verify that the Zalo API credentials are correctly set up with valid cookies and device info.
- User ID Not Found or Invalid: Ensure the provided User ID corresponds to a valid Zalo user in your contacts.
- Alias Name Validation: The alias name should comply with any length or character restrictions imposed by Zalo; otherwise, the API might reject the request.
- API Rate Limits or Network Issues: Temporary failures might occur due to network problems or API rate limiting; retrying later or checking network connectivity can help.
- Continue On Fail Option: If enabled, the node will continue processing other items even if one fails, returning error messages per item.
Links and References
- Zalo Official Developer Documentation
- Zalo API Client Library (zca-js) - GitHub (replace with actual link if available)