Suggestion: Enhance File Processing Capabilities in Code Nodes

[CoquiLee]

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.

Issue Description

While Dify's workflow offers a file extractor component, its output quality and formatting often don't meet specific use case requirements. As a developer, I'd like to create custom file extraction and processing logic but face several limitations:

1. Code nodes cannot directly accept file-type parameters
2. Attempts to access file content via file.url return empty strings
3. There's no clear way to implement custom file processing logic for different formats (docx, xlsx, pdf, etc.)

Suggested Improvements

I would appreciate if Dify could enhance code nodes' file processing capabilities by:

1. Allowing code nodes to directly accept file-type parameters, or providing a standardized file object structure
2. Ensuring file.url attributes return valid file access links

This would greatly enhance Dify workflow flexibility, allowing developers to customize file processing logic based on specific business requirements rather than being limited to the built-in file extractor.

Thank you for considering this suggestion to improve Dify's development experience.

2. Additional context or comments

No response

3. Can you help us with this feature?

• I am interested in contributing to this feature.