Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
The node "Evolution API Direct" allows users to interact directly with the Evolution API by specifying a resource and operation, along with necessary connection details such as server URL and API key. Specifically, for the Resource "Grupo" and Operation "Encontrar Participantes," this node fetches the list of participants in a specified group. This is useful in scenarios where you need to programmatically retrieve group membership information from the Evolution platform, for example, to audit group members, synchronize participant data with other systems, or trigger workflows based on group composition.
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 connect to. |
| ID Do Grupo | The unique identifier (JID) of the group whose participants you want to find. |
Output
The node outputs a JSON array containing the participants found in the specified group. Each item in the array represents a participant's data as returned by the Evolution API. The exact structure depends on the API response but typically includes participant identifiers and related metadata.
If the node supports binary data output, it is not indicated in the provided code or properties, so the output is purely JSON.
Dependencies
- Requires access to the Evolution API endpoint specified by the user.
- Requires a valid API key credential for authentication.
- The node expects the user to provide the correct server URL and instance name corresponding to their Evolution API setup.
Troubleshooting
Common Issues:
- Incorrect or missing API key will result in authentication errors.
- Providing an invalid or malformed Server URL or Instance Name may cause connection failures.
- Using an unsupported operation or resource combination will throw an error indicating the operation is not supported.
- Missing required parameters like Group ID will prevent the node from executing properly.
Error Messages:
"Operação não suportada."— This means the selected operation for the resource is not implemented. Verify that the Resource and Operation names are correct.- Network or authentication errors typically arise if the Server URL or API Key is incorrect; ensure these are valid and have proper permissions.
Resolution Tips:
- Double-check all input parameters for correctness.
- Ensure the API key has sufficient privileges.
- Confirm the Evolution API instance is reachable from the n8n environment.
- Review API documentation for any changes in endpoints or required parameters.
Links and References
- Evolution API official documentation (replace with actual URL): https://doc.evolution-api.com/api-reference
- n8n documentation on creating custom nodes: https://docs.n8n.io/integrations/creating-nodes/