Actions9
Overview
This node allows users to change the account settings of a Zalo user. It is useful for updating personal information such as display name, date of birth, gender, and language preferences on a Zalo account programmatically within an n8n workflow.
Practical examples include:
- Automatically updating user profile details based on data from another system.
- Synchronizing user information across multiple platforms.
- Customizing user profiles in bulk via automation.
Properties
| Name | Meaning |
|---|---|
| Name | Display name of the Zalo user. |
| 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 | Preferred language code, e.g., "vi" for Vietnamese or "en" for English. Optional field. |
Output
The node outputs JSON data containing:
status: A string indicating success ("success") or failure.response: The response object returned by the Zalo API after attempting to change the account settings.
The output is paired with the input item index to maintain traceability in workflows.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential to authenticate with the Zalo platform.
- Uses a Zalo API client internally that requires valid session cookies, device IMEI, and user agent strings, which are typically managed by the credential or node configuration.
- No additional external dependencies beyond the Zalo API and its authentication.
Troubleshooting
Common issues:
- Invalid or expired authentication credentials may cause failures.
- Incorrectly formatted date of birth (not matching YYYY-MM-DD) can lead to API errors.
- Missing required fields like Name, Date of Birth, or Gender will prevent execution.
Error messages:
- Errors thrown by the node usually contain the message from the Zalo API response.
- If the node cannot establish a connection due to missing or invalid cookies or tokens, it throws an error indicating failure to connect.
Resolutions:
- Ensure the API key credential is correctly configured and active.
- Validate all required input fields before running the node.
- Check the date format and gender value correctness.
- Enable error handling in the workflow to catch and manage API errors gracefully.