langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-08-27 03:01:54 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Can event driven nodes be added #13004

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

Originally created by @wanghonglin-for on GitHub (Apr 16, 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.

I'm glad to use dify. Currently, I have a scenario where I want to add a human intervention (or event driven) node at a certain node or any node between the start and end nodes. For example, I want to manually intervene and check if the execution result meets expectations after the second node is completed. If it does not meet expectations, the human will modify the result and continue to execute the next node after modification (calling the event driven node to continue executing the next node). Can this feature be developed? Looking forward to your reply. Thank you very much.

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 @wanghonglin-for on GitHub (Apr 16, 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. I'm glad to use dify. Currently, I have a scenario where I want to add a human intervention (or event driven) node at a certain node or any node between the start and end nodes. For example, I want to manually intervene and check if the execution result meets expectations after the second node is completed. If it does not meet expectations, the human will modify the result and continue to execute the next node after modification (calling the event driven node to continue executing the next node). Can this feature be developed? Looking forward to your reply. Thank you very much. ### 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:10:07 -05:00
yindo closed this issue 2026-02-21 19:10:07 -05:00
yindo commented 2026-02-21 19:10:07 -05:00
Author
Owner
Copy Link
Copy Source

@Yevanchen commented on GitHub (Apr 16, 2025):

We are interested in the planning

@Yevanchen commented on GitHub (Apr 16, 2025): We are interested in the planning
yindo commented 2026-02-21 19:10:07 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (May 17, 2025):

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

Issue Summary:

  • You requested a feature for event-driven nodes in Dify.
  • The feature would allow human intervention and manual checks during processes.
  • You want the ability to modify execution results before proceeding.
  • Yevanchen has shown interest in planning this feature.

Next Steps:

  • Please let us know if this feature request is still relevant to the latest version of Dify by commenting here.
  • If there is no further activity, the issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (May 17, 2025): Hi, @wanghonglin-for. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog. I'm marking this issue as stale. **Issue Summary:** - You requested a feature for event-driven nodes in Dify. - The feature would allow human intervention and manual checks during processes. - You want the ability to modify execution results before proceeding. - Yevanchen has shown interest in planning this feature. **Next Steps:** - Please let us know if this feature request is still relevant to the latest version of Dify by commenting here. - If there is no further activity, the issue will be automatically closed in 15 days. Thank you 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#13004
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?