Hello Railway Support Team,

I'm experiencing persistent issues with binary file handling in my n8n deployment hosted on your platform. Specifically, my workflows are unable to read or process binary files, which is preventing critical functionality like audio file transcription with OpenAI Whisper.

Error Details:

• When attempting to use HTTP Request nodes with binary file uploads, I receive errors like: "The item has no binary field '[object Object]'" or "Expected UploadFile, received: <class 'str'>"

• n8n appears unable to properly read or access binary data from the filesystem

• These operations work fine in local or other hosted environments, suggesting this is specific to the Railway deployment

Steps Already Taken:

• Verified my workflow configuration is correct

• Confirmed proper API credentials and parameters

• Attempted to use the built-in n8n nodes that handle binary files

Environment Information:

• n8n version: 1.86.0 (Self Hosted)

• Deployment platform: Railway.com

• Workflow involves: Processing audio files and sending them to OpenAI's Whisper API

I suspect this may be related to Railway's ephemeral filesystem, permission settings, or container configuration. Could you provide guidance on:

1. Recommended environment variable settings for n8n binary file processing on Railway

2. Proper volume configuration to ensure binary files can be read and processed

3. Any known limitations or recommended workarounds for binary file handling in your platform

Any assistance you can provide would be greatly appreciated, as this is blocking my workflow automation.

Thank you,