Organize local files

Use Files & Folders to archive recordings or copy selected logos into a scene's working folder. Start with disposable copies and Preview only before enabling live execution.

Before you start

Open and save a test project. In Core Settings → Files & Folders, create the locations the workflow needs. Folder access belongs to this project file on this PC and is not exported.

Allow subfolders wherever paths contain nested directories. Keep input and output locations separate so output writes do not repeatedly trigger the watcher.

Use … beside a path to select it from the Data-style tree popup. Add List and inspect permission to each location you want to browse; manual relative paths remain available without browsing. For a new destination, select the location and enter the relative name in the popup's path box.

Archive a ready recording

1. Create an automation with Files & Folders → File Ready.
2. Select recordings, leave Relative folder empty and use *.mkv;*.mp4 as the include pattern. Leave Process existing files off initially.
3. Choose a suitable stability period. Stability is not proof that recording has finished; prefer an explicit recorder completion signal when available.
4. Add Move File, with Location recordings and Relative path {event.payload.path}.
5. Set Destination location to archive, Destination path to finished/{event.payload.name}, enable Create parent folders and choose Fail for destination conflicts. Approve subfolder access at archive.
6. Enable Preview only, apply and save. Put a disposable completed video into the incoming folder.
7. Inspect the run: the source should remain, with result status preview and the intended destination.
8. Disable Preview only, save and introduce another disposable completed file. A successful run copies and verifies the destination before removing the source.

Expected result: the second file appears under finished in archive. A collision fails instead of replacing an existing recording. Choose UniqueName to preserve both versions.

For a recorder-driven automation, convert its completed-file reference into the approved location's relative name. Do not pass an unrestricted absolute path to the action.

Prepare scene logos

This workflow can use a button, timer or another integration's event. A folder signal is not required.

1. Create a string variable team and set it to a known test filename stem.
2. Add Copy File with Location logos, Relative path teams/{vars.team}.png, Destination location live and Destination path team.png.
3. Choose Replace, approve Modify / overwrite at live, and allow subfolders at logos because the source is inside teams.
4. Run with Preview only and inspect the paths.
5. Disable Preview only and run again. Confirm the destination image before letting the scene use it.

Expected result: the original logo remains; the selected image is copied to team.png in live. Files & Folders only prepares the file. It does not configure or prove that another application has refreshed its scene.

Read the result

Following steps can read {runtime.files.last.status}, {runtime.files.last.destinationPath} or {runtime.files.last.bytes}. Use a different Result path for each operation when several outputs must remain available in one run.

A failed or partial action follows the sequence's normal error policy. partial means some effects may already have happened; inspect item outcomes before retrying. Cancellation does not undo completed transfers.

Common problems

Related

• Files and folders reference
• Test a signal
• Pass data between steps
• Runs