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 server URL and an API key. It supports various resources and operations, including searching for instances ("Buscar Instancia"). This node is useful when you want to query or manipulate data in the Evolution API without relying on pre-built integrations, giving flexibility to work with custom endpoints or specific API features.
A practical example is searching for a particular instance by its name within your Evolution API environment, which can be helpful for automation workflows that need to retrieve instance details dynamically.
Properties
| Name | Meaning |
|---|---|
| Server URL | The full URL of your Evolution API server (e.g., https://api.exemplo.com). |
| API Key | The API key credential used to authenticate requests against the Evolution API. |
| Nome Da Instância | The name of the instance you want to search for within the Evolution API. |
Output
The node outputs a JSON array containing the results returned from the Evolution API for the requested operation. For the "Buscar Instancia" operation, this will typically include details about the instance(s) matching the provided name.
If the API returns binary data (not indicated in the provided code), it would be included as binary output, but based on the static analysis, the output is JSON-formatted data representing the API response.
Dependencies
- Requires access to the Evolution API endpoint specified by the user.
- Requires a valid API key for authentication.
- No additional external dependencies beyond standard HTTP request capabilities provided by n8n.
Troubleshooting
- Operation not supported error: If you select an unsupported operation or resource, the node throws an error indicating the operation is not supported. Ensure you use valid combinations of resource and operation.
- Authentication errors: If the API key or server URL is incorrect or missing, requests will fail. Verify the API key and URL are correct and have proper permissions.
- Empty or no results: If the instance name does not match any existing instance, the output may be empty. Double-check the instance name spelling and existence.
- Network issues: Ensure the server URL is reachable from the n8n environment and there are no firewall or connectivity problems.
Links and References
- Evolution API Documentation: https://doc.evolution-api.com/api-reference (as referenced in the default baseURL)
- n8n Documentation: https://docs.n8n.io/ (for general node usage and troubleshooting)