Email is full of PDFs and most of them never leave it. Then six months later you need one and you spend an hour searching for it. Here's a 90-second pipeline that gets each PDF from inbox to archive cleanly.
It's nothing clever. It's just consistent.
Save, don't star
When a PDF lands by email, save it to `/Inbox/PDFs` immediately. Don't star, don't 'I'll deal with it later'. Two clicks. Done. The PDF is now in your file system, not your email — which means search, naming, processing all work properly.
The email is now reference, not storage. Archive the email; the PDF is no longer dependent on it.
Rename to your convention
`YYYY-MM-DD_<sender>_<doc-type>.pdf`. Five seconds. Do it the moment you save, while the context is in your head.
Attachments often have terrible names — `attachment.pdf`, `document(3).pdf`, `Scan_20250815.pdf`. Rename and they become findable forever.
Process whatever it needs
Sign, compress, merge, redact — whatever the PDF needs to be useful. Do it now while you're already touching the file. Coming back later doubles the cost.
If no processing is needed, fine. Skip to file.
File and forget
Move to `/Archive/<year>/<category>/`. Close the folder. Done. The PDF is now safely outside your inbox and inside a structure where you can find it again.
Total time: 60 to 120 seconds. Total inbox attachments handled: one. Repeat as needed.
FAQ
What if I'm in a meeting when the PDF arrives?
Save it later that day. The pipeline isn't real-time — daily batch processing also works. The point is: never leave PDFs in email as your storage system.
Can I automate parts of this?
Email rules can auto-save attachments from specific senders to specific folders. Beyond that, processing is hands-on — but hands-on is fast when you've named and filed correctly upstream.
What about PDFs sent via Slack or Teams?
Same pipeline, different entry point. Download to `/Inbox/PDFs`, rename, process, file. Don't treat messaging-app PDFs as 'temporary'.
Do I lose anything by removing PDFs from email?
No — the email itself is still there as context. You're just not relying on it as the file store.
Email is not a filing system. Your file system is. Run the inbox-to-PDF pipeline in Flint on the next attachment that lands and feel the difference.