Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
The node "Evolution API Direct" allows interaction with the Evolution API by directly specifying the server URL and an API key. It supports various resources and operations, including managing group members under the "Grupo" resource with the "Atualizar Membros" (Update Members) operation.
In the context of updating group members, this node enables you to add, remove, promote, or demote participants in a specified group by providing their phone numbers. This is useful for automating group management tasks such as onboarding new members, removing inactive users, or adjusting administrative roles within a group.
Practical examples:
- Automatically adding new customers to a support group after registration.
- Removing users who have unsubscribed from a service.
- Promoting trusted users to administrators based on activity or role changes.
Properties
| Name | Meaning |
|---|---|
| Server URL | The full URL of your Evolution API instance (e.g., https://api.exemplo.com). |
| API Key | The API key credential required to authenticate requests to the Evolution API. |
| Nome Da Instância | The name of the specific Evolution API instance you want to interact with. |
| ID Do Grupo | The unique identifier of the group whose members you want to update. |
| Ação | The action to perform on the group members. Options: Add Member, Remove Member, Promote to Admin, Demote to Member. |
| Membros | Comma-separated list of phone numbers representing the members to be affected (e.g., 5511999999999,5511888888888). |
Output
The node outputs a JSON array containing the response from the Evolution API after performing the requested member update operation. The exact structure depends on the API's response but typically includes confirmation of the action taken on the specified members.
If the API returns binary data (not indicated here), it would represent raw content related to the operation, but this node primarily deals with JSON responses.
Dependencies
- Requires access to the Evolution API endpoint specified by the user.
- Needs a valid API key credential for authentication.
- Proper configuration of the server URL and instance name is necessary to target the correct API instance.
Troubleshooting
Common issues:
- Incorrect or missing API key leading to authentication failures.
- Invalid group ID causing the API to reject the request.
- Malformed phone number list (e.g., missing commas or invalid formats).
- Unsupported actions if the API changes or the node is outdated.
Error messages:
"Operação não suportada."indicates that the selected operation is not supported for the chosen resource. Verify that the resource and operation names are correct.- API errors related to authorization or bad requests usually stem from incorrect credentials or parameters; double-check all inputs.
Links and References
- Evolution API Documentation (as referenced in the node's default base URL)
- General n8n documentation on creating and using custom nodes: https://docs.n8n.io/
Note: This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.