[GH-ISSUE #14114] feat: Want to add support for native dify instead of relying on custom scripts #32675

New Issue

GiteaMirror · 2026-04-25T06:34:33-05:00

GiteaMirror commented

2026-04-25 06:34:33 -05:00

Originally created by @Mi0uno on GitHub (May 21, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/14114

Check Existing Issues

I have searched the existing issues and discussions.

Problem Description

Open WebUI currently does not natively support Dify’s Chatflows and Agent APIs, which limits its ability to serve as a frontend for more intelligent, multi-turn, and tool-enhanced conversations. Without this integration, users cannot take advantage of Dify’s dynamic message routing, tool calling, memory, and plugin system from within the Open WebUI interface.

Desired Solution you'd like

Agent Chat Integration
Add a setting to enter Dify’s API_KEY and API_BASE_URL.

Allow users to select a Dify Agent from a list fetched via the /v1/agents API.

Enable chat messages to be sent to POST /v1/agents/message, and display the agent's full response including tool outputs, thoughts, or citations.

Chatflow Support
Let users connect to specific Dify Chatflows via POST /v1/chat-messages with proper App ID.

Add support for chat history, user input, variable inputs, and plugin tool responses as defined in Chatflow configurations.

Optionally support file uploads if the selected chatflow supports them.

Interface Enhancements
Automatically switch interface modes between base LLM chat, agent chat, and chatflow chat.

Show agent or flow name, and optionally any real-time actions taken (tools, plugins used, etc.).

Use Open WebUI’s excellent UI to present multi-modal or tool-based replies in a clean way.

Alternatives Considered

Manually using Open WebUI’s custom API mode to route messages to Dify agents.
Downsides: Requires technical knowledge, lacks UI binding, no history/thread support.

Using Dify's own web UI.
Downsides: Limited customization, some users prefer the Open WebUI frontend for its local and extensible nature.

Additional Context

Dify Docs: https://docs.dify.ai

Relevant APIs:

POST /v1/agents/message

POST /v1/chat-messages

This feature would turn Open WebUI into a universal frontend for both open-source LLMs and enterprise-grade Dify deployments, enabling power users to orchestrate intelligent agents and dynamic chatflows in a familiar interface.

Originally created by @Mi0uno on GitHub (May 21, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/14114 ### Check Existing Issues - [x] I have searched the existing issues and discussions. ### Problem Description Open WebUI currently does not natively support Dify’s Chatflows and Agent APIs, which limits its ability to serve as a frontend for more intelligent, multi-turn, and tool-enhanced conversations. Without this integration, users cannot take advantage of Dify’s dynamic message routing, tool calling, memory, and plugin system from within the Open WebUI interface. ### Desired Solution you'd like 1. Agent Chat Integration Add a setting to enter Dify’s API_KEY and API_BASE_URL. Allow users to select a Dify Agent from a list fetched via the /v1/agents API. Enable chat messages to be sent to POST /v1/agents/message, and display the agent's full response including tool outputs, thoughts, or citations. 2. Chatflow Support Let users connect to specific Dify Chatflows via POST /v1/chat-messages with proper App ID. Add support for chat history, user input, variable inputs, and plugin tool responses as defined in Chatflow configurations. Optionally support file uploads if the selected chatflow supports them. 3. Interface Enhancements Automatically switch interface modes between base LLM chat, agent chat, and chatflow chat. Show agent or flow name, and optionally any real-time actions taken (tools, plugins used, etc.). Use Open WebUI’s excellent UI to present multi-modal or tool-based replies in a clean way. ### Alternatives Considered Manually using Open WebUI’s custom API mode to route messages to Dify agents. Downsides: Requires technical knowledge, lacks UI binding, no history/thread support. Using Dify's own web UI. Downsides: Limited customization, some users prefer the Open WebUI frontend for its local and extensible nature. ### Additional Context Dify Docs: https://docs.dify.ai Relevant APIs: POST /v1/agents/message POST /v1/chat-messages This feature would turn Open WebUI into a universal frontend for both open-source LLMs and enterprise-grade Dify deployments, enabling power users to orchestrate intelligent agents and dynamic chatflows in a familiar interface.

GiteaMirror closed this issue

2026-04-25 06:34:34 -05:00

GiteaMirror commented

2026-04-25 06:34:34 -05:00

@tjbck commented on GitHub (May 21, 2025):

You should use Functions.

@tjbck commented on GitHub (May 21, 2025): You should use Functions.

GiteaMirror commented

2026-04-25 06:34:34 -05:00

@Mi0uno commented on GitHub (May 21, 2025):

The use of functions is not particularly convenient

@Mi0uno commented on GitHub (May 21, 2025): The use of functions is not particularly convenient