Automating Everyday Work on a Mac

Most of the work a computer does is repetition wearing different hats: the same files renamed the same way, the same report built from the same numbers, the same three applications opened in the same order every morning. Automation is the habit of handing that repetition to the machine itself. On a Mac the options span twenty years of platform history, from a friendly new app to a scripting language older than some of its users, and the craft lies in matching the tool to the job rather than learning all of them.

What automation means on a Mac

An automation is a small instruction, or a chain of them, that the Mac executes without further attention. Rename two hundred photos, move yesterday's downloads into project folders, resize images for a client, open the morning's set of tabs and documents. The Mac offers more ways to build these than any of its rivals, a blessing that can read as clutter: several doors lead into one room. This guide describes each door and the kind of job that justifies walking through. The scheduling side of the same question, when an automation should run by itself at set times, has its own dedicated retrospective built around the MacAT story.

Shortcuts, the friendly front door

Shortcuts arrived on the Mac with macOS Monterey in 2021, carrying ideas polished on iPhone and iPad for years. A shortcut is built from actions, drag and drop blocks that each do one thing: find files, rename them, get text from the clipboard, ask for input, run a shell script. The app reads plainly enough that a careful beginner can build something useful in an evening, and shortcuts can be pinned to the menu bar, run by voice, triggered from the Dock, or scheduled. It absorbed the old Automator concepts, so workflows built in the 2010s often have a direct Shortcuts equivalent now. For personal routines, tidying downloads, resizing images for email, generating a dated folder for a new job, it is the first tool to try. Apple's own Shortcuts user guide for Mac is the reference to keep open on a second screen.

Automator and folder actions, the old hands

Before Shortcuts there was Automator, introduced with Tiger in 2005, and it still runs. Its interface is a vertical list of actions forming a workflow, saved as an application or a service, and its quiet superpower is the folder action: drop a file into a chosen folder and an attached workflow runs on it immediately. Photographers have used folder actions for two decades to sort and rename imports the moment they land. Automator shows its age in small ways, an interface that predates the retina era, actions that have not been updated in years, but for folder watching jobs it remains a plain and dependable mechanism, and workflows can be invoked from the Services menu of any application. A reader who meets it for the first time should think of it as a working vintage tool rather than a dead one, in the same spirit this magazine reads the older software of the platform.

AppleScript, the local language

Underneath both sits AppleScript, the Mac's own scripting language since the early 1990s, and one of the odd treasures of the platform. Its syntax was designed to read like stiff English, tell application "Finder" to empty the trash, so that a non programmer could hold a conversation with the system. That ambition was only ever half realised, but what AppleScript does uniquely well is application control: because it is woven into the Mac's interapplication messaging, a script can drive applications that have no other scripting surface, telling a database application to run a query, a word processor to reformat a document, an invoicing tool to export a month. Any automation that must reach inside a long established Mac application will eventually meet it. The scripts are saved as plain text files, they run from the Script Menu in the menu bar, and they age well because the language has barely changed in thirty years.

The shell, for the things beneath the desktop

The fifth door is the one professionals forget is open: the Unix shell underneath macOS. A dozen lines in a shell script, run from the Terminal or triggered on a schedule, will outperform a graphical tool for anything involving batches of files, text transformation, or talking to servers. Renaming, resizing, compressing, synchronising folders, scraping a log for one line: these are the shell's home ground, and the Mac ships with the full standard toolkit. Shortcuts knows this and offers a run shell script action, which makes the two layers compose: the friendly app on top, the terse engine underneath. The first hour in that engine room is covered by the Terminal basics guide, written for exactly the reader who has never opened it.

How to choose without learning everything

The choice reduces to three questions. Is the job personal or does it involve the whole system? Personal work leans Shortcuts, system level routines lean the shell or launchd. Does the job involve files arriving in a place, or work you start yourself? Arriving files suggest a folder action; started work suggests a shortcut or a service. Does the job need to reach inside an application that has no scripting hooks the modern tools can see? Then AppleScript, possibly wrapped inside a Shortcuts run script action so the friendly front door still opens onto it. A database administrator automating exports will use a different door than a photographer, and both differently from an office manager assembling a monthly report; the options around data work specifically are surveyed in the database client guide.

A first automation worth building

Start with something real but small, and take it to the end. A good first project: a shortcut that takes the selected files, renames each with today's date and a chosen prefix, and moves them into a folder it creates if needed. It exercises input, variables, a loop and an output, and it fails safely: the worst case is files renamed in a way no one likes, undone by hand in a minute. Build it in Shortcuts first, and if the appetite grows, rebuild it as a shell command to see the same job done in one line. The habit to avoid is building a cathedral immediately: automations are best grown like a garden, one plot at a time, each one earning its keep before the next is dug.

What automation does to a working day

The honest payoff of automation is not speed but steadiness. A renamed batch of files is never named three different ways; a scheduled backup never depends on remembering, the point the backup guide makes about restores; a sorted downloads folder never becomes an archaeology project. Twenty years ago the users of this domain's software built the same habits with cron style schedulers and AppleScript, as the shareware record shows, and the ones whose machines seemed to run themselves were simply the ones who had handed over the boring parts. The tools have turned over completely since; the instinct has not changed at all.