langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-21 17:45:23 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

I want to be able to select json directly as output in the "NextCloud" plugin #369

New Issue
Closed
opened 2026-02-16 10:19:09 -05:00 by yindo · 6 comments
yindo commented 2026-02-16 10:19:09 -05:00
Owner
Copy Link
Copy Source

Originally created by @hiro-gj on GitHub (Jun 14, 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 Dify issues & Dify Official Plugins, 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.1.3 -> 1.5.1

Plugin version

0.0.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I want to display the "json" results of the search output using the "NextCloud plugin". #20939
https://github.com/langgenius/dify/discussions/20939#discussion-8444614

✔️ Error log

https://github.com/langgenius/dify/discussions/20939#discussioncomment-13471828 by kurokobo

I think the data type just doesn't match.

  • The text output from the tool is of type String, and the json is of type Array[Object].
  • The answer node can accept String types, but not Array[Object} types.
  • As a workaround, one idea is to use a Template node, although I haven't tested it with the NextCloud plugin. You should be able to convert the Array[Object} type to a String type.
Originally created by @hiro-gj on GitHub (Jun 14, 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 [Dify issues](https://github.com/langgenius/dify/issues) & [Dify Official Plugins](https://github.com/langgenius/dify-official-plugins/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.1.3~ -> 1.5.1 ### Plugin version 0.0.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce I want to display the "json" results of the search output using the "NextCloud plugin". #20939 https://github.com/langgenius/dify/discussions/20939#discussion-8444614 ### ✔️ Error log https://github.com/langgenius/dify/discussions/20939#discussioncomment-13471828 by kurokobo > I think the data type just doesn't match. > > - The text output from the tool is of type String, and the json is of type Array[Object]. > - The answer node can accept String types, but not Array[Object} types. > - As a workaround, one idea is to use a Template node, although I haven't tested it with the NextCloud plugin. You should be able to convert the Array[Object} type to a String type.
yindo added the bug label 2026-02-16 10:19:09 -05:00
yindo closed this issue 2026-02-16 10:19:09 -05:00
yindo commented 2026-02-16 10:19:09 -05:00
Author
Owner
Copy Link
Copy Source

@hiro-gj commented on GitHub (Jun 14, 2025):

https://github.com/langgenius/dify/discussions/20939#discussioncomment-13471839

  • As a workaround, one idea is to use a Template node, although I haven't tested it with the NextCloud plugin. You should be able to convert the Array[Object} type to a String type.

@kurokobo Thank you very much!
By using a template, I was able to select output[String] at the next node, and the problem was solved!

@hiro-gj commented on GitHub (Jun 14, 2025): https://github.com/langgenius/dify/discussions/20939#discussioncomment-13471839 >> - As a workaround, one idea is to use a Template node, although I haven't tested it with the NextCloud plugin. You should be able to convert the Array[Object} type to a String type. >> > @kurokobo Thank you very much! By using a template, I was able to select `output[String]` at the next node, and the problem was solved!
yindo commented 2026-02-16 10:19:09 -05:00
Author
Owner
Copy Link
Copy Source

@hiro-gj commented on GitHub (Jul 8, 2025):

In NextCloud 0.0.1, it seems necessary to convert from json Array (Object) to Output (Strings) in the template before inputting it to the LLM node...

Image

I was trying it out because I could specify NextCloud's json Array (Object) in the LLM context...

  • (1) When the json Array (Object) of NextCloud (Search Files) is converted to the template Output (Strings) and then made into the LLM context. -> Succeeds.
    Image

  • (2) When the directly set the json Array (Object) of NextCloud (Search Files) to the LLM context. -> fail.

Image

(by search_files_0.0.1a.py)

Run failed: Invalid context structure: {'max_results': 50, 'results': [{'name': 'テスト3.md', 'path': 'テスト3.md', 'type': 'file'}], 'search_path': '/test1/*', 'search_pattern': '*テスト*.*', 'total_found': 1}
@hiro-gj commented on GitHub (Jul 8, 2025): ## In NextCloud 0.0.1, it seems necessary to convert from json Array (Object) to Output (Strings) in the template before inputting it to the LLM node... <img width="30%" alt="Image" src="https://github.com/user-attachments/assets/24ca835f-08a6-4865-8054-19c54e8bd3a1" /> ### I was trying it out because I could specify NextCloud's json Array (Object) in the LLM context... - (1) When the json Array (Object) of NextCloud (Search Files) is converted to the template Output (Strings) and then made into the LLM context. -> Succeeds. <img width="2113" height="945" alt="Image" src="https://github.com/user-attachments/assets/65c83823-4c74-4b6e-a93c-30be3e55f92e" /> - (2) When the directly set the json Array (Object) of NextCloud (Search Files) to the LLM context. -> fail. <img width="2113" height="945" alt="Image" src="https://github.com/user-attachments/assets/50edb614-d375-4e2c-b740-1e601ea1aeef" /> (by [search_files_0.0.1a.py](https://github.com/langgenius/dify-official-plugins/issues/1092#issuecomment-3047472435)) ``` Run failed: Invalid context structure: {'max_results': 50, 'results': [{'name': 'テスト3.md', 'path': 'テスト3.md', 'type': 'file'}], 'search_path': '/test1/*', 'search_pattern': '*テスト*.*', 'total_found': 1} ```
yindo commented 2026-02-16 10:19:09 -05:00
Author
Owner
Copy Link
Copy Source

@hiro-gj commented on GitHub (Jul 9, 2025):

@langgenius Specific proposed fix:
Is it possible to add a json Array [strings] to the output of the NextCloud plugin,
In addition to the current json Array [Object] ?

@hiro-gj commented on GitHub (Jul 9, 2025): @langgenius Specific proposed fix: Is it possible to add a` json Array [strings]` to the output of the NextCloud plugin, In addition to the current ` json Array [Object]` ?
yindo commented 2026-02-16 10:19:09 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 20, 2025):

Hi, @hiro-gj. I'm Dosu (https://dosu.dev), and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.

Issue Summary

  • You requested the NextCloud plugin to support JSON arrays or objects as output types, beyond just strings.
  • Currently, only string outputs are accepted, causing errors when directly passing JSON arrays to the LLM context.
  • You found a workaround by converting JSON arrays to strings using a Template node, which works but is not ideal.
  • The core limitation is the plugin's lack of support for JSON Array [strings] output type.
  • The issue remains unresolved and open for potential enhancement.

What's Next

  • Please let me know if this issue is still relevant with the latest version of the dify-official-plugins repository by commenting here.
  • If I do not hear back within 5 days, I will automatically close this issue.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Aug 20, 2025): Hi, @hiro-gj. I'm Dosu (https://dosu.dev), and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale. **Issue Summary** - You requested the NextCloud plugin to support JSON arrays or objects as output types, beyond just strings. - Currently, only string outputs are accepted, causing errors when directly passing JSON arrays to the LLM context. - You found a workaround by converting JSON arrays to strings using a Template node, which works but is not ideal. - The core limitation is the plugin's lack of support for JSON Array [strings] output type. - The issue remains unresolved and open for potential enhancement. **What's Next** - Please let me know if this issue is still relevant with the latest version of the dify-official-plugins repository by commenting here. - If I do not hear back within 5 days, I will automatically close this issue. Thank you for your understanding and contribution!
yindo commented 2026-02-16 10:19:09 -05:00
Author
Owner
Copy Link
Copy Source

@hiro-gj commented on GitHub (Aug 23, 2025):

@dosu
The latest version of the NextCloud plugin is 0.1.0, which PR #1377 has been merged.
However, the #1091 has not been addressed and remains an issue.
(This screenshot is from v0.1.0)
Image

@hiro-gj commented on GitHub (Aug 23, 2025): @dosu The latest version of the NextCloud plugin is [0.1.0](https://marketplace.dify.ai/plugins/langgenius/nextcloud), which PR #1377 has been merged. However, the #1091 has not been addressed and remains an issue. (This screenshot is from v0.1.0) <img width="295" height="88" alt="Image" src="https://github.com/user-attachments/assets/b4a21bc4-18f1-4937-9188-eda75b041f4e" />
yindo commented 2026-02-16 10:19:09 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 23, 2025):

@crazywoola The user @hiro-gj confirms that the issue with JSON array output in the NextCloud plugin remains unresolved in version 0.1.0 despite PR #1377 being merged, and has provided a screenshot for reference. Could you please assist with this?

@dosubot[bot] commented on GitHub (Aug 23, 2025): @crazywoola The user @hiro-gj confirms that the issue with JSON array output in the NextCloud plugin remains unresolved in version 0.1.0 despite PR #1377 being merged, and has provided a screenshot for reference. Could you please assist with this?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
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-official-plugins#369
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?