langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-22 04:25:29 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Add an option to the knowledge retrieval node in the dify workflow: select the knowledge base variable to achieve flexible configuration of the knowledge base #15872

New Issue
Closed
opened 2026-02-21 19:23:46 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 19:23:46 -05:00
Owner
Copy Link
Copy Source

Originally created by @Kevin0888 on GitHub (Aug 4, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

requirement specification
The knowledge retrieval node in dify's workflow, selecting and configuring the knowledge base, can add a feature selection option: selecting knowledge base variables. This allows for flexible configuration of the knowledge base.
When I call the workflow API, I pass a knowledge base variable from my own web page to the API, and then select this variable in the workflow to achieve the effect of dynamically passing in the knowledge base variable or parameter (knowledge base ID). Then, the knowledge search node of the workflow can match the knowledge base against this variable.

Requirement purpose
I have this requirement: users want to set up different types of knowledge bases (personal and public), so that there will be many knowledge bases. If I follow the current logic, I need to set up many processes in the workflow to choose different knowledge bases, which is very cumbersome.
If knowledge base variables can be selected in the knowledge retrieval node of the workflow, then only one process is needed to complete it.

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @Kevin0888 on GitHub (Aug 4, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. requirement specification The knowledge retrieval node in dify's workflow, selecting and configuring the knowledge base, can add a feature selection option: selecting knowledge base variables. This allows for flexible configuration of the knowledge base. When I call the workflow API, I pass a knowledge base variable from my own web page to the API, and then select this variable in the workflow to achieve the effect of dynamically passing in the knowledge base variable or parameter (knowledge base ID). Then, the knowledge search node of the workflow can match the knowledge base against this variable. Requirement purpose I have this requirement: users want to set up different types of knowledge bases (personal and public), so that there will be many knowledge bases. If I follow the current logic, I need to set up many processes in the workflow to choose different knowledge bases, which is very cumbersome. If knowledge base variables can be selected in the knowledge retrieval node of the workflow, then only one process is needed to complete it. ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 19:23:46 -05:00
yindo closed this issue 2026-02-21 19:23:46 -05:00
yindo commented 2026-02-21 19:23:47 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Aug 4, 2025):

@crazywoola commented on GitHub (Aug 4, 2025): - https://marketplace.dify.ai/plugins/kurokobo/knowledge_toolbox I think you can try something like this.
yindo commented 2026-02-21 19:23:47 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 5, 2025):

Hi, @Kevin0888. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You requested a feature to dynamically select knowledge base variables in the knowledge retrieval node.
  • This would allow passing variables via the workflow API, reducing the need for multiple workflows.
  • The goal is to simplify managing personal and public knowledge bases.
  • A community member suggested trying the "knowledge_toolbox" plugin from the Dify marketplace as a possible workaround.
  • No further updates or maintainer feedback have been provided since.

Next Steps:

  • Please let me know if this feature request is still relevant to the latest version of Dify by commenting on this issue.
  • If I don’t hear back within 15 days, the issue will be automatically closed.

Thanks for your understanding and contribution!

@dosubot[bot] commented on GitHub (Sep 5, 2025): Hi, @Kevin0888. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You requested a feature to dynamically select knowledge base variables in the knowledge retrieval node. - This would allow passing variables via the workflow API, reducing the need for multiple workflows. - The goal is to simplify managing personal and public knowledge bases. - A community member suggested trying the "knowledge_toolbox" plugin from the Dify marketplace as a possible workaround. - No further updates or maintainer feedback have been provided since. **Next Steps:** - Please let me know if this feature request is still relevant to the latest version of Dify by commenting on this issue. - If I don’t hear back within 15 days, the issue will be automatically closed. Thanks for your understanding and contribution!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 💪 enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#15872
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?