Actions25
- Get Actions
- Message Actions
- Friend Actions
- Group Actions
- Tool Actions
Overview
This node operation "Add Group Deputy" for the resource "Group" is designed to assign a deputy (a secondary admin or moderator) within a Zalo group chat. It allows a user with appropriate permissions to designate another user as a group deputy, thereby delegating some administrative responsibilities.
Common scenarios where this node would be beneficial include:
- Managing large group chats where multiple admins are needed.
- Delegating moderation tasks without transferring full ownership.
- Automating group management workflows by programmatically assigning deputies.
Practical example:
- A community manager wants to add a trusted member as a deputy to help moderate discussions and manage group settings. Using this node, they provide the User ID of the member and the Group ID to assign the deputy role.
Properties
| Name | Meaning |
|---|---|
| User Id | The unique identifier of the Zalo user to be added as a deputy in the group. |
| Group Id | The unique identifier of the Zalo group where the deputy role will be assigned. |
Output
The node outputs an array of JSON objects representing the result of the operation for each input item. Each object typically contains:
success: A boolean indicating whether the deputy was successfully added.data: Additional information returned from the API about the operation, such as confirmation details or error messages if any.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Zalo API with proper authentication credentials (e.g., an API key or token).
- The node depends on the Zalo service's group management API endpoints.
- Proper permissions must be granted to the authenticated user to modify group roles.
Troubleshooting
Common Issues
- Invalid User Id or Group Id: If either ID is incorrect or does not exist, the operation will fail.
- Insufficient Permissions: The authenticated user may lack rights to assign deputies in the specified group.
- API Rate Limits: Excessive requests might trigger rate limiting by the Zalo API.
- Network Errors: Connectivity issues can cause request failures.
Error Messages and Resolutions
"User not found": Verify the User Id is correct and the user exists on Zalo."Group not found": Confirm the Group Id is valid and accessible."Permission denied": Ensure the API credentials have sufficient privileges."Rate limit exceeded": Implement retry logic with exponential backoff.- Network timeouts or connection errors: Check network connectivity and proxy/firewall settings.
Links and References
- Zalo Official API Documentation
- Zalo Group Management API Reference
- n8n Documentation on Creating Custom Nodes
Note: This summary is based solely on static analysis of the provided source code and property definitions, without runtime execution or access to internal credential names.