Evolution API icon

Evolution API

Interact with Evolution API

Actions64

Overview

This node integrates with the Flowise bot system via an API, allowing users to manage and interact with Flowise instances programmatically. It supports operations such as creating, updating, finding, and deleting Flowise bots, as well as managing sessions and changing session statuses.

Typical use cases include automating chatbot lifecycle management, monitoring active sessions, and controlling bot behavior remotely. For example, a user can create a new Flowise bot instance with specific trigger keywords and expiration settings, or pause a bot session based on external events.

Properties

Name Meaning
Instance Name The name of the Flowise instance that will send the message.
What Do You Want to Do Operation to perform with the Flowise integration. Options: Add Flowise, Check Flowise, Update Flowise, Delete Flowise, Search Session in Flowise, Change Session Status in Flowise.
ID Do Flowise The ID of the Flowise bot to find, update, delete, or manage sessions for. Leave empty to target all.
Url Do Flowise The URL endpoint of your Flowise API. Required for creating or updating a Flowise bot.
ApiKey Do Flowise The API key for authenticating with the Flowise bot. Required for creating or updating a Flowise bot.
Tipo De Gatilho Trigger type for the Flowise bot. Options: Keyword, All. Used when creating or updating a bot.
Operador Do Gatilho Trigger operator for keyword triggers. Options: Contains, Equals, Starts With, Ends With, Regex.
Gatilho The word, phrase, or regex pattern used as a trigger to start the Flowise bot. Required if trigger type is keyword.
Expira Em (Minutos) Number of minutes without response after which the bot should be disabled.
Palavra Chave De Finalização The word or phrase used to close the bot session.
Delay Padrão Da Mensagem (Em Milésimos) Default delay in milliseconds before sending a message from the bot.
Palavra Chave De Finalização (unknownMessage) Message shown when the bot does not recognize the input.
Listen to Messages Sent by Me Boolean indicating whether the bot listens to messages sent by the user themselves.
Pausa O Bot Quando Eu Enviar Uma Mensagem Boolean indicating whether the bot pauses when the user sends a message.
Mantem a Sessão Do Bot Open Boolean indicating whether to keep the bot session open continuously.
Tempo De Espera (Em Segundos) Debounce time in seconds; how long the bot waits to collect multiple messages before processing them together.
Numero Do Destinatario RemoteJid identifier of the recipient, used when changing session status.
Status Status to set for a session. Options: Open, Paused, Closed. Used when changing session status.

Output

The node outputs JSON data representing the result of the requested operation. This may include details about created or updated Flowise bots, lists of bots or sessions, confirmation of deletions, or status changes. The exact structure depends on the operation performed but generally reflects the API response from the Flowise service.

No binary data output is indicated.

Dependencies

  • Requires access to a Flowise API endpoint (URL).
  • Requires an API key credential for authenticating requests to the Flowise bot.
  • Network connectivity to the Flowise service.
  • Proper configuration of input properties matching the Flowise API requirements.

Troubleshooting

  • Invalid or missing API URL or API Key: Ensure the Flowise API URL and API key are correctly provided and valid.
  • Operation not supported: If an unsupported operation is selected, the node will throw an error indicating the operation is not supported.
  • Empty required fields: Some operations require mandatory fields like instanceName, apiUrl, or triggerValue. Missing these will cause errors.
  • Session management errors: When changing session status, ensure the remoteJid and status are correctly specified.
  • Timeouts or network errors: Verify network connectivity and that the Flowise API endpoint is reachable.
  • Incorrect trigger configuration: For keyword triggers, ensure the operator and trigger value are compatible (e.g., regex patterns are valid).

Links and References

Discussion