Automations/Everyone
Rename Scanned PDFs by What Is on the Page
A scanner names a file by the order it came off the glass. Scan_0043.pdf tells you it was the forty-third thing scanned, which is the one fact about it you will never need.
The short answer
Renaming a scanned PDF properly means reading the page, because the name assigned by the scanner carries no information about the document. A workflow watching the folder your scans land in uses the Read Details from File step to pull the date, the document type and the party off the page, then the Rename step writes that into the filename — in place, in the folder the scan is already in. The Move step can then file it. Scans that arrive as email attachments need the Save a Copy step first, because an attachment has no home until something gives it one.
Steps this uses
Before and after
What actually changes
As they arrive
- Scan_0043.pdf
- Scan_0044.pdf
- Scan_0045.pdf
After the workflow
- 2026-08-02-invoice-northwind-4821.pdf
- 2026-08-04-signed-contract-acme.pdf
- 2026-08-04-receipt-dataflow.pdf
Three consecutive scans of three unrelated documents.
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.
When a scan lands in my scans folder or arrives as an email attachment, save a copy, read the date, document type and party off the page, rename it date-first, and file it by document type.
Send scans to one folder
Whatever your scanner already does is fine, as long as the output lands somewhere consistent — a Google Drive, OneDrive or Dropbox folder.
Describe the name you want
The date on the document, what kind of document it is, who it is from. In plain English, once.
The workflow reads the page
The Read Details from File step works from what is printed on the document, which is why it succeeds where the scanner filename fails entirely.
Renamed, then filed
The Rename step names it and the Move step puts it in the right folder. Both happen in place in your existing cloud storage.
Why scanner filenames are always wrong
A scanner knows two things: the order it processed pages and the time it did so. It cannot know that page forty-three was an invoice from Northwind dated the second of August, because it never read it. Every scanner naming scheme is therefore a counter, and every counter produces filenames that are unique and useless in equal measure.
Scans that arrive by email
Plenty of scanned documents never touch a scanner you own — they arrive as attachments from a client, an accountant, or a scanning service. An attachment has no home until something gives it one, so the Save a Copy step files it into cloud storage first, and the Rename and Move steps then treat it exactly like a scan from your own machine.
Multi-document scans
If you fed a stack through the sheet feeder and got one PDF containing eleven separate invoices, renaming is the second problem. The Split Document step separates them first, and each resulting document is then renamed on its own terms.
Then build
Variations worth building next
When someone shares a scanned PDF in our Microsoft Teams channel, save a copy to my drive, read the date, document type and party off the page, rename it date-first, and file it by document type.
Catches scans that colleagues post in Teams rather than send by email.
When a scan lands in my scans folder, ask AI whether it is an invoice, a receipt or a contract, rename it date-first from the page, and move each kind to its own folder. Send anything else to a Review folder.
Routes each kind of scan to its own folder and parks the unclear ones for a person.
When a scan lands in my scans folder, read the date, document type and party off the page, rename it date-first, and save a copy to the matching folder in our SharePoint library.
Keeps a shared team copy in SharePoint while the original stays where the scanner put it.
Limits
What to know before you build it
It runs on new files, not your backlog
This workflow fires when a file arrives. It will not go back over the documents already sitting in the folder, so switching it on leaves the existing pile exactly where it is. Working through what is already there is a scheduled run instead, which is a different workflow.
Organize the files you already haveIt needs a connected account
This workflow reads files out of an email inbox, so it cannot run until that account is connected. Connecting one is on the Max plan, or on any team workspace. There is no version of this particular workflow that runs on the free plan, because the files it organizes never arrive in The Drive AI on their own.
FAQ
Common questions
How do I rename scanned PDF files automatically?
Point a workflow at the folder your scans land in. The Read Details from File step reads the date, document type and party off the page, and the Rename step writes them into the filename. The file is renamed in place in your existing cloud storage.
Why does my scanner name files Scan_0043.pdf?
Because a scanner names files by the order it processed them and nothing else. It does not read the page, so it has no information about what the document is. Every scanner naming scheme is a counter for this reason.
Can I rename a scanned PDF that contains several documents?
Split it first. The Split Document step separates a multi-document scan into individual files, and each one is then renamed from its own contents.
Does this work on scans that arrive as email attachments?
Yes. The Save a Copy step gives the attachment a home in cloud storage first — an attachment has no folder of its own until something files it — and renaming proceeds from there.
Let the page name the file.
The date, the type and the party, taken off the document instead of the scanner.
5 GB free · No credit card required