01
Describe a repeated job, then inspect the draft
Plain language becomes a grounded local workflow that remains editable, explainable, undoable, and explicitly review-first before it is saved or run.
WorkflowsWorkflows
Build reusable file pipelines from plain language or precise steps.
Workflows chains compatible Foldout operations into an inspectable recipe. Describe a goal for a grounded local draft or build manually; choose the input prompt, ordered steps, file-type routing, conditions, failure behavior, output naming, and destination; then run once, save for later, launch from Finder Quick Actions, or call the workflow from Watch Folders.
Start the 14-day trial in the app. No payment method is required to try Foldout.
Local tool processingFiles and tool work stay on your Mac.
100+ focused toolsFiles, PDFs, media, capture, and developer workflows.
Settings ready to goFormats, dimensions, and other values carry into the tool.
Try everything first14 days in the app. No payment method required.
What it does
Turn repeated multi-step file work into a visible, editable, locally executed pipeline.
Describe a goal in plain language and review the grounded draft before anything runs.
Build manually from dozens of compatible PDF, image, video, audio, archive, and data steps.
See source files, ordered transforms, output type, naming, and destination as one pipeline.
Restrict a step to selected file types and add size or count conditions.
Choose whether a failed file is skipped, stops the workflow, or moves to a review folder.
Run once without saving or reuse the recipe from Foldout, Finder, and Watch Folders.
Preserve originals while each operation works on copies and writes deliberate outputs.
Build, review, run
Turn a repeated file job into an inspectable workflow.
Inputs, ordered steps, conditions, naming, and output decisions remain visible before the workflow runs.
02
Keep source, ordered steps, naming, and destination visible
The pipeline shows selected files flowing through resize and privacy cleanup, watermarking, and checksums before named outputs reach the chosen delivery folder.
03
Control each step instead of trusting a black box
Reorder the recipe, restrict which file types a step sees, choose failure behavior and conditions, then edit the selected operation with compatible next steps close by.
Why it belongs
Why Workflows earns a place in the toolbox.
The practical details that make this job faster, clearer, or safer than doing it by hand.
Natural language produces an editable plan
The local builder explains its steps, supports grounded refinements and undo, and never turns a phrase into an automatic run.
The pipeline exposes every handoff
Input, current file type, each transform, output naming, destination, and outcome checks remain visible before execution.
Each step has operational controls
Per-step routing, failure policy, optional conditions, reorder, duplicate, and removal controls make complex recipes predictable rather than opaque.
How to use it
From opening the tool to saving the result.
- 01
Describe the result you need or start from a template.
- 02
Review and edit the ordered compatible steps.
- 03
Choose input behavior, output naming, destination, and failure policy.
- 04
Run once or save the workflow for reuse from Foldout, Finder, or Watch Folders.
Questions
Before you try Workflows
Does a plain-language request run automatically?
No. Foldout creates a grounded editable draft that must be reviewed and explicitly run or saved.
Are original files modified?
No. Workflow processing operates on copies and writes new outputs.
Can a workflow be reused outside this page?
Yes. Saved workflows are available from Finder Quick Actions and Watch Folders as well as the Workflows tool.
Related tools