Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
The node "Evolution API" allows interaction with the Evolution API to perform various operations on different resources. Specifically, for the resource "Grupo" and operation "Atualizar Membros" (Update Members), it enables managing group participants by adding, removing, promoting to admin, or demoting members within a specified group. This is useful in scenarios where automated management of group membership is needed, such as moderating chat groups, updating team members dynamically, or administrating user roles programmatically.
Practical examples:
- Automatically add new users to a group when they register.
- Remove inactive members from a group based on certain criteria.
- Promote trusted members to administrators to help manage the group.
- Demote members who no longer require admin privileges.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance to connect to the Evolution API. |
| ID Do Grupo | The unique identifier of the group whose members will be updated. |
| Ação | The action to perform on the members: Add member, Remove member, Promote to administrator, or Demote to member. |
| Membros | Comma-separated list of phone numbers representing the members to update (e.g., 5511999999999,5511888888888). |
Output
The node outputs a JSON array containing the result of the executed operation. Each item in the output corresponds to the response from the Evolution API after performing the requested update on group members. The exact structure depends on the API's response but generally includes confirmation of success or failure for each member update action.
If the node supports binary data output, it is not indicated in the provided code or properties and thus can be assumed to only output JSON data.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node expects the Evolution API to be accessible and properly configured.
- No additional external dependencies are indicated beyond the API connection.
Troubleshooting
- Unsupported Operation Error: If the selected operation is not supported for the chosen resource, the node throws an error stating the operation is not supported. Ensure that the resource and operation names are correctly set.
- Invalid Group ID or Members List: Providing an incorrect group ID or improperly formatted members list (not comma-separated phone numbers) may cause API errors or failed updates.
- Authentication Issues: Missing or invalid API credentials will prevent successful communication with the Evolution API.
- Network or API Downtime: Connectivity issues or API service downtime will result in request failures.
To resolve these issues:
- Double-check input parameters for correctness.
- Verify API credentials and permissions.
- Confirm network connectivity and API availability.
Links and References
- Evolution API official documentation (not provided in source; consult your API provider)
- n8n documentation on creating and using custom nodes: https://docs.n8n.io/creating-nodes/
- General best practices for API authentication and error handling in n8n workflows.