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 session states programmatically within n8n workflows.

Common scenarios include:

  • Automating the deployment or update of Flowise bots.
  • Querying existing Flowise bots or sessions to monitor status.
  • Controlling session flow by pausing, opening, or closing sessions based on external triggers.
  • Integrating chatbot responses into broader automation pipelines.

Practical example:

  • Automatically create a new Flowise bot instance when a new customer support channel is added.
  • Pause a chatbot session if a user sends a specific command.
  • Fetch all active sessions to generate reports or trigger alerts.

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 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 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 deactivated.
Palavra Chave De Finalização Keyword or phrase used to close the bot session.
Delay Padrão Da Mensagem (Em Milésimos) Default delay in milliseconds before the bot sends a message.
Palavra Chave De Finalização (unknownMessage) Message or phrase used when the bot does not recognize input.
Escuta Mensagens Enviadas Por Mim 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 Aberta Boolean indicating whether to keep the bot session open.
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 RemoteJid (identifier) of the recipient. Required when changing session status.
Status Status to set for the 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, update, or deletion operations, it typically returns confirmation details or the updated resource data.
  • For find or fetch operations, it returns arrays or objects containing Flowise bot or session information.
  • For status changes, it returns the updated session status confirmation.

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.
  • Proper network connectivity to the Flowise service.
  • 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.
  • Operation not supported error: Occurs if an unsupported operation is selected; verify the operation matches the available options.
  • 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 remoteJid and status values are correct and correspond to existing sessions.
  • Timeouts or connectivity issues: Check network access to the Flowise API endpoint.
  • Trigger configuration errors: When using keyword triggers, ensure the trigger value and operator are properly set to match expected inputs.

Links and References

Discussion