Organize the Files You Already Have, Not Just the New Ones
Most file automation starts the day you switch it on. The four thousand documents already in the folder — the ones that sent you looking for automation in the first place — are exactly the ones it will not touch.
The short answer
Automation that only fires on arrival leaves the backlog precisely where it was, which is usually the problem you were trying to solve. The On a Schedule trigger runs a workflow over a folder you point it at rather than waiting for the next upload, so documents already sitting there are read, renamed from their contents and filed the same way new arrivals will be. As each one is filed somewhere else, the watched folder drains, and what started as a backfill turns into the workflow that keeps the folder empty. It is one workflow, not two.
Steps this uses
Before and after
What actually changes
As they arrive
- Documents/Scan_0043.pdf
- Documents/invoice FINAL (2).pdf
- Documents/Untitled document
- Documents/IMG_4471.pdf
After the workflow
- Clients/Northwind/2026/2026-08-02-invoice-northwind-4821.pdf
- Clients/Acme/2026/2026-08-04-invoice-acme-1180.pdf
- Clients/Lighthouse/2025/2025-11-28-proposal-lighthouse.pdf
- Clients/Dataflow/2026/2026-09-11-receipt-dataflow.pdf
A folder that had been accumulating for two years, worked through overnight and filed by what each document says rather than when it was found.
Setting it up
Described once, then it runs
This is the sentence. Send it to the builder and the steps below appear on a canvas, wired and named, for you to change before anything runs.
Every night, work through my Documents folder: read each file, rename it date-first from what is inside it, and file it under the client and year it belongs to.
Point it at the folder, not at the future
The On a Schedule trigger runs over a folder on a repeating schedule. That is the difference from an upload trigger, which can only ever see what arrives next. The documents already in the folder are what it works through.
Start with one slice
The Check File Details step narrows a run to a subset — PDFs only, or everything older than a year. Doing the whole folder on the first night is how you find out at scale that your instruction meant something slightly different from what you intended.
Watch the first pass
Ask a Person to Approve pauses before each move on the first run, so the proposals arrive as a list to accept rather than as a folder that has already changed. Once the naming is doing what you meant, take it out and let the rest run unattended.
Let the folder drain
Each document is filed somewhere else, so the watched folder empties as the run works through it. When the backlog is gone the same workflow is still there, doing to tomorrow’s uploads exactly what it did to last year’s.
Why most automation cannot see your backlog
Rule-based tools are built on events: a file was created, a file was modified. An event is a thing that happens, so a tool built on events can only act on what happens after it is installed. The documents already in the folder generated their events months ago and nobody was listening. This is why the answer to "can it organize what I already have" is so often a quiet no, and why it is worth asking before anything else.
The backlog is where the cost actually is
New documents arrive a few at a time and can be filed as they come. The backlog is a single large debt that never gets a good moment, and it grows a little every week it is deferred. It is also the part that makes search useless: a drive where the last month is tidy and the previous three years are not is, for practical purposes, an untidy drive. Clearing it is the thing that changes how the drive feels.
What it does not do
It reads each document and files it. It cannot put back information that is not there — a scan too dark to read produces no date and no party, and goes to review rather than to a guessed folder. It does not deduplicate, delete anything without being told to, or reorganize folders it has not been pointed at. And it works at the pace of reading documents, so a large backlog is an overnight job rather than an instant one.
FAQ
Common questions
Can it organize files I already have, or only new ones?
Both, and with the same workflow. A scheduled run works over a folder you point it at rather than waiting for an upload, so documents already sitting there are read, renamed and filed. Most file automation is event-driven and can only act on what arrives after it is switched on; this is the difference worth checking for in any tool.
Will it move my existing files without asking?
Not if you put an approval in front of the move, which is worth doing on the first run. Proposals arrive as a list to accept or reject before anything changes. Once the naming and filing are doing what you meant, remove the approval and let it run on its own.
What about files whose names say nothing?
Those are the ones this is for. The name is not used — the document is read, and the date, the type and the party come off the page. Scan_0043.pdf and IMG_4471.pdf are filed on what is printed inside them, which is why a backlog of meaningless names is a solvable problem rather than a permanent one.
How long does a backlog take?
It runs at the pace of reading documents rather than moving them, so a few thousand files is an overnight job rather than a few seconds. Starting with a slice — one file type, or one year — gets you a readable result quickly and tells you whether the instruction says what you meant before it is applied to everything.
Start with the folder you have been avoiding.
One workflow clears the backlog overnight and keeps the folder empty afterwards.
5 GB free · No credit card required