Import Automator Scripts into Shortcuts on macOS: Step-by-Step

This guide shows you how to bring your existing Automator workflows into the Shortcuts app on macOS, so you can run them with Siri, from the menu bar, or as part of larger shortcut chains. You’ll learn the two main methods—converting a workflow file directly and recreating it manually—plus what to do when a conversion isn’t possible. No prior Shortcuts experience is needed, but you should have your Automator workflow saved as a file (with the .workflow extension) and be running macOS Monterey or later, as that’s when Shortcuts became a standard Mac app.

What You’ll Need

• A Mac running macOS Monterey (12.0) or newer.
• An existing Automator workflow saved as a .workflow file (usually in ~/Library/Services or wherever you saved it).
• Your Mac logged in with the same Apple ID used for iCloud, if you want shortcuts to sync across devices.

Step-by-Step

1. Open the Shortcuts app. Click the Launchpad icon in the Dock, type “Shortcuts,” and press Return. Or use Spotlight (Cmd+Space) and type “Shortcuts.”
2. Locate your Automator workflow. In Finder, navigate to the folder containing your .workflow file. If you created it as a Quick Action (Service), it’s likely in ~/Library/Services. You can also search for it by name in Spotlight.
3. Drag the workflow file into the Shortcuts window. Click and hold the .workflow file in Finder, drag it over the Shortcuts window (the sidebar or the main grid), and release. Shortcuts will attempt to import it automatically.
4. Check the result. After the drag, a new shortcut should appear in your list. It may have the same name as the original workflow or a generic name like “Imported.” Double-click it to open the editor.
5. Review the actions. Shortcuts converts many Automator actions into equivalent Shortcuts actions. Scroll through the list and verify each step is present. Some actions may appear as “Open in App” or “Run Shell Script” if there’s no direct equivalent.
6. Fix any “Unsupported Action” warnings. If you see a red banner or an action that says “Action Not Available,” click it. Shortcuts will often suggest a replacement. If not, you’ll need to rebuild that step manually using the action library on the right side of the editor.
7. Test the shortcut. Click the play button (▶) in the top-right corner of the editor to run it. If it uses input files, select a test file when prompted.
8. Rename and organize. Right-click the shortcut in the sidebar and choose “Rename” to give it a meaningful name. You can also drag it into a folder or add it to the menu bar via Shortcuts → Settings → General → “Show in Menu Bar.”

If the drag-and-drop import fails (nothing happens, or you get an error), don’t worry. The next method always works:

9. Create a new shortcut manually. Click the “+” button in the Shortcuts toolbar to start a new shortcut.
10. Add the same actions. Open your Automator workflow in Automator (double-click the file). Note each action in order. In Shortcuts, use the search bar in the action library to find the matching action and add it. For example, “Get Selected Finder Items” in Automator becomes “Get Selected Files” in Shortcuts.
11. Copy settings. For each action, match the settings: file types, filters, shell scripts, etc. For “Run Shell Script” actions, copy the script text and the shell choice (e.g., /bin/bash).
12. Save and test. Once all actions are added, click the shortcut name to rename it, then press play to test.

Common Mistakes

• Dragging the workflow while Automator has it open. Close the workflow in Automator first, or the file may be locked.
• Expecting a perfect 1:1 conversion. Automator actions like “Extract Text from PDF” or “Combine PDF Pages” may not have direct Shortcuts equivalents. You’ll need to use “Open in App” actions or third-party integrations.
• Forgetting to set the input. If your workflow was a Quick Action that received text or files, your new shortcut needs an “Input” setting. Click the shortcut’s name in the editor, then check the “Input” section in the settings panel (the “i” icon) and choose “Shortcut Input” with the appropriate type.
• Ignoring the “Show More” options. Some actions have hidden settings. Click the “Show More” toggle at the bottom of an action to see all options.

Tips

• Use the “Convert to Shortcut” feature in Automator. In Automator, go to File → Convert to Shortcut. This exports the workflow as a shortcut file that you can double-click to install. It often handles more actions than drag-and-drop.
• Keep the Automator workflow as a backup. Don’t delete your original until the shortcut works perfectly.
• Use folders and tags. Organize imported shortcuts into folders (right-click in sidebar → New Folder) to keep things tidy.
• Add to menu bar. If you use the shortcut often, enable “Show in Menu Bar” in Settings so you can trigger it from anywhere.
• Test with sample data. Run the shortcut with a dummy file or text to avoid accidentally modifying real files during testing.

Troubleshooting

The workflow won’t drag into Shortcuts. Make sure Shortcuts is open and not in full-screen mode. If it still fails, use Automator’s “Convert to Shortcut” option instead.

The shortcut runs but does nothing. Check the input settings. If the shortcut expects files, it may be waiting for input that never comes. In the editor, click the shortcut name and set “Input” to “Shortcut Input” and choose the correct type (e.g., Files).

An action is missing or grayed out. This usually means the action requires a system extension or permission. Go to System Settings → Privacy & Security and check if Shortcuts needs access to Files, Photos, or Automation. Grant permission and try again.

Shell script errors. If your Automator workflow had a “Run Shell Script” action, the script may rely on environment variables or paths that differ. Open Terminal and run the same script manually to see the error. Adjust the script in Shortcuts accordingly.

The shortcut is not appearing in Siri suggestions. Make sure the shortcut is enabled for Siri: right-click it → Properties → check “Use with Siri.” Also, in System Settings → Siri & Spotlight, ensure Shortcuts is allowed.

Frequently Asked Questions

Can I import a .workflow file that was created on an older macOS version? Yes, drag-and-drop works regardless of the macOS version it was created on, as long as the actions are still supported. Unsupported actions will show warnings.

Will my Automator variables and lists carry over? Shortcuts uses a different variable system. Simple variables may convert, but complex ones often need to be recreated manually. Check each action’s variables in the editor.

Can I run the imported shortcut from the command line? Yes, you can use the shortcuts command in Terminal: shortcuts run "Shortcut Name". This works for any shortcut, including imported ones.

What if my workflow uses AppleScript? AppleScript actions convert to “Run AppleScript” actions in Shortcuts, which work the same way. The script itself is preserved.

Can I share the imported shortcut with someone else? Yes, right-click the shortcut → Share → Copy iCloud Link, or export it as a file via File → Export. The recipient will need macOS Monterey or later.

Is there a way to batch convert multiple Automator workflows? No built-in batch conversion exists. You’ll need to drag each one individually or use Automator’s “Convert to Shortcut” on each file.

Related

• Android as Second Display: Setup Guide
• Best Microsoft Edge Settings You Should Change
• Export Browse AI Data to Google Sheets in India