Evolution API icon

Evolution API

Interact with Evolution API

Actions64

Overview

The "Integração" node with the "Flowise" operation enables interaction with Flowise bots through various management actions such as creating, updating, finding, deleting Flowise instances, managing sessions, and changing session statuses. This node is useful for automating chatbot workflows, managing bot lifecycle, and controlling user sessions programmatically.

Common scenarios include:

  • Automating the deployment or update of chatbot configurations.
  • Querying existing Flowise bots to retrieve their details.
  • Managing active chat sessions by fetching or modifying their status.
  • Integrating chatbot controls into broader automation workflows.

For example, a user can create a new Flowise bot instance with specific trigger keywords and expiration settings, or pause an ongoing chat session based on external events.

Properties

Name Meaning
Nome Da Instancia The name of the Flowise instance that will send messages.
O Que Deseja Fazer Action to perform with the Flowise integration. Options: Add Flowise, Find Flowise, Update Flowise, Delete Flowise, Search Session in Flowise, Change Session Status in Flowise.
ID Do Flowise The ID of the Flowise bot to target. Leave empty to operate on all (used in find, update, delete, fetch sessions, change status operations).
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 your 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 defining how the trigger keyword is matched. Options: Contains, Equals, Starts With, Ends With, Regex. Only applicable if trigger type is Keyword.
Gatilho The keyword, 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 responses after which the bot should be deactivated.
Palavra Chave De Finalização Keyword or phrase used to close/end 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 or phrase sent when the bot does not recognize the input.
Escuta Mensagens Enviadas Por Mim Boolean flag indicating whether the bot listens to messages sent by the user themselves.
Pausa O Bot Quando Eu Enviar Uma Mensagem Boolean flag indicating whether the bot pauses when the user sends a message.
Mantem a Sessão Do Bot Aberta Boolean flag indicating whether to keep the bot session open indefinitely.
Tempo De Espera (Em Segundos) Time in seconds the bot waits for additional messages after receiving one, then combines them into a single message.
Numero Do Destinatario The remote identifier (JID) of the recipient. Required when changing session status.
Status The status to set for a session. Options: Opened, Paused, Closed. Used when changing session status.

Output

The node outputs JSON data representing the result of the requested operation on the Flowise bot or session. The structure varies depending on the action performed:

  • For creation or update operations, it returns confirmation and details of the created/updated Flowise bot.
  • For find or fetch operations, it returns one or more Flowise bot or session objects with their properties.
  • For delete operations, it returns confirmation of deletion.
  • For session status changes, it returns the updated session status information.

No binary data output is indicated.

Dependencies

  • Requires access to a Flowise API endpoint (URL) and a valid API key credential for authentication.
  • The node expects the Flowise API to be reachable and properly configured to accept requests.
  • No other external dependencies are indicated.

Troubleshooting

  • Invalid or missing API URL or API Key: Ensure the Flowise API URL and API key are correctly provided and valid.
  • Unsupported operation error: Occurs if an unsupported operation is selected; verify the operation matches the supported list.
  • Empty or incorrect Flowise ID: For operations requiring a Flowise ID, ensure the correct ID is provided; leaving it empty may cause unexpected results.
  • Session status change failures: Verify the remote JID and status values are correct and that the session exists.
  • Timeouts or connectivity issues: Check network connectivity to the Flowise API endpoint.
  • Trigger keyword misconfiguration: If the bot does not respond as expected, verify the trigger type, operator, and value are correctly set.

Links and References

Discussion