North build
Correspondence / 18 files
✓ Matched identifierGoogle-first property records
Property Project Tracker files Gmail threads and attachments into a searchable Drive record. If it cannot prove where a message belongs, it sends it to review.
Fictional filing plan · no property data
Correspondence / 18 files
✓ Matched identifierCorrespondence / 11 files
✓ Matched identifier1 ambiguous message
! No guessingThe main rule
Known addresses, lot references and project terms decide the route. A message with no clear match, or several possible matches, goes to a labelled review queue.
How it works
The workflow uses focused searches, exact duplicate checks and a visible review queue.
Configured project details find relevant messages without scanning the whole mailbox on every run.
Clear matching rules must find one project. No match or several matches sends the message to review.
The workflow compares message text and exact attachment hashes so copied threads create only one record.
A readable HTML record and each unique attachment land in the project's Correspondence folder.
A tracker row retains received date, route, sender, subject and direct Gmail and Drive links.
One malformed message cannot stop the batch, and uncommitted items remain available for the next run.
The tracker Sheet
Every processed message gets an index row. You can search by project, date, sender or subject, then open the original Gmail message or Drive file.
Safety
Folder IDs stay in private Script Properties. The automation creates correspondence records and tracker rows, but does not move or delete existing property documents.
A Drew's Digest project