I’m afraid it’s not possible w/ Rename/Move File. When you link a vault, you give AFO the permission to access that particular directory tree – but nothing outside it.
You’d have to fetch the file from its parent folder using a Get File from Folder action. This’d require you to explicitly allow folder access to that folder (stored in the action’s config for later/unsupervised use), and specify the file name. The result of that action would be a copy of that file, which you could then save in your vault using Save File. Example:
Your original would still be around, and only a copy would be saved in your vault (which you could then work with).
To actually move the file, you’d need to use the built-in Move File action:
It’s first parameter would be your original file (either select it directly, or pass in the result from another built-in File-emitting action, like Get File from Folder or Select File etc. The 2nd parameter needs you to explicitly allow folder access to the target folder (just like described above). Unfortunately, we can’t pass any path here from an AFO action because you have to manually give that permission at least once for security reasons.
Does that help?