Actions64
- Instance Actions
- Message Actions
- Group Actions
- Chat Actions
- Profile Actions
- Event Actions
- Integration Actions
Overview
The node "Evolution API" allows interaction with the Evolution API service. Specifically, for the Resource "Instance" and Operation "Set Behavior," it enables users to configure various behavioral settings of an instance within the Evolution platform. This includes controlling call rejection, message reading behavior, online status, synchronization of history, and group mention preferences.
This node is beneficial in scenarios where automated control over instance behavior is required, such as:
- Automatically rejecting incoming calls with a custom message.
- Setting the instance to always appear online.
- Managing how messages and read statuses are handled.
- Synchronizing full chat history for better data consistency.
Practical example: A user wants to set their instance to reject all calls with a specific message while ensuring the instance remains always online and synchronizes its full chat history.
Properties
| Name | Meaning |
|---|---|
| Name Da Instância | The name identifier for the instance to be configured. |
| Rejeitar Chamadas | Whether to reject incoming calls (true/false). |
| Call Message | The message sent automatically when calls are rejected. |
| Ignore Groups | Whether to ignore mentioning groups (true/false). |
| Sempre Online | Whether the instance should always appear online (true/false). |
| Ler Mensagens | Whether to mark messages as read or not (true/false). |
| Sincronizar Histórico Completo | Whether to synchronize the complete message history (true/false). |
| Read Status | Whether to update/read the status of messages (true/false). |
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 any relevant status information.
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 in n8n is necessary for successful execution.
Troubleshooting
- Unsupported Operation Error: If the selected operation is not supported for the resource, the node throws an error indicating the function is not supported. Ensure that the Resource and Operation names are correctly specified.
- Authentication Failures: Missing or invalid API credentials will cause authentication errors. Verify that the API key is correctly configured.
- Invalid Property Values: Providing incorrect types or missing required properties (e.g., instance name) may cause the API to reject the request. Double-check input values before execution.
- Network Issues: Connectivity problems to the Evolution API endpoint can cause timeouts or failures. Confirm network access and API availability.
Links and References
- Evolution API Documentation (official API reference)
- n8n documentation on Creating Custom Nodes