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

There is only text can be selected in the pre tool node #8441

New Issue
Closed
opened 2026-02-21 18:25:42 -05:00 by yindo · 4 comments
yindo commented 2026-02-21 18:25:42 -05:00
Owner
Copy Link
Copy Source

Originally created by @BigFaceBoy on GitHub (Feb 19, 2025).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • 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.

Dify version

1.0.0-beta.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

As the image shows below，there are two tool node in my workflow, but the seconde tool node can only select the text as its input, json and 'files' disappear!
Is there any config that I do not set?
Image

✔️ Expected Behavior

There are text 、'json' and files in the params.

❌ Actual Behavior

There is only text in the params.

Originally created by @BigFaceBoy on GitHub (Feb 19, 2025). ### Self Checks - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [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. ### Dify version 1.0.0-beta.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce As the image shows below，there are two tool node in my workflow, but the seconde tool node can only select the `text` as its input, `json` and 'files' disappear! Is there any config that I do not set? ![Image](https://github.com/user-attachments/assets/62578548-a129-4c7d-a7e1-38a3c64d4ea8) ### ✔️ Expected Behavior There are `text` 、'json' and `files` in the params. ### ❌ Actual Behavior There is only `text` in the params.
yindo added the 🐞 bug label 2026-02-21 18:25:42 -05:00
yindo closed this issue 2026-02-21 18:25:42 -05:00
yindo commented 2026-02-21 18:25:43 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 19, 2025):

The issue you're experiencing, where only text can be selected as an input type in the tool node, might be related to the configuration of input types in Dify. By default, Dify supports input types such as "text", "paragraph", "select", "number", "single file", and "file list" [1]. However, the availability of specific input types like json and files might depend on additional configuration or implementation within your workflow.

Here are a few things you can check or try:

  1. Tool Node Configuration: Ensure that the tool node is correctly configured to accept json and files as input types. This might involve setting up the tool parameters to handle these types explicitly.

  2. Workflow Node Settings: Verify that the workflow node settings allow for json and files as input types. This might require checking the node's input field configuration.

  3. Transformation Logic: If the input types are not directly supported, you might need to implement transformation logic to convert the input data into a compatible format. For example, using a Template node to convert JSON data into a string format before passing it to the tool node [2].

  4. Code Implementation: If you have access to the code, ensure that the _generate_parameters method or similar logic in your workflow supports the desired input types. The absence of specific handling for json and files might lead to their unavailability [3].

If these steps do not resolve the issue, it might be necessary to review the specific configurations or code related to your workflow to ensure compatibility with the desired input types.

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 (Feb 19, 2025): <!-- Answer --> The issue you're experiencing, where only `text` can be selected as an input type in the tool node, might be related to the configuration of input types in Dify. By default, Dify supports input types such as "text", "paragraph", "select", "number", "single file", and "file list" <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/en/guides/workflow/node/start.md)</sup>. However, the availability of specific input types like `json` and `files` might depend on additional configuration or implementation within your workflow. Here are a few things you can check or try: 1. **Tool Node Configuration**: Ensure that the tool node is correctly configured to accept `json` and `files` as input types. This might involve setting up the tool parameters to handle these types explicitly. 2. **Workflow Node Settings**: Verify that the workflow node settings allow for `json` and `files` as input types. This might require checking the node's input field configuration. 3. **Transformation Logic**: If the input types are not directly supported, you might need to implement transformation logic to convert the input data into a compatible format. For example, using a Template node to convert JSON data into a string format before passing it to the tool node <sup>[[2]](https://github.com/langgenius/dify/issues/13844)</sup>. 4. **Code Implementation**: If you have access to the code, ensure that the `_generate_parameters` method or similar logic in your workflow supports the desired input types. The absence of specific handling for `json` and `files` might lead to their unavailability <sup>[[3]](https://github.com/langgenius/dify/blob/main/api/core/workflow/nodes/tool/tool_node.py)</sup>. If these steps do not resolve the issue, it might be necessary to review the specific configurations or code related to your workflow to ensure compatibility with the desired input types. <!-- 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/9e9f1c4d-6839-4d84-a2da-bfbb0c9fdbe4?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/9e9f1c4d-6839-4d84-a2da-bfbb0c9fdbe4?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/9e9f1c4d-6839-4d84-a2da-bfbb0c9fdbe4?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/9e9f1c4d-6839-4d84-a2da-bfbb0c9fdbe4?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/9e9f1c4d-6839-4d84-a2da-bfbb0c9fdbe4?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/9e9f1c4d-6839-4d84-a2da-bfbb0c9fdbe4?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/9e9f1c4d-6839-4d84-a2da-bfbb0c9fdbe4?feedback_type=other)</sup>
yindo commented 2026-02-21 18:25:43 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Feb 19, 2025):

No, we just haven't support it yet. You can use template node to transform those into string.

@crazywoola commented on GitHub (Feb 19, 2025): No, we just haven't support it yet. You can use template node to transform those into string.
yindo commented 2026-02-21 18:25:43 -05:00
Author
Owner
Copy Link
Copy Source

@BigFaceBoy commented on GitHub (Feb 19, 2025):

@

No, we just haven't support it yet. You can use template node to transform those into string.

@crazywoola Dose it mean that each tool should return text result?

@BigFaceBoy commented on GitHub (Feb 19, 2025): @ > No, we just haven't support it yet. You can use template node to transform those into string. @crazywoola Dose it mean that each tool should return `text` result?
yindo commented 2026-02-21 18:25:43 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Feb 20, 2025):

@

No, we just haven't support it yet. You can use template node to transform those into string.

@crazywoola Dose it mean that each tool should return text result?

Nope, it depends, some tools will return json while some will return both of json and text.

@crazywoola commented on GitHub (Feb 20, 2025): > @ > > > No, we just haven't support it yet. You can use template node to transform those into string. > > [@crazywoola](https://github.com/crazywoola) Dose it mean that each tool should return `text` result? Nope, it depends, some tools will return json while some will return both of json and text.
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 🐞 bug
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#8441
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?