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 contacts.
Practical scenarios include:
- Personalizing contact names in your Zalo friend list for easier recognition.
- Automating updates of contact aliases based on external data sources.
- Managing large contact lists by programmatically setting meaningful aliases.
Example: You have a contact with user ID 12345 and want to change their alias to "Work Buddy". This node can perform that update 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 name (custom display name) 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 include details about the updated alias or confirmation data.
Example output JSON:
{
"status": "Thành công",
"response": {
// API response details here
}
}
No binary data is produced by this operation.
Dependencies
- Requires valid Zalo API credentials including an API key credential with cookie, device IMEI, and user agent information.
- Uses the
zca-jslibrary to interact with the Zalo API. - The node expects these credentials to be configured properly in n8n before execution.
Troubleshooting
Common issues:
- Invalid or expired credentials leading to login failure.
- Incorrect user ID causing the alias change to fail.
- Network or API errors from Zalo service interruptions.
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 correct and active.- Errors thrown during execution will include the message from the underlying API call. If
continueOnFailis enabled, errors will be returned as part of the output JSON under anerrorfield.
Resolution tips:
- Verify the API credentials and refresh them if necessary.
- Confirm the user ID exists and is accessible.
- Enable
continueOnFailto handle partial failures gracefully.
Links and References
- Zalo Official Developer Documentation
- n8n Documentation on Credentials
- zca-js GitHub Repository (for the underlying Zalo API client library)