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

the Reverse Invocation for "Knowledge base interaction" at plugin development #12346

New Issue
Closed
opened 2026-02-21 19:07:00 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 19:07:00 -05:00
Owner
Copy Link
Copy Source

Originally created by @wangtao on GitHub (Mar 29, 2025).

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
  • 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.

Hello, I noticed that in the "Reverse Invocation" section of the plugin development introduction chapter in Dify's documentation, several aspects are listed.

plugin development introduction

Convenient Reverse Invocation

Plugins can now interact bidirectionally with Dify’s core functions, including:

AI model invokes
Tool usage
Application access
Knowledge base interaction
Function node calls

However, I couldn't find specific examples of "Knowledge base interaction" in the Reverse Invocation documentation, Reverse Invocation of the Dify Service nor did I find implementation code in the Dify codebase at core/plugin/backwards_invocation. I would like to inquire about the status of this feature - is it still pending on the development roadmap, or are there other case? The reason for asking is that I specifically need to implement a plugin to achieve more flexible knowledge management capabilities.

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 @wangtao on GitHub (Mar 29, 2025). ### Self Checks - [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 (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [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. Hello, I noticed that in the "Reverse Invocation" section of the plugin development introduction chapter in Dify's documentation, several aspects are listed. [plugin development introduction](https://docs.dify.ai/plugins/introduction) > Convenient Reverse Invocation > > Plugins can now interact bidirectionally with Dify’s core functions, including: > > AI model invokes > Tool usage > Application access > **Knowledge base interaction** > Function node calls However, I couldn't find specific examples of "Knowledge base interaction" in the Reverse Invocation documentation, [Reverse Invocation of the Dify Service](https://docs.dify.ai/plugins/schema-definition/reverse-invocation-of-the-dify-service) nor did I find implementation code in the Dify codebase at core/plugin/backwards_invocation. I would like to inquire about the status of this feature - is it still pending on the development roadmap, or are there other case? The reason for asking is that I specifically need to implement a plugin to achieve more flexible knowledge management capabilities. ### 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:07:00 -05:00
yindo closed this issue 2026-02-21 19:07:00 -05:00
yindo commented 2026-02-21 19:07:00 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 29, 2025):

@wangtao Hello there! I'm here to help you with bug fixes, answer your questions, and guide you on how to become a contributor. Let me know how I can assist you today.

The "Knowledge base interaction" is indeed mentioned as one of the capabilities that plugins can interact with bidirectionally in Dify’s core functions [1]. However, there are no specific examples or detailed documentation available in the Reverse Invocation framework regarding its implementation. The current status of this feature in the development roadmap is not explicitly documented, and there are no ongoing development branches or pull requests related to it that I could find.

For implementing "Knowledge base interaction" in Dify plugins, there are specific requirements and specifications you can follow. These include required fields like knowledge_id, query, and retrival_setting, as well as the expected response structure and HTTP response codes [2][3][4].

If you are looking to implement more flexible knowledge management capabilities, you might consider exploring the existing "Knowledge" component in Dify, which provides a user-friendly interface for managing knowledge and supports real-time updates and integration with external knowledge bases [5][6][7].

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Mar 29, 2025): <!-- Greeting --> @wangtao Hello there! I'm here to help you with bug fixes, answer your questions, and guide you on how to become a contributor. Let me know how I can assist you today. <!-- Answer --> The "Knowledge base interaction" is indeed mentioned as one of the capabilities that plugins can interact with bidirectionally in Dify’s core functions <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/en/plugins/introduction.md)</sup>. However, there are no specific examples or detailed documentation available in the Reverse Invocation framework regarding its implementation. The current status of this feature in the development roadmap is not explicitly documented, and there are no ongoing development branches or pull requests related to it that I could find. For implementing "Knowledge base interaction" in Dify plugins, there are specific requirements and specifications you can follow. These include required fields like `knowledge_id`, `query`, and `retrival_setting`, as well as the expected response structure and HTTP response codes <sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/en/.gitbook/assets/Dify-test.openapi.json)</sup><sup>[[3]](https://github.com/langgenius/dify/issues/15886)</sup><sup>[[4]](https://github.com/langgenius/dify-docs/blob/main/jp/.gitbook/assets/Dify-test.openapi.jp.json)</sup>. If you are looking to implement more flexible knowledge management capabilities, you might consider exploring the existing "Knowledge" component in Dify, which provides a user-friendly interface for managing knowledge and supports real-time updates and integration with external knowledge bases <sup>[[5]](https://github.com/langgenius/dify-docs/blob/main/en/guides/application-orchestrate/app-toolkits/README.md)</sup><sup>[[6]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/llms.txt)</sup><sup>[[7]](https://github.com/langgenius/dify-docs/blob/main/en/guides/knowledge-base/README.md)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/9b9003d9-0c4f-4c54-ae35-6b33aa333714?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/9b9003d9-0c4f-4c54-ae35-6b33aa333714?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/9b9003d9-0c4f-4c54-ae35-6b33aa333714?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/9b9003d9-0c4f-4c54-ae35-6b33aa333714?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/9b9003d9-0c4f-4c54-ae35-6b33aa333714?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/9b9003d9-0c4f-4c54-ae35-6b33aa333714?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/9b9003d9-0c4f-4c54-ae35-6b33aa333714?feedback_type=other)</sup>
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#12346
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?