Actions64
- Instance Actions
- Chat Actions
- Message Actions
- Group Actions
- Profile Actions
- Event Actions
- Integration Actions
Overview
The "Leave Group" operation in the Group resource allows a user to leave a specified group within an instance of the Evolution API. This node is useful for automating group membership management, such as removing a user from a chat or collaboration group when they no longer need access or are leaving a project.
Practical examples include:
- Automatically removing users from project groups after project completion.
- Managing group memberships based on user status changes.
- Integrating with other workflows that require dynamic group membership updates.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the Evolution API instance where the group exists. This identifies which environment or server to target. |
| Group ID | The unique identifier of the group to leave. This specifies exactly which group the user will be removed from. |
Output
The node outputs a JSON array containing the response from the Evolution API after attempting to leave the group. The structure typically includes confirmation of the action or any relevant status messages returned by the API.
If the API supports binary data output (not indicated here), it would represent related files or media associated with the group leave operation, but this node primarily deals with JSON responses.
Dependencies
- Requires an active connection to the Evolution API via an API key or authentication token configured in n8n credentials.
- The node depends on the Evolution API endpoint for group management.
- Proper network access and permissions to call the Evolution API are necessary.
Troubleshooting
- Unsupported operation error: If the node throws an error stating the operation is unsupported, verify that the "resource" is set to "groups-api" and the operation to "leave-group".
- Authentication errors: Ensure the API key or authentication token is valid and has permissions to modify group memberships.
- Invalid Group ID: If the group ID does not exist or the user is not a member, the API may return an error. Double-check the group ID value.
- Network issues: Connectivity problems can cause request failures; verify network access to the Evolution API endpoint.
Links and References
- Evolution API official documentation: https://doc.evolution-api.com/api-reference
- n8n documentation on creating custom nodes: https://docs.n8n.io/integrations/creating-nodes/