langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-22 12:36:14 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Introduce the URL link obtained in the workflow into the LLM node #12365

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

Originally created by @chick26 on GitHub (Mar 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 report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
  • Please do not modify this template :) and fill in all the required fields.

Provide a description of requested docs changes

Image
I have a set of documents in PDF format that need to be converted into images before being fed into the multimodal LLM model node. However, the LLM node currently only accepts file-type variables from the "Start" node or the "HTTP" node. How can this issue be resolved? (I have already defined a local HTTP interface for file type conversion.)

Originally created by @chick26 on GitHub (Mar 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 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. ### Provide a description of requested docs changes ![Image](https://github.com/user-attachments/assets/af6ce725-71c3-4b81-a179-83f077c9122c) I have a set of documents in PDF format that need to be converted into images before being fed into the multimodal LLM model node. However, the LLM node currently only accepts file-type variables from the "Start" node or the "HTTP" node. How can this issue be resolved? (I have already defined a local HTTP interface for file type conversion.)
yindo closed this issue 2026-02-21 19:07:05 -05:00
yindo commented 2026-02-21 19:07:05 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 30, 2025):

Hello @chick26! I'm here to help you with any bugs, questions, or contributions you have. Let's work together to resolve the issue you're facing.

To address the issue of introducing a URL link obtained in the workflow into the LLM node, you need to ensure that the data is in a string format, as LLM nodes in Dify's workflow only support string-type variables [1]. Here are some steps you can follow:

  1. Convert File to URL: Since you have a local HTTP interface for file type conversion, ensure that the output of this conversion is a URL link to the converted image.

  2. Pass URL as String: Once you have the URL, you can pass it as a string to the LLM node. This involves ensuring that the URL is properly formatted as a string variable in your workflow.

  3. Use HTTP Node: If the URL is obtained from an HTTP node, ensure that the response is correctly mapped to a string variable that can be used by the LLM node.

  4. Check Node Compatibility: Make sure that the nodes in your workflow are compatible with handling string-type variables, especially when transitioning from file-type to string-type data.

If you encounter any issues with mapping the output from the HTTP node to the LLM node, you might find it helpful to refer to similar discussions, such as the one on mapping HTTP output files to a CODE execution node [2].

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 (Mar 30, 2025): <!-- Greeting --> Hello @chick26! I'm here to help you with any bugs, questions, or contributions you have. Let's work together to resolve the issue you're facing. <!-- Answer --> To address the issue of introducing a URL link obtained in the workflow into the LLM node, you need to ensure that the data is in a string format, as LLM nodes in Dify's workflow only support string-type variables <sup>[[1]](https://github.com/langgenius/dify/issues/16202)</sup>. Here are some steps you can follow: 1. **Convert File to URL**: Since you have a local HTTP interface for file type conversion, ensure that the output of this conversion is a URL link to the converted image. 2. **Pass URL as String**: Once you have the URL, you can pass it as a string to the LLM node. This involves ensuring that the URL is properly formatted as a string variable in your workflow. 3. **Use HTTP Node**: If the URL is obtained from an HTTP node, ensure that the response is correctly mapped to a string variable that can be used by the LLM node. 4. **Check Node Compatibility**: Make sure that the nodes in your workflow are compatible with handling string-type variables, especially when transitioning from file-type to string-type data. If you encounter any issues with mapping the output from the HTTP node to the LLM node, you might find it helpful to refer to similar discussions, such as the one on mapping HTTP output files to a CODE execution node <sup>[[2]](https://github.com/langgenius/dify/discussions/15915)</sup>. <!-- 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/effd4f69-d656-4b0b-b554-88769d86d171?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/effd4f69-d656-4b0b-b554-88769d86d171?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/effd4f69-d656-4b0b-b554-88769d86d171?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/effd4f69-d656-4b0b-b554-88769d86d171?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/effd4f69-d656-4b0b-b554-88769d86d171?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/effd4f69-d656-4b0b-b554-88769d86d171?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/effd4f69-d656-4b0b-b554-88769d86d171?feedback_type=other)</sup>
yindo commented 2026-02-21 19:07:05 -05:00
Author
Owner
Copy Link
Copy Source

@TylerSun-lab commented on GitHub (Mar 31, 2025):

To use the visual model of llm, you must specify Array[File] in llm. How do you implement the output variable files Array[File] in the http request module?

@TylerSun-lab commented on GitHub (Mar 31, 2025): To use the visual model of llm, you must specify Array[File] in llm. How do you implement the output variable files Array[File] in the http request module?
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
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#12365
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?