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

workflow end node #13566

New Issue
Closed
opened 2026-02-21 19:12:47 -05:00 by yindo · 4 comments
yindo commented 2026-02-21 19:12:47 -05:00
Owner
Copy Link
Copy Source

Originally created by @wlxwlxwlx on GitHub (Apr 30, 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.

When I use the workflow, the end node adds an extra layer to my output result. As a result, when I convert the workflow into a tool, I have to use Python code to remove the outer layer in order to use my output result. Is it possible to add a direct reply node just like the multi-turn within the workflow?

For example, my result is: {"name":"xx","age":18}. After converting it into a tool, the result I get when I call the tool is: {"result":{"name":"xx","age":18}}

Image

Image

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 @wlxwlxwlx on GitHub (Apr 30, 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. When I use the workflow, the end node adds an extra layer to my output result. As a result, when I convert the workflow into a tool, I have to use Python code to remove the outer layer in order to use my output result. Is it possible to add a direct reply node just like the multi-turn within the workflow? For example, my result is: {"name":"xx","age":18}. After converting it into a tool, the result I get when I call the tool is: {"result":{"name":"xx","age":18}} ![Image](https://github.com/user-attachments/assets/c2dd3169-1dcf-44f0-819e-4ead61d96d6b) ![Image](https://github.com/user-attachments/assets/a3ea7c8d-c0b1-40f3-929d-aa0fa2053503) ### 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🌊 feat:workflow labels 2026-02-21 19:12:47 -05:00
yindo closed this issue 2026-02-21 19:12:47 -05:00
yindo commented 2026-02-21 19:12:47 -05:00
Author
Owner
Copy Link
Copy Source

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

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

Issue Summary:

  • You reported an issue with the workflow end node adding an unnecessary extra layer to the output.
  • This requires additional Python coding to remove the layer when converting the workflow into a tool.
  • You requested a feature enhancement for a direct reply node to streamline the process.
  • There have been no comments or developments on this issue yet.

Next Steps:

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

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (May 31, 2025): Hi, @wlxwlxwlx. 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 reported an issue with the workflow end node adding an unnecessary extra layer to the output. - This requires additional Python coding to remove the layer when converting the workflow into a tool. - You requested a feature enhancement for a direct reply node to streamline the process. - There have been no comments or developments on this issue yet. **Next Steps:** - Please let me know if this issue is still relevant to the latest version of the Dify repository by commenting here. - If there is no further activity, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
yindo commented 2026-02-21 19:12:47 -05:00
Author
Owner
Copy Link
Copy Source

@wlxwlxwlx commented on GitHub (Jun 4, 2025):

The latest version of Dify still lacks this feature.

@wlxwlxwlx commented on GitHub (Jun 4, 2025): The latest version of Dify still lacks this feature.
yindo commented 2026-02-21 19:12:47 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jun 4, 2025):

@crazywoola, the user @wlxwlxwlx has indicated that the latest version of Dify still lacks the feature related to the workflow end node. Could you please assist them with this issue?

@dosubot[bot] commented on GitHub (Jun 4, 2025): @crazywoola, the user @wlxwlxwlx has indicated that the latest version of Dify still lacks the feature related to the workflow end node. Could you please assist them with this issue?
yindo commented 2026-02-21 19:12:47 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jul 17, 2025):

In v1.6.0 you can publish chatflow as mcp tools which can solve your problem.

@crazywoola commented on GitHub (Jul 17, 2025): In v1.6.0 you can publish chatflow as mcp tools which can solve your problem.
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 🌊 feat:workflow 💪 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#13566
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?