Actions64
- Instance Actions
- Chat Actions
- Message Actions
- Group Actions
- Profile Actions
- Event Actions
- Integration Actions
Overview
This node integrates with the Flowise bot system via an API, allowing users to manage and interact with Flowise bots programmatically. It supports operations such as creating, updating, deleting, and checking Flowise bots, as well as managing sessions and their statuses.
Common scenarios include automating chatbot lifecycle management, monitoring active sessions, and controlling session states remotely. For example, a user can create a new Flowise bot with specific trigger keywords and session timeout settings, or pause a bot session based on external events.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the instance that will send the message |
| What Do You Want To Do | Operation to perform with Flowise integration: Add Flowise, Check Flowise, Update Flowise, Delete Flowise, Fetch Session In Flowise, Change Session Status In Flowise |
| Flowise ID | The identifier of the Flowise bot to target for update, find, delete, fetch sessions, or change status; leave empty to target all (where applicable) |
| Flowise URL | The base URL of the Flowise API endpoint |
| Flowise ApiKey | The API key used to authenticate requests to the Flowise bot |
| Trigger Type | Type of trigger to activate the bot: Keyword or All |
| Trigger Operator | How the trigger keyword is matched: Contains, Equals, Starts With, Ends With, Regex |
| Trigger | The word, phrase, or regex pattern used as a trigger to start the Flowise bot |
| Expires In (Minutes) | Duration in minutes without responses after which the bot should be deactivated |
| Finish Keyword | Word or phrase used to close the bot session |
| Default Message Delay (In Milliseconds) | Delay time in milliseconds before the bot sends messages |
| Unknown Message | Message sent when the bot receives an unrecognized input |
| Listen To Messages Sent By Me | Whether the bot listens to messages sent by the user itself |
| Pause The Bot When I Send A Message | Whether sending a message from the user pauses the bot |
| Keep The Bot Session Open | Whether to keep the bot session open indefinitely |
| Wait Time (In Seconds) | Time in seconds the bot waits to merge multiple incoming messages into one |
| Recipient Number | The remote identifier (RemoteJid) of the recipient for changing session status |
| Status | The desired session status: Opened, Paused, or Closed |
Output
The node outputs JSON data representing the result of the selected operation. This typically includes details about the Flowise bot or session affected, such as confirmation of creation, updated properties, session lists, or status changes.
No binary data output is indicated.
Dependencies
- Requires access to a Flowise API endpoint specified by the user.
- Requires a valid API key credential for authenticating requests to the Flowise API.
- Network connectivity to the Flowise service.
- No other external dependencies are indicated.
Troubleshooting
- Invalid API URL or Key: Ensure the Flowise URL and API key are correct and have proper permissions.
- Missing Required Parameters: Operations like update or delete require a valid Flowise ID; ensure it is provided.
- Unsupported Operation: Selecting an unsupported operation or resource combination will throw an error indicating the function is not supported.
- Session Management Errors: Changing session status requires a valid recipient number and status; verify these inputs.
- Timeouts or Connectivity Issues: Network problems may cause request failures; check connectivity and API availability.
Links and References
- Flowise Official Documentation (example placeholder)
- n8n Documentation on Creating Custom Nodes
- REST API best practices for authentication and error handling