Use a Tool to read supporting files, find project files, and save processed results. Choose the main work under Documents or folders and review the destination before running it.
Read the main input and supporting files
The Tool already receives its selected primary input. A separate file-reading action is useful when the task also needs another file.
When creating the Tool, describe which supporting file to read and how it should be used. Avoid a fixed path when the Tool is meant to work with different inputs.
For AI guidance such as a style guide, use Optional guidance. See Context and Input.
Find files or inspect them
A Tool can list files in a folder, find files matching a name or pattern, and check information such as file size or modification date.
Describe the location and selection rule when creating the Tool, such as “process Markdown files in this folder.” A filename pattern such as *.md limits a listing to that file type.
Save output
A file-writing action saves the previous action's result. Review the Tool's save settings and Save New Files To when a configurable destination is available.
An output folder produces a new file. Some workflows target an existing document and append their result. With Process each input file separately, folder or multi-file runs create a separate output for each input; a selected output document contributes its parent folder instead of collecting all results into that document.
A fixed path in the saved workflow can override automatic destinations. Check generated files after the run, and see Tool Output and Results for destination behavior and the limitation affecting documents open in the editor.
Move or delete project files
Use Project Navigator's file and folder menus for ordinary file management. See Folder Tree.
The Copy, Move, and Delete file actions are unavailable when creating a Tool. That does not make every Tool safe: a trusted Python script can change or delete files using your account's permissions. See Python Script Tools.