In general Applescript and Filevault don't work very well together. Some people call it even a bug that you can't write with applescript to a filevault encrypted directory. As for this hint, it is shorter than my work around. My workaround was to save the file via the workflow first to a folder outside the filevault directory, say inside the Shared folder and then move the contents into a folder inside my personal Documents folder. I suspect the reason that the hint works is that while applescript fails to copy or move files into a filevault protected directory, the commandline unix commands do work. I guess that the automater actions of copying and moving are based directly on the unix commands. I have not tried the command line mkdir to see whether this creates a new folder inside a filevault protected directory.