Evolution API icon

Evolution API

Interact with Evolution API
Join our community

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.

Typical use cases include:

  • Automating the deployment and configuration of Flowise bots.
  • Querying existing bots or sessions to monitor or audit activity.
  • Updating bot triggers, messages, and behavior dynamically.
  • Managing session states (open, paused, closed) based on external events or user input.

For example, a user can create a new Flowise bot instance with specific trigger keywords and expiration settings, or pause a user's active session when needed.

Properties

Name Meaning
Nome Da Instancia The name of the Flowise instance that will send the message.
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 search 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 bot. Options: Keyword, All. Used when creating or updating a Flowise bot.
Operador Do Gatilho Trigger operator defining how the keyword matches. 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. Required for create/update operations.
Palavra Chave De Finalização Keyword or phrase used to close/end the bot session. Required for create/update operations.
Delay Padrão Da Mensagem (Em Milésimos) Default delay in milliseconds before the bot sends a message. Required for create/update operations.
Palavra Chave De Finalização (unknownMessage) Message or phrase sent when the bot does not recognize the input. Required for create/update operations.
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 continuously.
Tempo De Espera (Em Segundos) Time in seconds the bot waits for additional messages after receiving one, then combines them into a single message. Required for create/update operations.
Numero Do Destinatario The remote identifier (JID) of the recipient. Required for changing session status.
Status The status to set for a session. Options: Opened, Paused, Closed. Required for changing session status.

Output

The node outputs JSON data representing the result of the selected operation. The structure varies depending on the action performed:

  • For creation or update operations, it typically returns confirmation details about the Flowise bot instance.
  • For find or fetch operations, it returns lists or objects representing Flowise bots or sessions.
  • For delete operations, it returns success or failure confirmation.
  • For session status changes, it returns the updated session state.

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.
  • 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: If an unsupported operation is selected, the node throws an error indicating the operation is not supported.
  • Empty or incorrect Flowise ID: When required, ensure the Flowise ID is correctly specified; leaving it empty may cause unexpected results.
  • Trigger configuration errors: If using keyword triggers, ensure the trigger value and operator are correctly set; invalid regex patterns may cause failures.
  • Session status change failures: Verify the remote JID and status values are correct and correspond to existing sessions.
  • Timeouts or connectivity issues: Confirm network connectivity to the Flowise API endpoint.

Links and References

Discussion