Actions25
- Message Actions
- Friend Actions
- Get Actions
- Group Actions
- Tool Actions
Overview
This node operation, "Disperse Group" under the "Group" resource, is designed to disperse or disband a group in the Zalo platform. It effectively removes all members and dissolves the group identified by its unique Group Id.
Common scenarios for this node include:
- Automating the cleanup of groups that are no longer needed.
- Managing group lifecycle in workflows where groups are dynamically created and later dispersed.
- Integrating with other systems to maintain synchronized group states.
Practical example:
- After completing a project discussion in a Zalo group, an automation workflow can trigger this node to disperse the group, ensuring no further messages are sent and the group is archived.
Properties
| Name | Meaning |
|---|---|
| Group Id | The unique identifier of the Zalo group to be dispersed. This is a required string input. |
Output
The node outputs an array of JSON objects, each representing the result of the disperse operation per input item. Each object contains at least:
json: An object with details about the success or failure of the disperse action.- Typically includes a boolean status indicating if the operation was successful.
- May include error messages or codes if the operation failed.
No binary data output is produced by this node.
Dependencies
- Requires access to the Zalo API with appropriate permissions to manage groups.
- Needs an API key credential or authentication token configured in n8n to authorize requests.
- The node internally uses HTTP requests to communicate with Zalo's backend services.
Troubleshooting
Common Issues
- Invalid Group Id: If the provided Group Id does not exist or is malformed, the node will fail to disperse the group.
- Insufficient Permissions: The API credentials used may lack the necessary rights to disperse groups.
- Network or API Errors: Temporary network issues or Zalo API downtime can cause failures.
Error Messages and Resolutions
- "Group not found": Verify the Group Id is correct and the group exists.
- "Unauthorized" or "Permission denied": Check that the API credentials have group management permissions.
- Timeout or connection errors: Ensure stable internet connectivity and that Zalo API endpoints are reachable.
Links and References
- Zalo Official API Documentation (for general API usage and authentication)
- n8n community forums and documentation for custom node development and troubleshooting.
Note: The above summary is based on static analysis of the provided source code and property definitions without runtime execution.