Actions10
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 creating notes within groups.
The specific operation "Thêm Phó Nhóm" (Add Group Deputy) allows you to add a user as a deputy (co-admin) of a specified Zalo group. This is useful for delegating group management responsibilities without transferring full ownership.
Practical example:
If you run a community or team chat on Zalo and want to assign trusted members as deputies to help moderate or manage the group, this operation lets you programmatically add those deputies by specifying the group ID and the user ID of the member to promote.
Properties
Name | Meaning |
---|---|
ID Nhóm | The unique identifier of the Zalo group where you want to add a deputy. |
ID Người Dùng | The unique identifier of the user who will be added as a deputy in the specified 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 after attempting to add the deputy. This may include additional details about the operation's outcome.
Example output structure:
{
"status": "Thành công",
"response": { /* API response object */ }
}
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Zalo API via credentials that provide:
- A valid API authentication token (cookie).
- Device identifiers such as IMEI and User-Agent strings.
- The node depends on the external
zca-js
library to interact with the Zalo API. - Properly configured Zalo API credentials must be set up in n8n before using this node.
Troubleshooting
Common issues:
- Invalid or expired credentials can cause authentication failures.
- Incorrect group ID or user ID values will lead to errors from the Zalo API.
- Network connectivity problems may prevent successful API calls.
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 configured.- Errors returned from the API (e.g., user not found, insufficient permissions) will be thrown and can be caught if "Continue On Fail" is enabled.
Resolution tips:
- Verify that the group ID and user ID are correct and correspond to existing entities in Zalo.
- Ensure your API credentials are up to date and have necessary permissions.
- Enable "Continue On Fail" to handle errors gracefully during batch processing.
Links and References
- Zalo Official API Documentation (for detailed API capabilities and parameters)
- n8n Documentation (for general usage of custom nodes and credential setup)