Actions9
Overview
This node manages Zalo groups by interacting with the Zalo API. It supports various group-related operations such as creating groups, retrieving group information, managing members and deputies, changing group details, and more. The "Thêm Phó Nhóm" (Add Group Deputy) operation specifically allows adding a user as a deputy (co-admin) to an existing Zalo group.
Practical scenarios include:
- Automating group management tasks in Zalo for community managers or businesses.
- Adding trusted users as deputies to help moderate or manage group activities.
- Integrating Zalo group management into broader workflows, e.g., syncing group roles with other systems.
Properties
| Name | Meaning |
|---|---|
| ID Nhóm | The unique identifier of the Zalo group where the deputy will be added. |
| ID Người Dùng | The unique identifier of the user who will be added as a deputy to the group. |
Output
The output JSON contains:
status: A string indicating the result of the operation, typically"Thành công"meaning "Success".response: The raw response from the Zalo API related to adding the deputy user.
Example output structure:
{
"status": "Thành công",
"response": { /* API response object */ }
}
No binary data is output by this operation.
Dependencies
- Requires valid Zalo API credentials including cookie, IMEI, and user agent information.
- The node uses an external Zalo API client library (
zca-js) to perform API calls. - Credentials must be configured in n8n with appropriate access rights to manage Zalo groups.
Troubleshooting
Common issues:
- Invalid or expired credentials may cause authentication failures.
- Incorrect group ID or user ID can lead to errors or no effect.
- Network or API rate limits might cause request failures.
Error messages:
"No API instance found. Please make sure to provide valid credentials."
Means the node could not authenticate with Zalo API. Check your credentials and ensure they are correctly set.- Errors returned from the API (e.g., user not found, insufficient permissions) will be included in the error message. Review the IDs and permissions.
To handle errors gracefully, enable "Continue On Fail" in the node settings to process subsequent items even if one fails.