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

[PR #7027] Provide output data also in json property of workflow tool (#6924) #25537

New Issue
Closed
opened 2026-02-21 20:25:08 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 20:25:08 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/langgenius/dify/pull/7027

State: closed
Merged: Yes

Checklist:

  • Please open an issue before creating a PR or link to an existing issue
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods

Description

This patch will change the output behaviour of workflow tools, so the output data of a workflow block will also be provided via json property. This simplifies further usage of this data, because you do not need to transform the stringified output data from text property to access certain properties of this data in following tools. This issue is described in more detail in
Close #6924.

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update, included: Dify Document
  • Improvement, including but not limited to code refactoring, performance optimization, and UI/UX improvement
  • Dependency upgrade

Testing Instructions

  • Create a simple workflow (A), which takes a text input and provides this as an output in the end
  • Create a second workflow (B), which takes a text input, passes this into workflow (A), receives the output of this embedded workflow and finally provides this data in the end
  • Expect: If you run the parent workflow (B), the json property in the end finally contains the output data from the emebedded workflow (A).
**Original Pull Request:** https://github.com/langgenius/dify/pull/7027 **State:** closed **Merged:** Yes --- # Checklist: - [x] Please open an issue before creating a PR or link to an existing issue - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [x] I ran `dev/reformat`(backend) and `cd web && npx lint-staged`(frontend) to appease the lint gods # Description This patch will change the output behaviour of workflow tools, so the output data of a workflow block will also be provided via `json` property. This simplifies further usage of this data, because you do not need to transform the stringified output data from `text` property to access certain properties of this data in following tools. This issue is described in more detail in Close #6924. ## Type of Change - [ ] Bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update, included: [Dify Document](https://github.com/langgenius/dify-docs) - [ ] Improvement, including but not limited to code refactoring, performance optimization, and UI/UX improvement - [ ] Dependency upgrade # Testing Instructions - [x] Create a simple workflow (A), which takes a text input and provides this as an output in the end - [x] Create a second workflow (B), which takes a text input, passes this into workflow (A), receives the output of this embedded workflow and finally provides this data in the end - [x] Expect: If you run the parent workflow (B), the `json` property in the end finally contains the output data from the emebedded workflow (A).
yindo added the pull-request label 2026-02-21 20:25:08 -05:00
yindo closed this issue 2026-02-21 20:25:08 -05:00
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 pull-request
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#25537
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?