Include 'custom' Type in Documentation for Input Files in Workflow App API and Advanced Chat App API

[yagiyuki]

Self Checks

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

Provide a description of requested docs changes

/workflows/run in the Workflow App API states that four types are supported as input file types.

dify/web/app/components/develop/template/template_workflow.en.mdx

Lines 58 to 62 in 94c7dcc

	- `type` (string) Supported type:
	- `document` ('TXT', 'MD', 'MARKDOWN', 'PDF', 'HTML', 'XLSX', 'XLS', 'DOCX', 'CSV', 'EML', 'MSG', 'PPTX', 'PPT', 'XML', 'EPUB')
	- `image` ('JPG', 'JPEG', 'PNG', 'GIF', 'WEBP', 'SVG')
	- `audio` ('MP3', 'M4A', 'WAV', 'WEBM', 'AMR')
	- `video` ('MP4', 'MOV', 'MPEG', 'MPGA')

However, in actually, there is a custom type specification.
However, there is an item called "Other file types" in the file type.

If you specify "Other file types", you need to specify custom for type when making an API request.
If you use anything other than "custom", the request will fail.

■ If type is specified other than custom

API_KEY="xxxx"

curl -X POST http://localhost/v1/workflows/run \
-H "Authorization: Bearer $API_KEY" \
-H "Content-Type: application/json" \
-d '{
  "inputs": {
    "doc": {
      "type": "document",
      "transfer_method": "remote_url",
      "url": "https://github.com/langgenius/dify/blob/main/README.md"
    }
  },
  "response_mode": "blocking",
  "user": "abc-123"
}'

{"code": "invalid_param", "message": "File validation failed for file: README.md", "status": 400}

■ If type is specified as custom

API_KEY="xxxx"

curl -X POST http://localhost/v1/workflows/run \
-H "Authorization: Bearer $API_KEY" \
-H "Content-Type: application/json" \
-d '{
  "inputs": {
    "doc": {
      "type": "custom",
      "transfer_method": "remote_url",
      "url": "https://github.com/langgenius/dify/blob/main/README.md"
    }
  },
  "response_mode": "blocking",
  "user": "abc-123"
}'

{"task_id": "2df5290f-17e5-4c0d-9f1f-9c1cbfaaca24", "workflow_run_id": "f0795bc8-60d7-47b5-a152-913ee19e5ace", "data": {"id": "f0795bc8-60d7-47b5-a152-913ee19e5ace", "workflow_id": "863edfa8-0f17-4c8f-9301-eae39a1f2a7e", "status": "succeeded", "outputs": {"result": "README.md"}, "error": null, "elapsed_time": 0.030771207995712757, "total_tokens": 0, "total_steps": 2, "created_at": 1734274941, "finished_at": 1734274941}}%

Currently, "custom" does not exist in the API specification as a type specification candidate, so I will add it.
The Advanced Chat App API's /chat-messages has a similar issue.