⚠️WARNING: This may not work on Big Sur. See #26.

This is a workflow for anyone who uses Keyboard Maestro and wishes it had built-in Alfred support. In Alfred simply type km followed by the name of any of your KM macros.

Alfred 3 with Powerpack and Keyboard Maestro 6.3 or greater. If you don't have them, go get them immediately. You will not regret it.

• Alfred (Free, but requires £17 Powerpack)
• Keyboard Maestro (Free to try. $36/license)

Both well worth the cost.

Download the file directly, then double-click Alfred Maestro.alfredworkflow file to install.

You can also compile and install this workflow from sources. It's written in Go, so you should install it first.

1. Clone this repository
2. Install AwGo library: go get github.com/deanishe/awgo
3. Run make pack
4. Double-click Alfred Maestro.alfredworkflow file to install the workflow.

Type km followed by the name of any of your defined macros. Use ⌘ modifier to reveal the macro in Keyboard Maestro.

I also wrote a blog post on how I personally use this workflow for anyone who's interested: Integrating Alfred and Keyboard Maestro

Thanks to Peter Lewis of Stairways Software, the creator of Keyboard Maestro for adding a feature to KM that greatly increased the power of this workflow. Now Alfred can launch any of your macros, not just the ones with a hotkey!

Important: If you have macros that you only want to run in certain applications read this.

If you create a macro group that is not set to run in all applications you will need to make sure it is set to run in Alfred in addition to whatever application you want it to run in. See issue 5 for details.

If you're using macOS Mojave and get the following error, it's very likely that Alfred doesn't have access to Keyboard Maestro. First, make sure that Alfred has all needed access to your system. Then check that Alfred could access Keyboard Maestro. If after that Alfred still doesn't show you your macros ping us in #22 and we'll try to help you.

If you are having trouble, feel free to open an issue. I try to check up on it regularly. Alternatively, ping me on Twitter: @ian_sinn