Convert .pages files to word (or rtf) in bulk

The code itself works just fine in macOS 11.6.8, and 12.5.1. However, the first time you run the Automator application it will prompt you three times for permissions that you must grant in order for it to proceed. When you agree (select OK) each time, it will update the System Preferences > Security & Privacy > Privacy panel entries to make these permissions permanent. In this case, my arbitrary name for the Automator application is PagesXWord.app.

I exported a 180pp Pages document this morning to Word .docx without issues using this code.

First:

Second:

and finally:

As mentioned previously, the Automator Application requires two actions:

1. Ask For Finder Items
   1. Start at Desktop
   2. Type: Folders ☑︎ Allow Multiple Selection
   3. Select the Pages folder, press the ⌘-key, and then select the output folder for the exported Word docx
2. Run AppleScript
   1. Remove all default boilerplate content from this action and replace it with the AppleScript in the original post.
   2. The on quit handler should read: on quit and not on quit {}.

Here is the updated comment section for that AppleScript:

(*
 The script converts Pages documents found in the source folder to Word (.docx) documents
 in the output folder.

 Intended to be used in an Automator application's Run AppleScript action
 Preceded by an Ask for Finder Items action whose type is Folders with Allow Multiple
 Selection, one chooses the folder containing the Pages documents and
 then presses the ⌘+key to select the destination folder. This order is critical.

 Reference: https://discussions.apple.com/thread/253072302
 Tested: macOS 11.5.2 (20G95), Pages 11.1, macOS 10.14.6 (18G9323, Pages 10.1
 Tested Update 2022-09-10: macOS 11.6.8, 12.5.1, Pages 12.1
 VikingOSX, 2021-08-23, Apple Support Communities, No warranties/support expressed or implied.
*)

Hopefully, there are no English<->Italian namespace issues for quoted names as AppleScript is not auto-language sensing.

As Pages is no Word clone, the content of your existing Pages documents may not appear in Word format as it does in Pages. It might be better to achieve a visually faithful export to PDF, and then use MS Word v16.31 or later to open those PDFs and create Word .docx documents from them.

In System Preferences > Security & Privacy > Privacy panel > Automation, make certain you have the following items selected where your Automator application name replaces PagesXWord:

Once those three dialogs are satisfied, either currently when running Automator, or from some other prior application resolving them, they do not repeat, so understandable that you may not receive all three of those challenges.

There are two ways to design this Automator application: 1) Three actions where you are sequentially prompted for the source folder containing the Pages documents, and then a second prompt for the destination folder to receive the Word documents, or 2) One Ask for Finder Items action that allows multiple selections to first specify the Pages folder, and then by pressing the ⌘-key, clicking the destination folder. In either scenario, two folder paths are passed to the Run AppleScript action in their selection order.

This solution is currently written to expect a source folder and a destination folder. If you want the Desktop as the source folder and the Desktop again as the destination folder, that will work with the two prompt [1] implementation above as you just click choose on each dialog. It won't work with the one-prompt, multiple-selection version.

Automator applications are intended to be saved to the Desktop where they are double-clickable. I usually leave them there, or maybe drag them into the /Applications folder, but never attempt to save them anywhere but the Desktop. I have also never received the code-signing error or any error regarding the CommandLine Tools and I am running macOS 11.6.8. That xcrun application is in /usr/bin, not in the CommandLine tools path that it proclaimed as missing on that dialog.

When you dragged the Run AppleScript action to the main workflow window, did you remove all default content, before pasting in the entire code provided in the original post?

I can build this solution from scratch using either [1] or [2] design scenarios from above and it just saves and works correctly without any errors. Perplexed that it does not work for you…