Help: How to Auto-recognize Custom Tools During DSL Project Import?

[YikaiHu]

Self Checks

• 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.

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

When we import custom tools from one Dify system and then import a DSL project that uses those tools, Dify fails to automatically recognize and link the custom tools within the imported project. This creates a broken workflow that requires manual intervention.

Current Workflow Issues

• Import custom tools from System A to System B ✅
• Import DSL project that uses those tools ❌ (Tools not recognized)
• Manually delete each tool node from the chatflow
• Manually re-integrate each tool back into the project
• Manually update all variables that reference the custom tools
• Only then does the project work properly

Impact on Users

• My customers are experiencing significant difficulties with project migration
• Time-consuming manual work that should be automated
• Risk of configuration errors during manual re-integration
• Poor user experience when moving between environments (dev/staging/production)
• Blocks efficient collaboration and project sharing between teams

Business Impact:

This limitation makes it difficult to:

• Share projects between different Dify installations
• Migrate from self-hosted to cloud or vice versa
• Collaborate across different organizations using Dify
• Maintain consistent development workflows

2. Additional context or comments

Expected Behavior:

When importing a DSL project, Dify should automatically detect and link custom tools that:

• Have the same tool name/identifier
• Are already available in the target system
• Match the tool specifications used in the project

Technical Details:

• Dify Version: 1.3.1
• Deployment: Self Hosted (Docker)
• This occurs even when tool calling names are identical between systems
• The tools themselves import successfully - the issue is with the DSL project recognition

[YikaiHu]

Same request as #10911

[YikaiHu]

Alternative Solution

If automatic recognition is not feasible in the short term, providing access to custom tool UUIDs in the UI would allow users to manually replace tool references in DSL files before import, which would be a significant improvement over the current workflow.

Currently, users can only obtain custom tool IDs by opening browser developer tools and searching through network requests, which is not a user-friendly experience.