Actions64
- Instancia Actions
- Mensaje Actions
- Grupo Actions
- Crear Grupo
- Actualizar Imagen Del Grupo
- Actualizar Nombre Del Grupo
- Actualizar Descripción Del Grupo
- Actualizar Configuraciones
- Actualizar Miembros
- Buscar Enlace De Invitación
- Revocar Enlace De Invitación
- Enviar Enlace De Invitación
- Buscar Grupos
- Encontrar Participantes
- Mensajes Temporales
- Unirse Al Grupo
- Salir Del Grupo
- Chat Actions
- Perfil Actions
- Evento Actions
- Integración Actions
Overview
This node integrates with the Flowise bot system through an API, allowing users to manage and interact with Flowise instances programmatically. It supports operations such as creating, verifying, updating, deleting Flowise bots, fetching sessions, and changing session statuses.
Typical use cases include automating chatbot lifecycle management, monitoring active sessions, or controlling bot behavior remotely within an n8n workflow. For example, a user can create a new Flowise bot instance with specific trigger keywords and session timeout settings, or pause a bot session based on external events.
Properties
| Name | Meaning |
|---|---|
| Nombre De La Instancia | The name of the Flowise instance for integration purposes. |
| Qué Desea Hacer | Operation to perform with Flowise integration. Options: Añadir Flowise (create), Verificar Flowise (find), Actualizar Flowise (update), Eliminar Flowise (delete), Buscar Sesión En Flowise (fetch sessions), Cambiar Estado De La Sesión En Flowise (change status). |
| ID De Flowise | The ID of the Flowise bot to find, update, delete, fetch sessions, or change status. Leave empty to target all. |
| URL De Flowise | The base URL of the Flowise API endpoint. Required for creating or updating a Flowise bot. |
| APIKey De Flowise | The API key token for authenticating requests to the Flowise bot. Required for creating or updating a Flowise bot. |
| Tipo De Disparador | Trigger type for the bot activation. Options: Palabra Clave (keyword), Todos (all messages). |
| Operador Del Disparador | Operator for matching the trigger keyword. Options: Contiene (contains), Igual A (equals), Comienza Con (startsWith), Termina Con (endsWith), Regex (regex). Only applicable if trigger type is "keyword". |
| Disparador | The keyword, phrase, or regex pattern used to trigger the Flowise bot. Required if trigger type is "keyword". |
| Expira En (Minutos) | Number of minutes without response after which the bot will be deactivated. |
| Palabra Clave De Finalización | Keyword or phrase used to close the bot session. |
| Retraso Predeterminado Del Mensaje (En Milisegundos) | Default delay in milliseconds before the bot sends a message. |
| Mensaje Desconocido | Message shown when the bot does not understand the user's input. |
| Escucha Mensajes Enviadas Por Mim | Whether the bot listens to messages sent by the user themselves (boolean). |
| Pausa O Bot Quando Eu Enviar Uma Mensagem | Whether the bot pauses when the user sends a message (boolean). |
| Mantem a Sessão Do Bot Aberta | Whether to keep the bot session open continuously (boolean). |
| Tempo De Espera (Em Segundos) | Time in seconds that the bot waits for additional messages after receiving one, then merges them into a single message. |
| Número Del Destinatario | RemoteJid identifier of the recipient. Required when changing the status of a Flowise session. |
| Estado | Status to set for the session. Options: Abierta (opened), Pausada (paused), Cerrada (closed). Used when changing session status. |
Output
The node outputs JSON data representing the result of the performed operation. This typically includes details about the Flowise bot instance(s), session information, or confirmation of actions like creation, update, deletion, or status changes.
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 configuration of these credentials and URLs within the node parameters is necessary.
Troubleshooting
Common issues:
- Missing or incorrect API URL or API key will cause authentication failures.
- Providing an invalid Flowise bot ID when updating, deleting, or fetching sessions may result in errors or empty responses.
- Incorrect trigger keyword/operator combinations might prevent the bot from activating as expected.
- Session status changes require a valid remoteJid; missing this will cause errors.
Error messages:
- "Operation not supported" if an unsupported operation is selected.
- Authentication errors if API key or URL are invalid.
- Validation errors if required parameters are missing.
Resolutions:
- Verify API URL and API key correctness.
- Ensure required fields are filled according to the chosen operation.
- Confirm that IDs and remoteJid values correspond to existing Flowise entities.
Links and References
- Flowise Official Documentation (for understanding Flowise bot concepts and API)
- n8n documentation on Creating Custom Nodes