Actions10
Overview
This node manages Zalo user account operations, specifically for the "Zalo User" resource. The "Thay đổi cài đặt tài khoản" (Change Account Setting) operation allows updating a user's profile information such as display name, date of birth, and gender.
Common scenarios include:
- Automating updates to user profiles in bulk.
- Synchronizing user data from other systems into Zalo accounts.
- Managing user settings programmatically without manual intervention.
For example, you can use this node to update the display name and birthday of multiple users based on data from a CRM system.
Properties
| Name | Meaning |
|---|---|
| Name | Display name of the Zalo user to set. |
| Date of Birth | User's date of birth in the format YYYY-MM-DD. |
| Gender | User's gender. Options: Male (1), Female (2), Other (3). |
| Language | (Optional) Language preference code, e.g., "vi" for Vietnamese or "en" for English. |
Output
The output JSON contains:
status: A string indicating success, typically"Thành công"(Success).response: The raw response object returned by the Zalo API after updating the profile.
Example output JSON structure:
{
"status": "Thành công",
"response": {
// API response details about the updated profile
}
}
No binary data is produced by this operation.
Dependencies
- Requires an API key credential to authenticate with the Zalo API.
- Uses stored cookie, IMEI, and user agent values from credentials or input data for authentication.
- Depends on the external
zca-jslibrary to interact with the Zalo API.
Troubleshooting
- Invalid Credentials: If the node throws "No API instance found," verify that the provided API key credential is valid and includes necessary cookie, IMEI, and user agent information.
- Incorrect Date Format: Ensure the "Date of Birth" property follows the
YYYY-MM-DDformat to avoid API errors. - Missing Required Fields: The "Name," "Date of Birth," and "Gender" fields are required; missing any will cause the operation to fail.
- API Rate Limits or Network Issues: Temporary failures may occur due to network problems or API rate limits; consider enabling "Continue On Fail" to handle partial batch processing.
Links and References
- Zalo Official Developer Documentation
- zca-js GitHub Repository (for the underlying Zalo API client used)