Actions10
Overview
This node manages Zalo groups by interacting with the Zalo API. Specifically, the "Đổi Avatar Nhóm" (Change Group Avatar) operation updates the avatar image of a specified Zalo group using a provided image URL.
Common scenarios for this node include:
- Automatically updating group avatars based on events or schedules.
- Managing multiple Zalo groups' appearances programmatically.
- Integrating with other systems to reflect branding changes in group avatars.
Example use case: A marketing team uses this node to update the avatar of their Zalo group daily with a new promotional banner image hosted online.
Properties
| Name | Meaning |
|---|---|
| ID Nhóm | The unique identifier of the Zalo group whose avatar will be changed. |
| URL Ảnh | The URL of the new avatar image to set for the group. |
Output
The output JSON contains:
status: A string indicating success, typically"Thành công"(meaning "Success").response: The raw response from the Zalo API after attempting to change the group's avatar. This may include details about the updated group or confirmation data.
No binary data is output by this node.
Example output JSON:
{
"status": "Thành công",
"response": {
/* API response details */
}
}
Dependencies
- Requires valid Zalo API credentials including an API key credential that provides cookie, IMEI, and user agent information.
- The node depends on the external
zca-jslibrary to interact with the Zalo API. - Proper configuration of the Zalo API credential within n8n is necessary for authentication.
Troubleshooting
- Invalid Credentials: If the node throws an error about missing or invalid API instance, verify that the Zalo API credentials are correctly configured and contain valid cookie, IMEI, and user agent values.
- Network Issues: Failures to reach the Zalo API could cause errors; ensure network connectivity and that the API endpoint is accessible.
- Invalid Group ID or Image URL: Errors may occur if the group ID does not exist or the image URL is inaccessible or invalid. Double-check these inputs.
- API Rate Limits: Frequent calls might hit rate limits imposed by Zalo API, resulting in errors. Implement retries or delays as needed.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error messages in the output JSON.
Links and References
- Zalo Official API Documentation
- n8n Documentation - Creating Custom Nodes
- zca-js GitHub Repository (for the underlying Zalo API client library)