Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
The node "Evolution API" allows interaction with the Evolution API service, providing various operations grouped by resources. Specifically, for the resource Instancia and operation Definir Comportamento, it configures behavior settings of an instance such as call rejection, message reading, status reading, and synchronization preferences.
This node is useful in scenarios where you want to programmatically control how a communication instance behaves—e.g., automatically rejecting calls with a custom message, deciding whether to mark messages as read, or syncing full chat history. Practical examples include automating customer support workflows, managing presence status, or customizing interaction rules for messaging platforms integrated via Evolution API.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name assigned to the instance being configured. |
| Rejeitar Chamadas | Boolean flag to reject incoming calls or not. |
| Mensagem De Chamadas | Message sent automatically when calls are rejected. |
| Ignorar Grupos | Boolean flag indicating whether to ignore group mentions. |
| Sempre Online | Boolean flag to keep the instance always online. |
| Ler Mensagens | Boolean flag to mark messages as read or not. |
| Sincronizar Histórico Completo | Boolean flag to synchronize the complete message history. |
| Ler Status | Boolean flag to read status updates or not. |
Output
The node outputs a JSON array containing the result of the operation performed on the instance. The exact structure depends on the Evolution API response but generally includes confirmation of the updated settings or error details if the operation failed.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The base URL for requests is
https://doc.evolution-api.com/api-reference. - Proper configuration of the API credential within n8n is necessary.
Troubleshooting
- Operation Not Supported Error: If the selected operation is not implemented, the node throws an error stating the operation is unsupported. Ensure the resource and operation names are correct.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key is correctly set up.
- Invalid Property Values: Required properties like "Nome Da Instância" must be provided; otherwise, the API may reject the request.
- Network Issues: Connectivity problems to the Evolution API endpoint can cause timeouts or errors.
Links and References
- Evolution API Documentation (official API reference)
- n8n documentation on Creating Custom Nodes