Actions114
- Instance Actions
- Message Actions
- Group Actions
- Chat Actions
- Profile Actions
- Event Actions
- Integration Actions
- Call Actions
- Label Actions
- OpenAI Actions
- N8N Integration Actions
- EvoAI Actions
- Template Actions
- Business Actions
Integration → Dify
AI-generatedOverview
This node interacts with the Dify integration within the Evolution API, allowing users to perform various operations such as creating, checking, updating, deleting Dify instances, managing sessions, and changing session statuses. It is useful for automating and managing chatbot or bot-related workflows in applications that use Dify as a service.
Use Case Examples
- Creating a new Dify bot instance with specific triggers and settings.
- Checking the status or details of an existing Dify bot by its ID.
- Updating the configuration of a Dify bot, including triggers, messages, and session settings.
- Deleting a Dify bot instance by ID to clean up resources or stop the bot from running further sessions.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the Dify instance that will send the message, required for identification. |
| What Do You Want To Do | The specific operation to perform with the Dify integration, such as create, find, update, delete, fetch sessions, or change session status. |
| Dify ID | The identifier of the Dify bot to search for or modify; optional for some operations. |
| Dify URL | The URL endpoint for the Dify API, required for creating or updating bots. |
| Dify ApiKey | The API key for authenticating with the Dify bot API, required for creating or updating bots. |
| Trigger Type | The type of trigger to activate the bot, such as keyword or all messages. |
| Trigger Operator | The operator to match the trigger keyword, e.g., contains, equals, starts with, ends with, regex. |
| Trigger | The word, phrase, or regex pattern used as the trigger to start the Dify bot. |
| Expires In (Minutes) | The duration in minutes after which the bot deactivates if no responses are received. |
| Finish Keyword | The word or phrase used to close the bot session. |
| Default Message Delay (In Milliseconds) | The delay in milliseconds before the bot sends a message. |
| Unknown Message | The 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 themselves. |
| Pause The Bot When I Send A Message | Whether the bot pauses when the user sends a message. |
| Keep The Bot Session Open | Whether to keep the bot session open continuously. |
| Wait Time (In Seconds) | The debounce time in seconds to wait for additional messages before merging them. |
| Recipient Number | The remoteJid identifier of the recipient, required for changing session status. |
| Status | The session status to set, such as opened, paused, or closed. |
Output
JSON
result- The JSON response from the Dify API operation performed, containing details or status of the requested action.
Dependencies
- Requires Evolution API credentials for authentication and access to the Dify integration endpoints.
Troubleshooting
- Ensure that the Dify URL and API key are correctly entered and valid to avoid authentication errors.
- Verify that the Dify ID is provided when required for operations like find, update, delete, fetch sessions, or change status.
- Check that required fields such as instance name, trigger values, and session settings are properly configured to prevent operation failures.
- Common errors may include unsupported operations if the selected action is not implemented, or network errors if the API endpoint is unreachable.