Actions12
Overview
This node manages Zalo user interactions, specifically for the "Zalo User" resource. The operation "Đổi Tên Gợi Nhớ" (Change Alias Name) allows you to update the alias name (a nickname or a custom display name) of a specific Zalo user in your contacts. This is useful when you want to personalize how contacts appear in your Zalo app or system by assigning memorable or meaningful names.
Practical examples:
- Automatically updating contact nicknames based on CRM data.
- Personalizing friend lists with custom aliases for easier identification.
- Synchronizing alias names from external databases or marketing tools.
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 output JSON contains:
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 include details about the updated alias or confirmation data.
Example output structure:
{
"status": "Thành công",
"response": {
// API response details here
}
}
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential to authenticate with the Zalo platform.
- The node uses stored credentials including cookie, IMEI, and user agent strings to establish a session with Zalo's API.
- The underlying implementation depends on the
zca-jslibrary to interact with Zalo services.
Troubleshooting
Common issues:
- Invalid or expired credentials can cause authentication failures.
- Incorrect User ID or alias name format might result in API errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
"No API instance found. Please make sure to provide valid credentials."
Means the node could not authenticate with Zalo. Verify that the API key credential is correctly configured and valid.- Errors returned from the Zalo API will be passed through; check the error message for details such as invalid user ID or permission issues.
Resolution tips:
- Ensure the API credential is up to date and has necessary permissions.
- Double-check the User ID exists and is correct.
- Validate the alias name does not contain unsupported characters or exceed length limits.
- Enable "Continue On Fail" if you want the workflow to proceed despite individual item errors.