Actions12
Zalo User → Đổi Tên Gợi Nhớ
AI-generatedOverview
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 friendly 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 (friendly name) 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.
- Needs valid session information including cookie, device IMEI, and user agent strings, which are either provided via credentials or input data.
- Uses the external
zca-jslibrary to interact with the Zalo API.
Troubleshooting
Common issues:
- Invalid or expired credentials leading to authentication failure.
- Incorrect or missing User ID causing the API call to fail.
- Network connectivity problems preventing communication with Zalo servers.
Error messages:
"No API instance found. Please make sure to provide valid credentials."
Resolution: Verify that the API key credential is correctly configured and active.- Errors related to invalid parameters (e.g., wrong User ID or alias name format).
Resolution: Double-check the input values for correctness and completeness. - API rate limits or temporary service unavailability.
Resolution: Retry after some time or check Zalo API status.
If the node is set to continue on failure, errors will be returned in the output JSON under the
errorfield for each failed item.