Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
This node, named "Evolution API Direct," allows users to interact directly with the Evolution API by specifying a custom server URL and an API key. It is designed for scenarios where users need to perform operations on the Evolution API without relying on predefined resource-operation pairs, offering flexibility through direct URL access.
Typical use cases include:
- Integrating custom or less common endpoints of the Evolution API not covered by standard nodes.
- Quickly testing or prototyping API calls by specifying the exact server URL and authentication key.
- Automating workflows that require direct interaction with Evolution API resources using user-provided URLs.
Properties
| Name | Meaning |
|---|---|
| Server URL | The full URL of the Evolution API endpoint you want to call (e.g., https://api.exemplo.com). This is required. |
| API Key | The API key for authenticating requests to your Evolution API instance or global account. This is required and treated as sensitive information. |
Output
The node outputs a JSON array containing the response data from the Evolution API call. Each item in the array corresponds to one result object returned by the executed operation.
If the API returns binary data, it would typically be handled separately, but based on the provided code, the output focuses on JSON responses.
Dependencies
- Requires an active Evolution API endpoint accessible via the provided Server URL.
- Requires a valid API key credential for authentication.
- No additional external dependencies are indicated beyond the Evolution API itself.
- The node uses standard HTTP headers (
Accept: application/jsonandContent-Type: application/json) for communication.
Troubleshooting
- Unsupported Operation Error: If you select an operation that is not supported for the chosen resource, the node throws an error stating the operation is not supported. To fix this, ensure you select a valid operation-resource combination.
- Invalid Server URL or API Key: Providing an incorrect URL or invalid API key will likely result in authentication errors or connection failures. Verify the URL format and API key correctness.
- Network Issues: Connectivity problems to the specified server URL can cause request failures. Check network settings and firewall rules.
- Empty or Malformed Responses: If the API returns unexpected data, verify that the requested operation and parameters conform to the Evolution API specifications.
Links and References
- Evolution API Documentation (as referenced in the node's default base URL)
- General n8n documentation on creating custom nodes