Actions64
- Instance Actions
- Message Actions
- Group Actions
- Integration Actions
- Chat Actions
- Profile Actions
- Event Actions
Overview
The node provides integration with the Dify bot service through an API, allowing users to manage and interact with Dify bots programmatically. It supports operations such as creating, finding, updating, deleting Dify bots, fetching sessions, and changing session statuses.
This node is beneficial in scenarios where automated management of chatbot instances is required, such as:
- Automating the deployment and configuration of chatbots.
- Monitoring and managing active chatbot sessions.
- Controlling chatbot behavior dynamically based on external triggers or workflows.
Practical examples include:
- Creating a new Dify bot instance with specific trigger keywords and session timeout settings.
- Querying existing Dify bots by ID to retrieve their configurations.
- Updating bot parameters like trigger phrases or message delays.
- Pausing or closing active chatbot sessions remotely.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the Dify bot instance that will send messages. |
| What Do You Want To Do | Operation to perform with the Dify integration: Add Dify, Check Dify, Update Dify, Delete Dify, Fetch Session In Dify, Change Session Status In Dify. |
| Dify ID | Identifier of the Dify bot to search for or modify; leave blank to search all (used in find, update, delete, fetch sessions, change status). |
| Dify URL | URL endpoint of the Dify API (required for create and update operations). |
| Dify API Key | API key credential for authenticating with the Dify bot API (required for create and update operations). |
| Trigger Type | Type of trigger to activate the bot: Keyword or All messages (for create and update). |
| Trigger Operator | How the trigger keyword is matched: Contains, Equals, Starts With, Ends With, Regex (only if Trigger Type is Keyword). |
| Trigger | The word, phrase, or regex pattern used as a trigger to start the Dify bot (required if Trigger Type is Keyword). |
| Expires In (Minutes) | Duration in minutes without responses after which the bot should be deactivated (create and update). |
| Keyword To Finish | Phrase used to close the bot session (create and update). |
| Default Message Delay (In Milliseconds) | Delay time in milliseconds before the bot sends a message (create and update). |
| Unknown Message | Message sent when input is not recognized (create and update). |
| Listen To Messages Sent By Me | Boolean indicating whether the bot listens to messages sent by the user themselves (create and update). |
| Pause The Bot When I Send A Message | Boolean indicating whether sending a message pauses the bot (create and update). |
| Keep The Bot Session Open | Boolean indicating whether to keep the bot session open indefinitely (create and update). |
| Wait Time (In Seconds) | Time to wait for additional messages to join into one after receiving a message (create and update). |
| Recipient Number | RemoteJid identifier of the recipient (used in change session status operation). |
| Status | Desired status of the session: Opened, Paused, Closed (used in change session status operation). |
Output
The node outputs JSON data representing the result of the selected operation. This typically includes:
- Details of created, updated, found, or deleted Dify bots.
- Lists or details of sessions fetched from Dify.
- Confirmation of session status changes.
The exact structure depends on the operation but generally reflects the API response from the Dify service.
No binary data output is indicated.
Dependencies
- Requires access to the Dify API via a valid URL and API key.
- The user must provide these credentials as input properties.
- No other external dependencies or environment variables are indicated.
Troubleshooting
- Invalid or missing API URL/API Key: Ensure the Dify URL and API key are correctly provided for create and update operations.
- Unsupported operation error: Selecting an operation not supported by the node will throw an error; verify the chosen operation matches the available options.
- Missing required fields: Required fields like "Instance Name," "Trigger," or "Recipient Number" must be filled depending on the operation.
- Session status change failures: Ensure the "RemoteJid" and "Status" values are correct and correspond to active sessions.
- Timeouts or connectivity issues: Verify network connectivity to the Dify API endpoint.
Links and References
- Dify Official Website (for general information about the Dify bot platform)
- Refer to the Dify API documentation (not provided here) for detailed API usage and authentication methods.