Actions64
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
- Instancia Actions
- Mensagem Actions
- Grupo Actions
Overview
The node "Evolution API" allows interaction with the Evolution API service. Specifically, for the resource Instancia and operation Definir Comportamento, it configures the behavior settings of an instance within the Evolution system. This includes options such as rejecting calls, setting call rejection messages, managing group mentions, online status, message reading, history synchronization, and status reading.
This node is useful in scenarios where automated control over instance behavior is needed, such as customizing how an instance handles incoming calls or messages, controlling presence status, or synchronizing chat history. For example, a user might want to automatically reject phone calls with a custom message while keeping the instance always online and syncing full chat history.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance to configure. |
| Rejeitar Chamadas | Whether to reject incoming calls (true/false). |
| Mensagem De Chamadas | Message sent when calls are rejected. |
| Ignorar Grupos | Whether to ignore group mentions (true/false). |
| Sempre Online | Whether the instance should always appear online (true/false). |
| Ler Mensagens | Whether the instance should mark messages as read (true/false). |
| Sincronizar Histórico Completo | Whether to synchronize the full chat history (true/false). |
| Ler Status | Whether to read status updates (true/false). |
Output
The node outputs a JSON array containing the result of the behavior configuration operation. The exact structure depends on the Evolution API response but generally confirms the updated settings or returns status information about the instance behavior update.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node expects the Evolution API service to be accessible and properly configured.
- No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
- Operation not supported error: If the selected operation or resource is not supported, the node throws an error indicating the unsupported function. Ensure that the resource is set to "instances-api" and operation to "instance-settings" to match this functionality.
- API authentication errors: If the API key or credentials are invalid or missing, the node will fail to connect. Verify that the correct API key credential is configured.
- Invalid property values: Required properties like "Nome Da Instância" must be provided; otherwise, the node may throw validation errors.
- Network issues: Connectivity problems with the Evolution API endpoint can cause timeouts or failures.
Links and References
- Evolution API official documentation (not provided here, but users should consult their API docs for detailed behavior settings).
- n8n documentation on creating and using API nodes: https://docs.n8n.io/integrations/creating-nodes/