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 parameters such as server URL and API key. Specifically, for the Resource "Instancia" and Operation "Definir Comportamento," this node configures behavior settings of an instance in the Evolution system. This can include controlling call rejection, message reading, status reading, synchronization of history, and other instance-specific behaviors.
This node is beneficial when you want to programmatically manage or automate the configuration of your Evolution API instances without manually adjusting settings through a UI. For example, you could automatically set an instance to reject calls during off-hours with a custom message or enable full history synchronization for audit purposes.
Properties
| Name | Meaning |
|---|---|
| Server URL | The full URL of your Evolution API endpoint (e.g., https://api.exemplo.com). |
| API Key | The API key credential for authenticating requests to the Evolution API instance or global. |
| Nome Da Instância | The name identifier for the specific instance whose behavior you want to define. |
| Rejeitar Chamadas | Boolean flag indicating whether incoming calls should be rejected. |
| Mensagem De Chamadas | Message sent back if calls are rejected (default: "Não aceitamos ligações telefônicas."). |
| Ignorar Grupos | Boolean flag indicating whether group mentions should be ignored. |
| Sempre Online | Boolean flag indicating if the instance should always appear online. |
| Ler Mensagens | Boolean flag indicating whether messages should be marked as read. |
| Sincronizar Histórico Completo | Boolean flag indicating whether to synchronize the complete message history. |
| Ler Status | Boolean flag indicating whether to read status updates. |
Output
The node outputs a JSON array containing the response from the Evolution API after applying the behavior settings to the specified instance. The exact structure depends on the API's response but generally includes confirmation of updated settings or error details if the operation failed.
No binary data output is indicated.
Dependencies
- Requires access to the Evolution API endpoint specified by the user.
- Requires a valid API key credential for authentication.
- Network connectivity to the provided Server URL.
- No additional external dependencies beyond standard HTTP request capabilities.
Troubleshooting
Common Issues:
- Incorrect or missing Server URL or API Key will cause authentication failures.
- Providing an unsupported operation or resource combination will throw an error indicating the operation is not supported.
- Network issues or incorrect API endpoint URLs may result in connection errors.
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.- Authentication errors typically indicate invalid or expired API keys; ensure the API key is current and has appropriate permissions.
- Timeout or network errors suggest connectivity problems; check your internet connection and API server availability.
Links and References
- Evolution API Documentation: https://doc.evolution-api.com/api-reference
- n8n Node Development Guide: https://docs.n8n.io/integrations/creating-nodes/