Keyboard Maestro on a Mac: automating the clicks you repeat

The same eleven clicks happen every Monday morning. Open the reporting tool, switch to the right account, set the date range, export, rename the file, drop it in the right folder, paste a summary into a document. Nothing about it is difficult and nothing about it can be skipped, which is exactly the shape of work a Mac can be made to do without supervision.

Keyboard Maestro is the oldest and most capable answer to that on macOS, and it is also the one people bounce off fastest. The reason is usually that it gets treated as a hotkey utility, which is like treating a spreadsheet as a calculator. Understanding two concepts, triggers and macro groups, is the difference between abandoning it in a week and building something that still works in three years.

What it is, in its own terms

The description on the product site is direct about scope:

Automate applications or web sites, text or images, simple or complex, on command or scheduled. You can automate virtually anything. Source: keyboardmaestro.com

The current release is version 11.1.1, from Stairways Software, a company whose copyright notice on that page runs from 1990. That matters for a tool meant to hold a decade of accumulated automation, because the risk with automation software is not that it fails to work today. It is that it disappears and takes the work with it.

The building block is a macro, and a macro is two halves. One or more triggers decide when it runs. A sequence of actions decides what it does. The product site describes the action library as "hundreds of built-in actions" that combine with "flow control, conditions and looping actions," which means the sequence is a small program rather than a recorded set of clicks. That distinction is why macros survive an interface redesign that would break a click recording.

Keyboard Maestro requires macOS 10.13 High Sierra or later and runs natively on Apple Silicon. For anyone deliberately staying on an older system, the site links to older versions.

Triggers: the part most people never explore

A hotkey is the trigger everybody starts with, and it is one of roughly thirty-seven that the documentation lists. Reading the list is the fastest way to understand what the tool is for, because most of the useful automations start from something other than a keystroke.

The documented triggers include the Hot Key trigger and the Typed String trigger, which fires when a chosen sequence of characters is typed. Beyond those there is an Application trigger, for macros that run when a particular app launches, activates or quits, and a Focused Window trigger for reacting to which window is in front. Time gets three: a Time of Day trigger, a Periodic trigger, and a Cron trigger.

Hardware and system events get their own set. A Folder trigger watches a directory for new files. A Mounted Volume trigger fires when a disk appears. There are USB Device and USB Device Key triggers, a MIDI trigger, a Wireless Network trigger, a Power Status Changed trigger, and Sleep, Wake, Login and Unlock triggers. A Display Layout Changed trigger covers the moment a laptop is connected to an external monitor, which is the natural home for window arrangement macros.

Then there are triggers meant for being called rather than for happening: a Subroutine trigger, a URL trigger, a Remote trigger, a Public Web trigger, and a trigger from the keyboardmaestro command line tool added in version 11.

The practical lesson is that the question to ask is not "what shortcut should this be." It is "what already happens at the moment this should run." Connecting to the office network, plugging in a monitor, a file landing in a folder: those are better triggers than a keystroke, because they do not have to be remembered.

Macro groups are the feature that makes it survivable

At twenty macros, Keyboard Maestro is a list. At two hundred, without groups, it is a conflict. Macro groups are the organising layer, and the documentation notes that groups control their activation status across applications and windows.

That sentence is the whole design. A group can be active only while a specific application is in front, which means the same key combination can do different things in a mail client, a spreadsheet and a browser, because only one group is active at a time. Shortcut namespace, in other words, stops being global and becomes contextual.

Two consequences follow. The first is that a hotkey no longer needs to be exotic. A single unmodified key can be a trigger inside a group scoped to one application, which is why heavy users end up with simpler shortcuts rather than more baroque ones. The second is that scoping is also safety. A macro that deletes rows should be unable to fire anywhere except in the one application where deleting rows is meaningful, and a group scoped to that application enforces it.

Clipboard History sits alongside this as the feature that justifies the purchase for people who never write a macro at all. The documentation states that Clipboard History "is optionally saved across logins and restarts," which makes it a searchable record of what was copied rather than a buffer that empties on reboot.

The permissions conversation

Anything that can press keys and read windows on behalf of a person needs system permissions, and macOS asks for them one by one. Version 11 added a Security Settings pane specifically to show the current status of the various system permissions the app relies on, which turns a class of silent failure into something visible.

That pane is the first place to look when a macro that worked last month stops doing anything. A system update, a migration to a new Mac or a restored backup can leave the permissions revoked while every macro still looks correct, and the symptom is a macro that runs and accomplishes nothing rather than an error.

What it costs

The pricing is unusual enough in 2026 to be worth stating plainly.

Item	Price
New licence for version 11	"US$36 * plus applicable tax"
Upgrade from any previous version	"US$25 * plus applicable tax"
Purchases made since 1 March 2023	Free upgrade to version 11
Ongoing cost	"Keyboard Maestro 11 is a one-time purchase. No subscription"

The site states that version 11 can be purchased "and use version 11 indefinitely," with a major upgrade released every couple of years and charged for separately. A free trial is offered from the same page.

For comparison with the subscription tools that occupy the same part of a working day, a one-time 36 dollars with an occasional 25 dollar upgrade lands well under a year of most monthly plans. What the money does not buy is a gentle beginning. There is a user manual, a wiki and an active forum, and the tool expects a reader.

Where it sits next to Shortcuts, Automator and launchers

These get compared as though they were competing, and they overlap less than that.

Tool	Strongest at	Weakest at
Keyboard Maestro	Reacting to system and application events, conditional multi-step sequences, contextual hotkeys	Nothing to learn on day one. No mobile counterpart
Apple Shortcuts	Actions that apps publish deliberately, and sharing the same shortcut with iPhone and iPad	Reaching into an app that publishes nothing
Automator	Simple file and Finder workflows that already exist and still run	Triggers. It mostly waits to be run
App launchers	Opening things and running quick commands fast	Long conditional sequences and event-driven work

Apple's own framing of its tool is modest by comparison. The Shortcuts user guide for Mac defines a shortcut as "a quick way to get one or more tasks done with your apps," and the strength of that model is that actions are published by the app. Where an app publishes good actions, Shortcuts is the cleaner choice and it travels to a phone.

Keyboard Maestro's territory is the opposite case: software that publishes nothing, where automation has to be built from window titles, menu items, clipboard contents and keystrokes. Most business software falls into that category, which is why the two tools coexist on the same Mac rather than replacing one another.

Automating web apps, and why tabs make it harder

A large share of the repeated work on a modern Mac happens inside web applications, and the product site names this directly, listing filling in web forms, visiting commonly read pages and downloading reports or bank statements among the things it can do.

The obstacle is not the automation. It is addressing the target. Macro groups activate by application and by window, so a macro can be scoped precisely to one application. A browser with fourteen tabs is one application, and the reporting tool is not an application at all. It is a tab whose position changes hourly, inside a window that also holds unrelated work. Every macro then begins with the fragile part: find the right tab, confirm it is the right account, and only then do the actual work.

Giving each web application its own window changes what a macro can rely on. A browser that keeps each web app in its own window turns the reporting tool into a named, addressable window with its own session, which means an Application trigger or a group scoped to that window has something stable to attach to. The macro can start at the work instead of starting at the search. Arranging the accounts this way is what workspaces are for, and the supported apps list is the place to check whether a specific service behaves well in a window of its own.

This is also where the multiple-account version of the problem shows up. Two accounts on the same service inside one browser session are indistinguishable to a macro, because the thing that differs is a cookie rather than a window. Separate windows with separate sessions make the distinction visible to automation, not just to the person at the keyboard.

What to build first

Three macros are enough to decide whether this tool belongs on a particular Mac, and they should be built in this order.

Start with a Typed String trigger that expands an abbreviation into something long and exactly worded: a bank account block, a support reply, a meeting address. It takes five minutes and it pays back immediately.

Second, build a Display Layout Changed macro that arranges windows when an external monitor connects. It demonstrates the value of an event trigger over a remembered keystroke better than any explanation.

Third, take the Monday morning report and automate only the middle of it, leaving the opening and the final judgement to a person. Partial automation of a reliable sequence beats full automation of a fragile one, and it is the honest test of whether the remaining clicks are worth 36 dollars.

What to change first

Download the trial, build the text expansion macro, and then spend the remaining time on the trigger list rather than on actions, since that is where the leverage is. If the work being automated lives in web applications, give those applications their own windows before writing macros against them, which is the arrangement SpaceDeck is built to provide.