The action Save file to

Purpose  

Saves the output produced by the previous action (for example a converted PDF, an AI summary, a transcript, an image or any generated file) to a local or network folder. Use this action at the end of a scenario (or at any point where you need to persist an intermediate result) to write the file to disk.

Where to add  

Place Save File in any scenario step that receives a file from a preceding action (Convert to PDF, Extract Text, Summarize with AI, Generate Image, etc.). The action writes the current item in the pipeline to the selected destination.

Main settings

• Destination folder
  Enter or browse to the folder where files should be written. Click Search to open the folder picker.
  You may use local paths (e.g., D:\temp) or UNC network paths (e.g., \\server\share\MyFolder). If saving to a network location, don't use network shortcut (like x:\MyFolder\), read more on this page >
  You can insert fields to create dynamic folder, for example: d:\temp\%DATE_YEAR%\%FILE_EXTENSION%\
• Filename
  Enter the filename to create. Use Fields to insert dynamic value into the filename (for example %FILENAME_FULL%, %DATE_YEAR%, %RANDOM_NUMBER%). This lets you compose dynamic, unique filenames that include the original name, date/time stamps, content-based metadata or random values. Use them to avoid name collisions and to create meaningful, sortable filenames.

Quick configuration steps

1. Add the Save File action to your scenario step.  
2. In Destination folder, type or Browse to the folder where files will be saved (use a UNC path for network shares).  
3. In Filename, type the desired name and include the extension, or build the name with Fields.  
4. Click OK to save the action.

Network saving notes and permissions

• Use UNC paths (\\server\share\path) rather than mapped drive letters when the scenario runs as a service, mapped drives may not be available to service accounts.  
• Ensure the account under which your scenario runs (service account or scheduled user) has write permissions on the destination share/folder. Verify both NTFS and share permissions.  

Filename and collision guidance

• Prevent accidental overwrites by composing filenames with date/time or a random token (for example %RANDOM_NUMBER%-%FILENAME_FULL%).  

Best practices

• Standardize file naming for easy sorting and ingestion by downstream systems (CRM, ERP, archive). Examples: %DATE_FULLSHORT%_%FILENAME_FULL% or Invoice_%RANDOM_NUMBER%_%DATE_FULLSHORT%.txt.  
• Test with representative files and run the scenario with the same account that will be used in production to validate permissions and path resolution.  
• Use subfolders generated from fields (for example \\server\share\%DATE_DAY%\) to organize output by day or process.
• Keep filenames short and avoid invalid characters (\/:*?"<>|).

Troubleshooting

• “Access denied” or “Path not found”: verify the path is correct and that the scenario process account has write permissions. Prefer UNC path for network shares.  
• Files appear to be missing: check that you included the extension and the correct destination folder; verify any filters or downstream saves do not move or delete files.  
• Name collisions: add a timestamp or %RANDOM_NUMBER% token to filenames to avoid overwriting.  
• Long path errors: ensure path length does not exceed OS limits; use shorter folder names if necessary (in Windows limit is set to 240 chars).

Examples

• Save a converted PDF with original name and a random prefix: Destination folder = D:\temp, Filename = %RANDOM_NUMBER%-%FILENAME_FULL%
• Save AI summary as a dated text file: Destination folder = \\fileserver\summaries, Filename = Summary_%DATE_FULLSHORT%_%FILENAME_FULL%.txt  
• Store daily outputs in date folder: Destination folder = \\server\share\exports\%DATE_DAY%\, Filename = %FILENAME_FULL%

That’s all, pick a folder, define a filename (use fields for dynamic names), set failure handling if needed, and the Save File action will write the previous action’s result to the chosen local or network location.