As we speak I have been establishing a brand new Folder Motion automator workflow for pdf to picture conversion (that is really the primary time I am working with script and automation in any respect, so there could also be rudimentary errors). The workflow works as meant: after I drop in a pdf picture into the designated watch folder, the file will get transformed right into a png and prompts me to reserve it to a different path. However there’s one constant downside that I am unable to resolve.
The folder I take advantage of because the "Folder Motion Folder" (folder identify in Finder "Automated Conversion") is beneath one other folder — name it the "Isolation Folder" (folder identify in Finder "Grapher Export") — which is beneath the consumer’s Footage folder (like under).
Footage -> Isolation Folder -> Folder Motion Folder (the folder designated within the Folder Motion workflow)
Here is a screenshot of my folder construction in Finder, hope it helps a bit:
I did this in order that the "Folder Motion" folder is remoted from day by day actions and I will not be by chance including any information to it. However I found that placing information within the "Isolation Folder", regardless of it being the father or mother folder of the "Folder Motion Folder", nonetheless triggers the automator workflow. I’m very confused that it labored like that.
Footage -> Isolation Folder (placing file right here triggers workflow, bizarre) -> Folder Motion Folder
I did some experiments for this. In a single, I added a subfolder to the "Folder Motion Folder", after which added a file to that subfolder. This triggered the workflow as nicely.
Footage -> Isolation Folder -> Folder Motion Folder -> New Folder (placing file right here additionally triggers workflow)
However including information to the father or mother folder of the "Isolation Folder", which is the Footage folder, does not set off any of that.
Footage (placing file right here doesn’t set off workflow) -> Isolation Folder -> Folder Motion Folder
I attempted re-creating that workflow, re-creating the folders, restarting my Mac, however the state of affairs remained the identical. Should not Folder Motion workflow be solely working for that one folder designated solely, with out getting influenced by any actions in its father or mother or sub folder? Does anybody have any thought on what is occurring right here? How ought to I make it that solely including information to the designated "Folder Motion Folder" will set off the workflow?
My macOS model is Sequoia 15.6.1, and this is a screenshot of my workflow:
The AppleScript I used (I mixed the code from https://www.macscripter.internet/t/save-files-to-a-user-chosen-location-at-runtime/71181 and Google’s search AI):
on run {enter, parameters} -- Specify the textual content file to retailer the trail. set pathFile to (alias "Macintosh HD:Customers:andyzou:Footage:Grapher Export:" as textual content) & ".last_folder.txt" -- Learn the final saved path from the file, if it exists. attempt set lastPath to (learn file pathFile as textual content) on error -- If the file doesn't exist, set the default path to the Desktop. set lastPath to path to desktop as alias finish attempt set destinationFolder to (select folder with immediate "Select a vacation spot folder for the Grapher Export" default location lastPath) -- Get the POSIX path of the chosen folder. set theChosenPath to POSIX path of destinationFolder -- Write the brand new path to the textual content file for subsequent time. set fileRef to open for entry file pathFile with write permission set eof of fileRef to 0 write theChosenPath to fileRef shut entry fileRef inform utility "Finder" transfer enter to destinationFolder with changing finish inform inform utility "Finder" delete (each merchandise of folder ("Macintosh HD:Customers:andyzou:Footage:Grapher Export:Automated Conversion:")) finish inform return enter finish run 
