Manage files in Mate Drive

Use Mate Drive to manage files used by a Hyperflow. Keep the selected Hyperflow version and the file's path together so that a flow uses the intended resource.

Before you start

• Open the intended Hyperflow and select its Dev version for file changes.

• Prepare a small sample file and confirm the storage/file-size allowance shown by your environment.

• Identify any action that references the file.

• Keep a copy of a file before replacing or deleting it.

Upload a file

1. Open Mate Drive for the selected Hyperflow version.

2. Navigate to the intended folder using the folder tree or breadcrumb.

3. Upload the sample file.

4. Confirm the filename and path in the file list.

5. Select or map the file in the action that will use it.

6. Run a controlled test and inspect that action's output.

If the upload adds a suffix to a duplicate filename, use the resulting filename rather than assuming the original path was replaced.

Organize and reuse files

1. Select the Dev version and locate the file.

2. Use the available folder and file controls to organize it.

3. If copying a file from another version into Dev, verify both the source and destination.

4. Recheck any action path after moving or renaming a file.

5. Before releasing the Hyperflow, confirm that the required file is available to the version you intend to run.

The Active version is intended for released resources. Make file changes through the appropriate editable version instead of treating the production file list as a shared scratch folder.

Remove an unused file

1. Check for actions that reference the file.

2. Keep any required recovery copy.

3. Select the file in the editable version and use the available delete control.

4. Confirm the filename and version before accepting deletion.

5. Test any affected flow path.

Historical-version file permissions can differ. Use only the operations offered by the selected version; do not work around a disabled control.

Expected result

The action reads the intended file from the intended version, and unrelated versions retain their expected resources.

Troubleshoot

• Upload rejected: check file size, available storage, permissions, and the selected version.

• File not found: compare the actual path and filename after upload, copy, or move.

• Works in Dev but not after release: check the file/resource referenced by the released version.

• Duplicate file: inspect the generated suffix and update the consuming action if needed.

Related reference

• Manage versions and dependencies

Try it: upload a CSV and use its versioned path

Use the three-line synthetic docs-departments.csv from the CSV example. The captured file is 59 bytes and contains request_id,department followed by REQ-DEMO-001,finance and REQ-DEMO-002,hr on separate lines.

1. Open Docs - Action examples - 20261013 in Dev v1.0.1 and select the Mate Drive control. Check the version displayed inside the Mate Drive dialog.

2. Use Add New to create the test folder docsexamples20261013. Open it and choose Upload File. After uploading, the list shows docs-departments.csv, 59 Bytes and the last-modified time.

The Dev v1.0.1 resource folder contains the uploaded 59-byte CSV. Keep the version and full file path together.

3. Use Copy Path for the folder. In this example it returns mate:/docsexamples20261013. The consuming action uses the complete path mate:/docsexamples20261013/docs-departments.csv. Copy the actual filename if your upload receives a duplicate-name suffix.

4. Add CSV → Read in the same Dev Hyperflow. Choose Custom String for File Path, enter the complete mate:/ path, select comma(,), Read Only, Exclude header from data and Read file as UTF-8. Map csv Source to the Data Table variable department_rows.

The consuming CSV action references the exact uploaded mate:/ path. Its table mapping needs its own result check.

5. Save and run the Hyperflow. CSV Read completed with INFO at 11:10:03 on 13 October 2026 and returned a generated file-path string in its action preview. This checks that the resource path can be read, rather than previewing every table row. The follow-on Data Table Length returned 3 for the header plus two business-data records with Exclude header from data both selected and cleared. Engineering is tracking this behavior in the checked release. Follow the CSV guide and inspect the first row before using the records.

6. Before releasing, confirm which resource the intended version uses. A file uploaded to Dev does not by itself verify availability in an existing Active version. Keep the synthetic file until its consuming action and data mapping have been checked.