Actions12
Overview
This node interacts with the Zalo User API to change account settings for a Zalo user. It allows updating personal information such as display name, date of birth, gender, and language preferences. This is useful in scenarios where you want to automate profile updates or synchronize user data from other systems into Zalo accounts.
Practical examples include:
- Automatically updating user profiles after registration on your platform.
- Synchronizing user demographic changes from a CRM system to Zalo.
- Localizing user language settings based on their preferences or location.
Properties
| Name | Meaning |
|---|---|
| Name | The display name of the Zalo user. |
| Date of Birth | The user's date of birth in the format YYYY-MM-DD. |
| Gender | The user's gender. Options: Male (1), Female (2), Other (3). |
| Language | Optional. The preferred language code for the user, e.g., "vi" for Vietnamese, "en" for English. |
Output
The node outputs JSON data containing the status of the operation and the response from the Zalo API. The structure typically looks like:
{
"status": "Thành công",
"response": { /* detailed response object from Zalo API */ }
}
status: A string indicating success or failure of the update operation.response: Contains detailed information returned by the Zalo API about the updated account settings.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the Zalo API.
- The node depends on a Zalo API client library internally to perform requests.
- Proper configuration of credentials in n8n is necessary to authorize API calls.
Troubleshooting
Common issues:
- Invalid or expired API credentials will cause authentication failures.
- Incorrect date format for the Date of Birth property may result in validation errors.
- Missing required fields (Name, Date of Birth, Gender) will prevent the operation from executing.
Error messages:
- Errors thrown by the node typically contain messages from the Zalo API, such as invalid parameters or unauthorized access.
- To resolve, verify that all required properties are correctly set and that the API credentials are valid and have sufficient permissions.