Evolution API icon

Evolution API

Interact with Evolution API

Actions64

Overview

The node "Evolution API" allows interaction with the Evolution API service, providing various operations grouped by resource types. Specifically, for the resource Instancia and operation Definir Comportamento, it configures behavior settings of an instance. This can be useful in scenarios where you want to programmatically control how an instance handles calls, messages, status reading, and synchronization of history.

Practical examples include:

  • Automatically rejecting incoming calls with a custom message.
  • Configuring whether the instance should always appear online.
  • Enabling or disabling reading of messages and statuses.
  • Deciding if group mentions should be ignored.
  • Synchronizing full chat history for better data consistency.

Properties

Name Meaning
Nome Da Instância The name assigned to the instance.
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 be online (true/false).
Ler Mensagens Whether the instance should read messages (true/false).
Sincronizar Histórico Completo Whether to synchronize the complete chat history (true/false).
Ler Status Whether the instance should read status updates (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 data returned by the API after applying the behavior configuration.

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 or external dependencies 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 and operation names match those implemented.
  • Authentication errors: Failure to authenticate with the Evolution API will prevent execution. Verify that the API key credential is correctly set up.
  • Invalid input properties: Required fields like "Nome Da Instância" must be provided; missing or invalid inputs may cause the API call to fail.
  • API connectivity issues: Network problems or incorrect API endpoint configurations can lead to request failures.

Links and References

Discussion