Automator on macOS offers two distinct workflow types—workflows and applications—plus a few specialized variants like Quick Actions, Folder Actions, and Print Plugins. The core difference is how and when each type is launched: a regular workflow runs only from within the Automator app, while an application runs as a standalone double-clickable file. This article explains each type, when to use it, and how to choose the right one for your task.
What Automator Is and Why Workflow Types Matter
Automator is a built-in macOS tool that lets you automate repetitive tasks without writing code. You build a workflow by dragging actions—such as “Get Selected Finder Items” or “Rename Finder Items”—into a canvas and connecting them in a sequence. The type of document you save determines how that sequence is launched and what inputs it can accept. Choosing the wrong type can mean the difference between a one-click utility and a file that never runs when you need it.
The Main Workflow Types
Automator offers several document types, but the two primary ones are Workflow and Application. Additionally, there are Quick Actions, Folder Actions, Print Plugins, and Calendar Alarms. Here’s a breakdown:
- Workflow – The default type. It runs only when you open it in Automator and click the Run button. It’s useful for testing and for tasks you run manually from within the app.
- Application – Saves as a standalone .app file. Double-clicking it runs the workflow. It can also accept files or text dropped onto its icon, making it ideal for batch processing.
- Quick Action – Appears in the Services menu, the Touch Bar, and the Finder’s context menu (right-click). It’s designed to work with selected items, like files or text, and can be assigned a keyboard shortcut.
- Folder Action – Attaches to a specific folder and runs automatically when items are added, removed, or changed in that folder.
- Print Plugin – Appears in the PDF menu of the Print dialog, allowing you to process the current document (e.g., save as PDF, extract text).
- Calendar Alarm – Runs at a scheduled time or when a calendar event occurs. It can be used for reminders or scheduled maintenance tasks.
Workflow vs. Application: The Core Difference
The most common confusion is between a standard Workflow and an Application. A Workflow is essentially a project file that requires Automator to run. If you double-click a .workflow file, it opens in Automator, not runs. This is fine for editing and testing, but it’s not convenient for everyday use. An Application, on the other hand, is a self-contained executable. It doesn’t need Automator to be running, and it can be placed in the Dock, the Applications folder, or anywhere else. It can also accept input: if you drag a file onto the app icon, the workflow receives that file as its input (provided the first action is of the “Get Selected” type).
For example, a workflow that resizes images and saves them to a folder would be more useful as an Application, because you can drag a batch of images onto the app icon and it processes them all. A workflow that you only run occasionally while developing, like a test that renames a few files, can stay as a Workflow.
Quick Actions: The Modern Replacement for Services
Quick Actions (formerly called Services) are a more integrated type. They appear in the right-click context menu in Finder and in the Touch Bar (on supported Macs). They are designed to receive the currently selected item—files, text, images, etc.—and perform an action on it. For instance, a Quick Action could take selected images and create a PDF, or take selected text and count its words. You can also assign a keyboard shortcut in System Settings → Keyboard → Shortcuts → Services. This makes Quick Actions the best choice for tasks that you want to trigger from anywhere with a right-click or a shortcut.
Folder Actions and Calendar Alarms: Automation Triggers
Folder Actions and Calendar Alarms are for automatic, event-driven workflows. A Folder Action attaches to a specific folder and runs whenever files are added, renamed, or deleted. For example, you could set up a Folder Action that automatically converts any image dropped into a “To Convert” folder to JPEG. Calendar Alarms let you schedule a workflow to run at a specific time or when a calendar event occurs. This is useful for daily backups or generating reports at a set hour. Both require the workflow to be saved in the appropriate format, and they run in the background without user interaction.
How to Choose the Right Workflow Type
To decide which type to use, ask yourself three questions:
- How do I want to start it? If you want to click a button in Automator, use Workflow. If you want to double-click an app or drop files onto it, use Application. If you want a right-click menu option, use Quick Action. If you want it to run automatically, use Folder Action or Calendar Alarm.
- Does it need input? If it needs selected files or text, Quick Action or Application (with drag-and-drop) are the best. Workflows can also accept input, but you have to select it within the workflow itself.
- Do I need to share it? Applications are the easiest to share because they are self-contained. Workflows require the recipient to have Automator, and Quick Actions are installed on a per-user basis.
Common Mistakes and Troubleshooting
One common mistake is saving a workflow as a Workflow and expecting it to run by double-clicking. It won’t—it opens in Automator. Another is using an Application with actions that require a specific input type, but then dragging a file that doesn’t match (e.g., an action that expects images, but you drag a PDF). Automator will either throw an error or skip the action. Also, Quick Actions often appear grayed out if the selected item’s type doesn’t match the action’s input. For example, a Quick Action that expects text won’t work on a file selection.
If a Folder Action doesn’t run, check that it’s enabled in the folder’s “Folder Action Setup” (right-click the folder → Folder Actions Setup). For Calendar Alarms, ensure the calendar exists and the workflow is saved as a Calendar Alarm type.
Frequently Asked Questions
Can I convert a Workflow to an Application later?
Yes. Open the workflow in Automator, then go to File → Convert To → Application. This creates a new .app file with the same actions. You can also convert to Quick Action or other types from the same menu.
Why is my Quick Action not showing up in the context menu?
Quick Actions are only shown when the selected item matches the input type of the first action. For example, if your Quick Action expects image files, it will only appear when you right-click an image file. Also, check that the Quick Action is enabled in System Settings → Privacy & Security → Extensions → Finder.
Can an Application run without Automator installed?
Yes, an Application is a standalone executable. It does not require Automator to be installed on the system. However, it does require macOS, and some actions may depend on other apps (like Preview or Mail) being present.
What is the difference between a Quick Action and a Workflow?
A Workflow runs only inside Automator, while a Quick Action is a service that appears in the context menu and can be triggered with a keyboard shortcut. Quick Actions are also more integrated with the system, but they are limited to receiving the selected item, whereas a Workflow can run with no input or with input you specify within the workflow.
Can I schedule a Workflow to run automatically?
Yes, by saving it as a Calendar Alarm. You can then create a calendar event to trigger it, or use the “Repeat” feature in the calendar to run it daily, weekly, etc. Alternatively, you can use a third-party tool like launchd, but that’s beyond Automator’s scope.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.
More cards in this drawer
- Arctic Sea Ice Forecasts Disagree: What to Do
- MySQL Workbench to VPS: SSH Tunnel Setup
- Bluesky Beginners Guide: How to Get Started5.00 min/km
- LG V20 Won’t Turn On? Fixed
- Snagit vs Camtasia: Which One Do You Need?
- Scale a Small Business Without Losing Culture