Actions25
- Message Actions
- Friend Actions
- Get Actions
- Group Actions
- Tool Actions
Overview
This node operation "Add Group Deputy" for the resource "Group" is designed to assign a deputy (a secondary administrator or moderator) within a Zalo group. It allows a user to designate another user as a deputy in a specified group, which can be useful for delegating administrative responsibilities such as managing members, moderating content, or handling group settings.
Common scenarios where this node is beneficial:
- When a group owner wants to share management duties with trusted members.
- Automating the process of assigning deputies based on certain triggers or workflows.
- Managing large groups by distributing admin tasks without transferring full ownership.
Practical example:
- Automatically add a deputy when a new member reaches a certain level of activity or trust.
- Assign deputies during onboarding workflows to help manage new group members.
Properties
| Name | Meaning |
|---|---|
| User Id | The unique identifier of the Zalo user who will 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 JSON data representing the result of the deputy addition operation. This typically includes confirmation of success or failure and may contain details about the updated group or deputy status.
If the operation involves any binary data (e.g., media attachments), it would be included in the binary output field, but for this specific operation, the focus is on JSON response data indicating the action's outcome.
Dependencies
- Requires an active connection to the Zalo API with appropriate permissions to manage group roles.
- Needs an API key credential or authentication token configured in n8n to authorize requests.
- The node internally uses HTTP request libraries to communicate with Zalo's backend services.
Troubleshooting
Common issues:
- Invalid or missing User Id or Group Id leading to failed API calls.
- Insufficient permissions or invalid API credentials causing authorization errors.
- Network connectivity problems preventing communication with Zalo servers.
Error messages and resolutions:
- "User not found" — Verify that the User Id is correct and the user exists on Zalo.
- "Group not found" — Check that the Group Id corresponds to an existing group accessible by the authenticated account.
- "Unauthorized" or "Invalid credentials" — Ensure the API key or authentication token is valid and has necessary scopes.
- "Operation failed" — Review API limits, group settings, or consult Zalo API documentation for restrictions.
Links and References
- Zalo Official API Documentation
- Zalo Group Management API Reference
- n8n Documentation on Creating Custom Nodes
Note: The provided source code was obfuscated and minified, so the summary is based on static analysis of input properties and typical usage patterns for such operations in Zalo API integrations.