Actions64
- Instance Actions
- Message Actions
- Group Actions
- Integration Actions
- Chat Actions
- Profile Actions
- Event Actions
Overview
This node, named "Evolution API," allows users to interact with the Evolution API service. Specifically for the Group resource and the Leave Group operation, it enables a user to leave a specified group by providing the instance name and the group's unique identifier. This is useful in scenarios where automated workflows need to manage group memberships dynamically, such as removing a bot or user from a chat group after certain conditions are met.
Practical examples include:
- Automatically leaving a group after completing a task.
- Managing group memberships based on external triggers or events.
- Cleaning up group memberships in bulk via automation.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the Evolution API instance to connect to. |
| Group ID | The unique identifier (JID) of the group that the user wants to leave. |
Output
The node outputs a JSON array containing the result of the leave group operation. The exact structure depends on the Evolution API response but typically includes confirmation of the action or any relevant status messages. There is no indication that binary data is output by this node.
Dependencies
- Requires an active connection to the Evolution API service.
- Needs an API authentication credential configured in n8n to authorize requests.
- The base URL for the API is
https://doc.evolution-api.com/api-reference. - The node expects JSON responses and sends JSON content-type headers.
Troubleshooting
- Operation not supported error: If the node throws an error stating the operation is not supported, verify that the resource and operation names are correctly set to "groups-api" and "leave-group" respectively.
- Authentication errors: Ensure the API key or authentication token is valid and properly configured in the node credentials.
- Invalid Group ID: Providing an incorrect or non-existent group ID will likely cause the API to return an error; double-check the group identifier.
- Instance Name issues: The instance name must correspond to a valid Evolution API instance; otherwise, the request will fail.
Links and References
- Evolution API Documentation (base URL used by the node)
- Refer to your Evolution API provider's official docs for detailed information on group management endpoints.