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

Enable JSON Output Option for LLM Node #2653

New Issue
Closed
opened 2026-02-21 17:48:24 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 17:48:24 -05:00
Owner
Copy Link
Copy Source

Originally created by @jicasada on GitHub (Apr 25, 2024).

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).
  • Pleas do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing?

Yes, this request stems from a specific challenge we have encountered in our current workflow. When utilizing the LLM node, all output data is produced as stringified JSON, which requires additional parsing when integrating with other systems that expect raw JSON format.

2. Describe the feature you'd like to see

I would like to see an enhancement to the LLM node that allows it to output data directly as raw JSON objects, rather than stringified JSON. This feature should include a configurable option within the node's custom properties where users can choose the format of the output—either as a stringified JSON text or as a raw JSON object.

3. How will this feature improve your workflow or experience?

Reduced Complexity: By eliminating the need to parse stringified JSON, we can streamline our data processing tasks. This reduction in complexity speeds up the integration with other systems and reduces the workload on developers who no longer need to write and maintain parsing code.

4. Additional context or comments

image
This function becomes irrelevant if the output is always in text format.

5. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @jicasada on GitHub (Apr 25, 2024). ### 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] Pleas do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Yes, this request stems from a specific challenge we have encountered in our current workflow. When utilizing the LLM node, all output data is produced as stringified JSON, which requires additional parsing when integrating with other systems that expect raw JSON format. ### 2. Describe the feature you'd like to see I would like to see an enhancement to the LLM node that allows it to output data directly as raw JSON objects, rather than stringified JSON. This feature should include a configurable option within the node's custom properties where users can choose the format of the output—either as a stringified JSON text or as a raw JSON object. ### 3. How will this feature improve your workflow or experience? Reduced Complexity: By eliminating the need to parse stringified JSON, we can streamline our data processing tasks. This reduction in complexity speeds up the integration with other systems and reduces the workload on developers who no longer need to write and maintain parsing code. ### 4. Additional context or comments ![image](https://github.com/langgenius/dify/assets/6273003/87bf12f0-8e9d-4800-a463-e9d79b4a7cd6) This function becomes irrelevant if the output is always in text format. ### 5. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 17:48:24 -05:00
yindo closed this issue 2026-02-21 17:48:25 -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 💪 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#2653
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?