langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-20 19:50:06 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Support cross-workflow copy and paste for nodes #19781

New Issue
Closed
opened 2026-02-21 20:03:56 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 20:03:56 -05:00
Owner
Copy Link
Copy Source

Originally created by @Halfknow on GitHub (Oct 21, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 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.

I frequently work with multiple workflows in Dify, and I often find myself needing to reuse similar node configurations across different workflows. Currently, when I want to replicate a node setup from one workflow to another, I have to manually recreate each node and reconfigure all its parameters from scratch.

For example, I was building a new customer service workflow and wanted to reuse a complex LLM node configuration (with specific prompts, model parameters, and output formatting) from my existing content generation workflow. Instead of being able to simply copy the node, I had to:

  1. Open the original workflow
  2. Screenshot or manually note down all the settings
  3. Switch to the new workflow
  4. Create a new LLM node
  5. Manually input all the same configurations again

This process is time-consuming, error-prone, and significantly slows down my workflow development process. It was frustrating because I knew the exact configuration I needed, but had no efficient way to transfer it between workflows.

2. Additional context or comments

Proposed Solution:
Add the ability to copy nodes (or groups of nodes) from one workflow and paste them into another workflow, similar to how we can currently copy-paste within the same workflow.

Suggested Implementation:

  • Right-click context menu option: "Copy node"
  • When switching to another workflow, option to "Paste node" that preserves all configurations
  • Support for copying multiple selected nodes at once
  • Maintain connections between copied nodes when pasting multiple nodes together

Benefits:

  • Dramatically improve workflow development efficiency
  • Reduce errors from manual reconfiguration
  • Enable better reusability of proven node configurations
  • Support workflow templating and best practices sharing

Alternative Approaches:

  • Node templates/library feature where commonly used configurations can be saved and reused
  • Workflow fragment export/import functionality

This feature would be particularly valuable for teams working on multiple similar workflows or for users who maintain different variations of workflows for different use cases.

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @Halfknow on GitHub (Oct 21, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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, otherwise it will be closed. - [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. I frequently work with multiple workflows in Dify, and I often find myself needing to reuse similar node configurations across different workflows. Currently, when I want to replicate a node setup from one workflow to another, I have to manually recreate each node and reconfigure all its parameters from scratch. For example, I was building a new customer service workflow and wanted to reuse a complex LLM node configuration (with specific prompts, model parameters, and output formatting) from my existing content generation workflow. Instead of being able to simply copy the node, I had to: 1. Open the original workflow 2. Screenshot or manually note down all the settings 3. Switch to the new workflow 4. Create a new LLM node 5. Manually input all the same configurations again This process is time-consuming, error-prone, and significantly slows down my workflow development process. It was frustrating because I knew the exact configuration I needed, but had no efficient way to transfer it between workflows. ### 2. Additional context or comments **Proposed Solution:** Add the ability to copy nodes (or groups of nodes) from one workflow and paste them into another workflow, similar to how we can currently copy-paste within the same workflow. **Suggested Implementation:** - Right-click context menu option: "Copy node" - When switching to another workflow, option to "Paste node" that preserves all configurations - Support for copying multiple selected nodes at once - Maintain connections between copied nodes when pasting multiple nodes together **Benefits:** - Dramatically improve workflow development efficiency - Reduce errors from manual reconfiguration - Enable better reusability of proven node configurations - Support workflow templating and best practices sharing **Alternative Approaches:** - Node templates/library feature where commonly used configurations can be saved and reused - Workflow fragment export/import functionality This feature would be particularly valuable for teams working on multiple similar workflows or for users who maintain different variations of workflows for different use cases. ### 3. Can you help us with this feature? - [x] I am interested in contributing to this feature.
yindo added the 💪 enhancement🌊 feat:workflow labels 2026-02-21 20:03:56 -05:00
yindo closed this issue 2026-02-21 20:03:56 -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 🌊 feat:workflow 💪 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#19781
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?