Actions10
Overview
This node manages Zalo user account operations, specifically for the "Zalo User" resource. The selected operation "Thay đổi cài đặt tài khoản" (Change Account Setting) allows updating a user's profile information such as display name, date of birth, and gender.
Typical use cases include:
- Automating updates to user profiles in bulk.
- Synchronizing user data from other systems into Zalo.
- Managing user information programmatically without manual intervention.
For example, you can update multiple users' display names and birthdays by feeding their data into this node, which then calls the Zalo API to apply these changes.
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 node outputs JSON objects for each input item processed. For the "changeAccountSetting" operation, the output JSON contains:
status: A string indicating success, typically "Thành công" (Success).response: The raw response object returned from 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 node.
Dependencies
- Requires an API key credential to authenticate with the Zalo platform.
- Uses the
zca-jslibrary internally to interact with the Zalo API. - The node expects valid authentication cookies, device IMEI, and user agent strings either from credentials or input data.
- Proper configuration of the Zalo API credential in n8n is necessary before using this node.
Troubleshooting
- Invalid Credentials: If the node throws "No API instance found," it indicates invalid or missing credentials. Ensure the API key and related authentication details are correctly configured.
- Incorrect Date Format: The "Date of Birth" must be in
YYYY-MM-DDformat. Invalid formats may cause API errors. - Missing Required Fields: The "Name," "Date of Birth," and "Gender" fields are required. Omitting them will result in errors.
- API Rate Limits or Network Issues: Failures during API calls might occur due to rate limits or connectivity problems. Retrying or checking network status may help.
- Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error messages per item.