Actions9
Overview
This node manages Zalo user accounts by interacting with the Zalo platform through an API. It supports various user-related operations such as accepting or sending friend requests, blocking/unblocking users, changing account settings including the avatar, retrieving user information, and searching for users.
The "Đổi ảnh đại diện" (Change Account Avatar) operation specifically allows you to update a Zalo user's profile picture by providing the user ID and the file path of the new avatar image.
Practical examples:
- Automatically update profile pictures for multiple Zalo users in bulk.
- Integrate with other systems to synchronize user avatars from external sources.
- Manage user profiles programmatically without manual intervention.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the Zalo user whose avatar will be changed. |
| File Path | The local file system path to the image file that will be set as the new avatar picture. |
Output
The output JSON contains two main fields:
status: A string indicating the success status, typically"Thành công"(meaning "Success").response: The raw response object returned from the API call to change the avatar, which may include details about the updated user or confirmation data.
Example output structure:
{
"status": "Thành công",
"response": {
// API response details here
}
}
No binary data is output by this node.
Dependencies
- Requires a valid API authentication credential to connect to the Zalo platform.
- The node uses an underlying Zalo API client library to perform actions.
- The credential must provide necessary authentication tokens such as cookies, device identifiers, and user agent strings.
- The file path provided must point to a valid image file accessible by the n8n instance.
Troubleshooting
Common issues:
- Invalid or expired credentials can cause authentication failures.
- Incorrect or inaccessible file paths will prevent the avatar from being updated.
- Network connectivity problems may interrupt API calls.
Error messages:
"No API instance found. Please make sure to provide valid credentials."
This indicates missing or invalid API credentials. Verify and reconfigure the API authentication.- Errors related to file access or upload failure usually indicate the file path is incorrect or the file is not accessible by n8n.
Resolution tips:
- Ensure the API credential is correctly configured and active.
- Confirm the file path is correct and the file permissions allow reading.
- Check network connectivity and API endpoint availability.