Can we get a folder added to workflows named 'Output' (in the root folder as well as one for any sub folders created)?
personally, I'd like to use an Output folder for generating documentation files which would also need integration of something like pdoc or apiDoc.
I could also see it used as a way to generate files in one workflow, then consume them in another (essentially using the Output folder as per-run temp storage).... This would also cut down on the amount of data we would need to send between workflows and it'd lower the average size of data returned by workflows, since we now don't have to return anything we can just make a file then later on choose if we need it or not by adding a workflow named like 'Get Output Files' so we can bubble up the files to our UI, letting us do things like have an AI generate md files for our UI to consume, generate images without having to store them in-memory, split files without ending up with essentially 2 copies of the original + file overhead in memory (the original + all the splits = 2 * original + overhead).
To help manage space used on the server 'Output' folders could be cleared before each run (only for the Output folder in the same 'directory' as the workflow being ran.... this would let other workflows in different folders to process/validate/manage the output of one workflow before using it or passing it on).
your_org.retool.com/workflows/
├─ Output/
│ ├─ workflows_docs.md
│ └─ last_run_from_root_folder_log.txt
├─ Agentic Workflows/
│ ├─ Output/
│ │ ├─ agentic_workflows_docs.md
│ │ └─ last_run_from_agentic_workflows_folder_log.txt
│ └─ Agentic 1.workflow
├─ FrontEnd Workflows/
│ ├─ Output/
│ │ └─ last_run_from_frontend_workflows_folder_log.txt
│ ├─ Get Files By User ID.workflow
│ └─ Generate Avatar.workflow
├─ BackEnd Workflows/
│ ├─ Output/
│ │ └─ last_run_from_backend_workflows_folder_log.txt
│ ├─ Upload File To Retool Storage.workflow
│ ├─ Make RPC Call.workflow
│ └─ Make MCP Call.workflow
├─ Validators/
│ ├─ Output/
│ │ └─ last_run_from_validators_folder_log.txt
│ ├─ Validate UI Inputs.workflow
│ ├─ Validate Prompt Inputs.workflow
│ └─ Get Input Types.workflow
├─ Prompts/
│ ├─ Output/
│ │ ├─ new_prompt.txt
│ │ └─ last_run_from_prompts_folder_log.txt
│ ├─ Generate Prompt.workflow
│ ├─ Get Base Prompt By Model And Task
│ ├─ Store Prompt in DB
│ └─ Get Stored Prompt.workflow
├─ Tests/
│ ├─ Output/
│ │ └─ tests_docs.md
│ └─ test_wkflw.workflow
├─ unorganized_wkflw1.workflow
└─ unorganized_wkflw2.workflow
being able to create a file we can reference by path would also let us use pythons memory-mapped file features (I think? I'm still learning it, but if we have a process intensive block due to file manipulation of some sort a memory-mapped file would help us stay away from runtime limits and having to divert time towards refactoring blocks/processes)