Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
The node "Evolution API" provides an interface to interact with the Evolution API, specifically supporting operations on various resources. For the resource "Grupo" and operation "Sair Do Grupo" (Leave Group), this node allows a user to leave a specified group by providing the group ID and instance name. 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 when 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 participations in bulk workflows.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance to connect to. This identifies which Evolution API instance to use. |
| ID Do Grupo | The unique identifier (ID) 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 API key credential for authenticating with the Evolution API.
- The node expects the Evolution API service to be accessible and properly configured.
- No additional environment variables are explicitly required beyond the API authentication.
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 credential is valid and has sufficient permissions to perform group leave operations.
- Invalid group ID: Providing an incorrect or non-existent group ID will likely cause the API call to fail. Double-check the group ID format and existence.
- Instance name issues: The instance name must correspond to a valid and active Evolution API instance; otherwise, the request will fail.
Links and References
- Evolution API official documentation (not provided in source, please refer to your API provider)
- n8n documentation on creating custom nodes and using credentials: https://docs.n8n.io/
- General REST API usage best practices