Files in Script Tasks (Python Lambda)

Unmeshed Python script tasks ("Python Lambda") can read files that have been uploaded to the platform. These files are mounted inside the script at /app/files and match what you see under Manage Files in the UI. This is ideal for large inputs that should not be passed through workflow payloads.

The Manage Files view shows the same set of files available under /app/files in Python script tasks.

• Avoid large payload sizes and memory limits inside workflow steps.
• Share data across steps and workflows without re-sending large content.
• Keep workflow inputs lightweight while storing heavy assets separately.

• A remote worker generates a large file and needs a Python script to process it.
• You want to reuse a file across multiple steps or downstream workflows.
• You want to pass only a file name or key through the workflow, not the file itself.

1. A worker uploads a file to Unmeshed before its step completes.
2. The worker passes the file name/path to the next step.
3. A Python script task reads the file from /app/files/<file-name>.
4. Another step (or worker) can download the file if needed.
5. Files are retained by default; delete them when they are no longer needed.

Use unique file names or paths to avoid overwriting files.

Files are retained by default. If the file is no longer needed after your workflow finishes, delete it as part of a cleanup step to keep storage tidy.