Actions9
Overview
This node manages Zalo groups, specifically allowing operations such as creating groups, retrieving group info, managing members and deputies, changing group avatars or names, and more. The "Đổi Avatar Nhóm" (Change Group Avatar) operation updates the avatar image of a specified Zalo group by providing a new image URL.
Practical scenarios include:
- Updating the visual identity of a group to reflect current branding or events.
- Automating group management tasks in workflows that integrate with Zalo.
- Keeping group information up-to-date without manual intervention.
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" (Success).response: The raw response from the API call that changes the group's avatar, which may include details about the update status.
Example output structure:
{
"status": "Thành công",
"response": { /* API response object */ }
}
No binary data is output by this operation.
Dependencies
- Requires an API key credential to authenticate with the Zalo platform.
- The node uses stored credentials including cookie, device IMEI, and user agent strings to establish a session.
- The external dependency is the Zalo API client library (
zca-js), which handles communication with Zalo services.
Troubleshooting
- Invalid Credentials: If the node throws "No API instance found," it indicates invalid or missing credentials. Ensure the API key and related authentication details are correctly configured.
- Invalid Group ID: Providing a wrong or non-existent group ID will cause the API call to fail. Verify the group ID before running the node.
- Invalid Image URL: The image URL must be accessible and valid; otherwise, the avatar change will not succeed.
- API Rate Limits or Permissions: The Zalo API might restrict certain actions based on permissions or rate limits. Check your API quota and permissions if requests fail.
- Continue On Fail: If enabled, the node will continue processing other items even if one fails, returning error messages in the output JSON.