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 memorable or custom display name) for a specific user in your Zalo contact list.
Common scenarios where this node is useful include:
- Personalizing contact names in your Zalo account programmatically.
- Automating updates of friend aliases based on external data or CRM systems.
- Managing large contact lists by setting meaningful aliases for easier identification.
For example, you could use this node to rename a contact from their default phone number or ID to a more recognizable name like "John from Sales Team".
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 (custom display name) that you want 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 object returned from the underlying API call confirming the alias name change.
Example output JSON:
{
"status": "Thành công",
"response": {
// API response details about the alias name change
}
}
No binary data is produced by this operation.
Dependencies
- Requires an active connection to the Zalo API via an API key credential with valid authentication cookies, device IMEI, and user agent information.
- The node uses an external library (
zca-js) to interact with the Zalo API. - Proper configuration of the Zalo API credentials within n8n is necessary before using this node.
Troubleshooting
- Invalid Credentials: If the node throws an error about missing or invalid API instance, verify that the Zalo API credentials are correctly set up and contain valid cookie, IMEI, and user agent values.
- User Not Found: Errors may occur if the provided User ID does not exist or is incorrect. Double-check the User ID input.
- Permission Issues: The API might reject alias changes if the authenticated user lacks permission to modify the target user's alias.
- Network or API Errors: Temporary network issues or API downtime can cause failures. Retrying after some time or checking network connectivity may help.
- Continue On Fail: If enabled, the node will continue processing other items even if one fails, returning error messages in the output JSON.
Links and References
- Zalo Official Developer Documentation
- n8n Documentation - Creating Custom Nodes
- Zalo API Wrapper Library (zca-js) (used internally by the node)