Actions25
- Get Actions
- Message Actions
- Friend Actions
- Group Actions
- Tool Actions
Overview
This node operation, Disperse Group, is designed to disperse or disband a group in the Zalo platform by its unique Group ID. It is useful when you want to programmatically dissolve a group, for example, after an event has ended or when the group is no longer needed.
Typical use cases include:
- Automatically cleaning up groups created for temporary projects or events.
- Managing group lifecycle in automated workflows.
- Integrating with other systems to control group membership and existence.
By providing the Group ID, this operation sends a request to the Zalo API to disperse the specified group.
Properties
| Name | Meaning |
|---|---|
| Group Id | The unique identifier of the Zalo group to be dispersed. This is a required string input. |
Output
The output of this node operation is a JSON object indicating the result of the disperse action. Typically, it will contain fields such as:
success: A boolean indicating whether the group was successfully dispersed.message: A string message from the API response, possibly including error details if the operation failed.
No binary data output is expected from this operation.
Dependencies
- Requires access to the Zalo API with appropriate authentication (an API key or token).
- The node must be configured with credentials that allow it to perform group management actions on Zalo.
- Network connectivity to the Zalo API endpoint is necessary.
Troubleshooting
Common Issues
- Invalid Group ID: If the provided Group ID does not exist or is malformed, the API will return an error.
- Insufficient Permissions: The API credentials used may lack permissions to disperse the group.
- Network Errors: Connectivity issues can prevent the API call from succeeding.
- API Rate Limits: Excessive requests might trigger rate limiting by Zalo.
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 the necessary rights."Network error": Ensure stable internet connection and that the Zalo API endpoint is reachable."Rate limit exceeded": Implement retry logic with backoff or reduce request frequency.
Links and References
- Zalo Official API Documentation — For detailed API usage and authentication setup.
- n8n Documentation — For general guidance on using n8n nodes and credentials.
Note: The above summary is based on static analysis of the provided source code and property definitions without executing the code.