sodcalculator

10 Tech How-To

Convert Automator Actions Apps on Mac

Guide 10-38144 · Updated · Step by step

This guide shows you how to turn an Automator Quick Action (previously called a Service) into a standalone app on your Mac, so you can run it by double-clicking instead of right-clicking in the menu bar. You’ll also learn how to convert an existing Automator app into a Quick Action if you prefer the opposite. You only need the built-in Automator app, which comes free with macOS.

What You’ll Need

  • A Mac running macOS Ventura or later (the steps are similar on older versions).
  • The Automator app, located in your Applications folder or accessible via Spotlight (press Cmd+Space and type “Automator”).
  • The existing Automator workflow file (with a .workflow extension) or app (with a .app extension) you want to convert.

Step-by-Step

  1. Open Automator. Launch Automator from your Applications folder or via Spotlight. When the startup dialog appears, choose “Quick Action” (or “Service” on older macOS) and click “Choose.”
  2. Load your existing workflow. If you already have a Quick Action workflow file, go to File > Open and select it. If you have an Automator app you want to convert, skip to Step 4.
  3. Set the workflow to receive input (if needed). At the top of the workflow window, check the “Workflow receives current” dropdown. For a standalone app that doesn’t need input, select “no input” from the dropdown. For an app that processes files or text, choose the appropriate option (e.g., “files or folders” or “text”).
  4. Convert an existing app to a Quick Action. If you have an Automator app, open it in Automator by dragging the .app file onto the Automator icon in the Dock, or by using File > Open and selecting the app. Then go to File > Convert To and choose “Quick Action.” A new window opens with the same actions.
  5. Save as a Quick Action. Once your workflow is ready, go to File > Save. Give it a name (e.g., “Resize Images”). Automator saves it as a Quick Action in ~/Library/Services/.
  6. Test the Quick Action. Right-click (or Control-click) a file or selected text in Finder or any app, and look for your Quick Action in the context menu under “Quick Actions.” Click it to run it.
  7. To create a standalone app from a Quick Action: Open your Quick Action in Automator (File > Open, then navigate to ~/Library/Services/ and select it). Then go to File > Convert To and choose “Application.” This creates a copy as an .app file.
  8. Save the app. Go to File > Save and choose a location (e.g., Desktop or Applications). Name it and click Save. The app now runs independently when double-clicked.
  9. Adjust app settings. If your app needs to process files dropped onto it, check the “Input” section in the workflow. For an app, the input is set by dragging files onto the app icon. To allow that, make sure the workflow receives “files or folders” as input.
  10. Test the app. Double-click the .app file to run it. If it requires input, drag a file or folder onto the app icon. If it doesn’t work, check the Console app for errors (see Troubleshooting).

Common Mistakes

  • Forgetting to change the input type. A Quick Action that expects text won’t work well as an app if you drag a file onto it. Make sure the input type matches what you’ll actually feed it.
  • Saving over the original. When converting, Automator creates a new file but may ask to overwrite if the name is the same. Always save with a different name to keep the original.
  • Not enabling the app to run without input. If your workflow has a “Get Specified Finder Items” action, it doesn’t need input. But if it uses “Get Selected Finder Items,” it will fail when run as an app because there’s no selection. Replace that action with “Get Specified Finder Items” or “Ask for Finder Items.”
  • Ignoring permissions. If your workflow accesses files in protected folders (like Desktop, Documents, or Downloads), macOS may block it. You’ll need to grant permission in System Settings > Privacy & Security.

Tips

  • Use the “Run Shell Script” action carefully. When converting, the shell script’s “Pass input” setting may need to be changed from “to stdin” to “as arguments” depending on whether you’re using files or text.
  • Keep a backup. Before converting, duplicate your original workflow or app so you can revert if something goes wrong.
  • Test with a simple workflow first. If you’re new to Automator, create a tiny workflow (like a “Display Notification” action) and convert it both ways to understand the process.
  • Use the “Quick Actions” section in System Settings. After saving a Quick Action, you can manage it under System Settings > Keyboard > Keyboard Shortcuts > Services. You can assign a keyboard shortcut there.
  • For distribution, export as an app. If you want to share your workflow with others, converting to an app is more user-friendly because they don’t need Automator.

Troubleshooting

  • The app doesn’t run at all. Double-click the app and check if it appears in the Dock. If it doesn’t, open Console (in Utilities) and look for errors related to your app’s name. Common issues include missing permissions or a broken action. Rebuild the workflow step by step.
  • The app runs but does nothing. Check the input type. If the workflow expects files, drag a file onto the app icon. If it expects text, you may need to use a “Get Clipboard Contents” action instead. Also verify that each action is configured correctly.
  • “Cannot be opened because the developer cannot be verified.” This happens if the app was created on another Mac or downloaded. Right-click the app and select “Open” to bypass the warning once. For permanent access, go to System Settings > Privacy & Security and allow it.
  • Quick Action doesn’t appear in the context menu. Make sure the workflow is saved in ~/Library/Services/. Also check that the input type matches what you’re right-clicking. For example, a workflow that receives “text” won’t show when right-clicking a file.
  • Permissions errors when accessing files. Go to System Settings > Privacy & Security > Files and Folders. Find your app or the parent app (like Finder) and enable the relevant folders. You may need to restart the app.

Frequently Asked Questions

  1. Can I convert a Quick Action back to an app? Yes, open the Quick Action in Automator and use File > Convert To > Application. This creates a separate app file.
  2. Do I need Xcode to do this? No, Automator is sufficient. Xcode is only needed if you want to build a native app with a custom interface.
  3. Will the app work on other Macs? Yes, as long as the actions used are available on that macOS version. Some actions may require specific apps (like Preview) to be installed.
  4. Can I assign a keyboard shortcut to a standalone app? Yes, you can use the Keyboard Shortcuts settings to assign a shortcut to the app, or you can create a Quick Action and assign a shortcut to that instead.
  5. What’s the difference between a Quick Action and an app? A Quick Action appears in the right-click context menu and is designed to work with selected items. An app runs independently and can be double-clicked or dragged onto files.
  6. Can I edit a converted app later? Yes, you can drag the .app file onto the Automator icon to open it for editing. The changes will be saved back to the app.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →