Actions9
Overview
This node allows users to interact with Zalo User accounts, specifically enabling the operation to change a user's profile avatar image. It is useful in scenarios where automated updates of user avatars are needed, such as managing multiple user profiles or integrating avatar changes into workflows that respond to external triggers.
For example, a marketing automation workflow could update the profile pictures of user accounts based on campaign events or user status changes.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the Zalo user whose avatar will be changed. |
| File Path | The file system path to the new avatar image to upload for the user. |
Output
The node outputs JSON data containing:
status: A string indicating the success status of the avatar change operation (e.g., "success").response: The response object returned from the API call that performs the avatar update, which may include details about the updated user or confirmation of the change.
No binary data output is indicated by the code.
Dependencies
- Requires valid Zalo API credentials configured in n8n to authenticate API requests.
- Uses an external Zalo API client library (
zca-js) to perform operations. - The node expects access to the local file system path specified in the
File Pathproperty to read the avatar image.
Troubleshooting
- Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect or inaccessible file paths for the avatar image will result in file read errors.
- Providing an invalid User ID may cause the API to reject the request or return an error.
- Error messages:
"No API instance found. Please make sure to provide valid credentials."indicates missing or invalid API authentication setup.- Errors related to file handling or API responses will be thrown and can be caught if "Continue On Fail" is enabled, allowing the workflow to proceed despite individual item failures.