Hi all,
A workplace accounting team organizes PDF copies of Accounts Payable in a "Year:Payable To" folder structure. Currently, the filing is done via manual copies into the destination folder.
I could save labor if I could devise a workflow that operates as
-Copy PDF into a single auto-sorting folder
-PDF is analyzed for content, it seeks the name of the recipient (it's in a predictable place), then moves PDF into the paired "payable to" folder.
In my first hour of exploring Hazel, my PoC of "content contains <who it's paid to>" -> move to the folder I paired with was a home run.
Great, except that at this moment, there are 398 possible destination folders, which means 398 rules to build. Next week there will be over 400: this is both unappealing to build, and unsustainable.
The ideal rule would flow as
-Look at this consistent section of page 1 of the PDF, extract the top line
-Does a folder matching that name exist in the destination path?
--If no, then create folder
-Move PDF to the matching folder
I'm not seeing anything that looks like a way to directly get there via what Hazel offers: afaict Hazel could be the trigger for an AppleScript or shell script that would actually do the action, but in that case, isn't Folder Actions the right tool for the job?
Throwing my question out here to see if there's any power in Hazel I'm overlooking.