[FeatureRequest] Add a “Save to...” block, with the function to save the output files on SFTP or Clouds

[Emasoft]

Self Checks

• [X] I have searched for existing issues search for existing issues, including closed ones.
• [X] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• [X] Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Many times it is necessary for the user to manually copy and paste the output of a workflow using the result box. That is inadequate because: 1) it is inefficient and goes against the automation philosophy of the project, 2) manually extracting the output of a workflow is cumbersome and prone to errors, 3) the lack of a remote save option prevents the use of temp files in the workflow essentials for debug, 4) it prevents the option to auto-resume/retry a workflow without having to restart it from scratch and lose the progress, 5) it makes impossible to update files remotely and asynchronously using the workflow as a chron/timed automatic job that does not require user intervention.

The proposal id to add a “Save to...” block, with the function to save the output files on SFTP or Clouds remote services like:

• SFTP/SSH remote server (with automatic SSH key generation)
• Google Drive
• Microsoft One Drive
• DropBox
• Microsoft Azure
• AWS S3
• WebDAV
• Jottacloud (for European users)
• Tailscale (for sensible data)
• Yandex Drive
• GitHub (and with GitHub Action to update files based on a cron custom script)
• …and pretty much anything supported by https://rclone.org

It would be great if the user could add more than one service as a fallback in case one was temporarily unavailable.

2. Additional context or comments

Of course, a correspondent “Load from...” block would be also useful, since it would share the remotes configurations and would not require additional actions by the user.

3. Can you help us with this feature?

• [ ] I am interested in contributing to this feature.

[dosubot[bot]]

Hi, @Emasoft. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale.

Issue Summary

• Proposed feature: "Save to..." block for saving workflow outputs to remote services (SFTP, Google Drive, AWS S3).
• Suggested complementary feature: "Load from..." block for sharing remote configurations.
• Aimed at improving automation and minimizing manual errors.
• No comments or further activity since the issue was opened.

Next Steps

• Please confirm if this feature request is still relevant to the latest version of the Dify repository by commenting on this issue.
• If there is no further activity, the issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

[Emasoft]

Sorry for the late answer. Yes, this is still very relevant. Please implement this change. Thank you.

[dosubot[bot]]

@takatost, the user Emasoft has indicated that this issue is still very relevant and has requested the implementation of the change. Could you please assist them with this? Thank you!

[dosubot[bot]]

@takatost, the user Emasoft has indicated that this issue is still very relevant and has requested the implementation of the change. Could you please assist them with this? Thank you!

[crazywoola]

See https://marketplace.dify.ai/