The one folder Neaflo watches. Exactly one per workflow. Subfolders and hidden files are opt-in.
Everything Neaflo does, in the order you meet it.
You do not need the app open to understand it. This page walks the whole model: the steps you can place on a canvas, what Preview tells you, and what happens after you switch automation on.
The five kinds of step
A workflow always starts with one Source and ends each path with Move or Ignore. Everything in between shapes the destination.
Splits the path into branches. Branches are checked in order, and the last one is the fallback.
Each structure step adds one folder level. Stack several to build a deeper destination path.
Ends a path by moving the file into the destination the structure steps produced.
Ends a path by leaving the file exactly where it is. Useful as the fallback branch of a filter.
Rules read metadata, never contents
A File filter branch matches on facts about a file, not on what is inside it. That is a deliberate limit: it keeps behaviour predictable and keeps your documents unread.
Build one here before you install anything.
Add steps from the dock, drag them into a different order, and press Preview. The list on the right recomputes from your flow—the same way the real planner does.
What Preview tells you
Preview is a dry run against the same operation plan execution uses. Every file falls into one of four states, and each one is labelled in words as well as colour.
Will move
The full destination path is shown before anything happens, so you can check the structure you built.
Documents / 2026 / July / ImagesStays where it is
The file reached an Ignore branch, or no branch matched it. Neaflo does not touch it.
Stays where it isNot stable yet
The file is still downloading or being written. Neaflo waits and retries once its metadata settles.
neaflo-setup.exe.partConflict handled
A file with that name already exists at the destination. The incoming file gets a counter instead of overwriting.
client-brief (2).docxAutomation
Once a workflow has been previewed successfully, it can watch the folder for new files.
- Activate, pause and resume per workflow
- Several non-conflicting workflows can run together
- Start at login and stay in the system tray
- Runs while Neaflo and your device are available—not in the cloud
History
Every run and every individual operation is recorded locally so you can answer "where did that file go?".
- Grouped by workflow, newest run first
- Manual runs and automated runs are labelled separately
- Each operation keeps its source and destination path
Guarded undo
Undo reverses a run, but only while it is still safe to do so.
- A moved file that changed after the run is blocked, not guessed
- Undo stops if the original location is no longer safe
- Blocked items are listed with the reason, per file