Alfred workflows worth keeping when files are the work

Searching for Alfred workflows returns galleries with hundreds of entries, and the usual outcome is a dozen installed in an evening and two still triggered a month later. That is not a failure of the gallery. It is that the question being answered is the wrong one. The useful question is not which workflows exist, it is which ones survive contact with a working week, and the answer depends much more on what you already do than on what the workflow can do.

For anyone whose day is mostly files, folders and commands against them, the shape of a workflow that lasts is fairly predictable, and a surprising number of popular ones duplicate something Alfred already does natively.

What actually sits behind the Powerpack

Workflows are a Powerpack feature, and so are several things people assume come with the free app. Clipboard history for text, images and file paths. Snippets with automatic expansion from a keyword. File Filters for custom search scopes. The Text View and Grid View workflow objects. The View in Alfred universal action that previews Markdown, images, PDFs and text files.

The licence is a one time purchase. The Single Licence reads at 34 pounds and the Mega Supporter option at 59 pounds with free lifetime upgrades, both for a single user, and both are listed as Alfred 5 licences. The buy page currently states that a purchase now includes a free upgrade to Alfred 6, which the site announces for this autumn. That combination matters for timing: buying in the weeks before a major version is usually the moment to hesitate, and here the vendor has removed the reason to.

Workflows themselves are built by connecting objects, described as building blocks, without writing code. They can be triggered by a hotkey, by a keyword, or by a button in Alfred Remote on an iPad. For anything more elaborate, list filters, script filters and JSON output are the documented routes for feeding results back in.

The shape of a workflow that survives

Three properties separate the ones still in use after a month from the rest.

It replaces a sequence, not a capability. A workflow that saves four keystrokes on something done twice a day earns its keyword. A workflow that does something impressive you might need quarterly will be forgotten before the quarter ends.

It starts from something already selected. This is what Universal Actions are for, and it inverts the usual order: choose the file, the text or the link first, then decide what happens to it. Alfred ships over 60 default actions, from copying to the clipboard and saving a snippet to extracting URLs from a block of text, and it narrows the list to actions that make sense for the type of thing selected. The default hotkey is Command and slash, and the feature needs Accessibility permission granted before the hotkey works, which is the usual reason it appears to do nothing on a fresh install.

It ends somewhere visible. A workflow whose result lands in a file you then have to go and find has moved the work rather than removed it. This is where the view objects matter: a scriptable, editable text window with Markdown and image support, or a thumbnail grid, both keep the result in front of you.

The file features that are not workflows at all

A large share of file related workflows in circulation reimplement things already in the preferences.

Alfred's default results cover applications, system settings, contacts and any file types added to that list. Beyond them, three keywords do the heavy lifting: one to open a file, with the space bar as a shortcut for it, one to reveal a file in the Finder, and one to search inside file contents rather than names. All three keywords are editable, the file types shown can be restricted, and the number of results is configurable.

Navigation is separate from search. Typing a slash jumps to the root of the disk and a tilde to the home folder, after which you walk down the tree by typing the first characters of each folder. The File Buffer collects several files as you go, so a set can be assembled and then acted on together.

For Powerpack users, File Filters are the native way to build a custom scope: a saved search restricted by file type, by location, or both. A filter for one client folder, invoked by three letters, is usually better than any general purpose workflow doing the same job, because it has no dependency to break when macOS or Alfred updates.

The practical advice from all of this is to configure before installing. Anything that could be a File Filter, a default results setting or a universal action is better as one of those.

Five kinds of workflow that keep earning their place

The job	Where it belongs	Why
Reaching one project's files instantly	A File Filter in preferences	No external dependency, no keyword to forget
Running a command against the selected file	A universal action into a shell step	Starts from the selection instead of retyping a path
Reusing text you type constantly	Snippets with auto expansion	Clipboard history can promote a clip into a snippet with Command and S
Checking a result before acting on it	A workflow using Text View or Grid View	Markdown, images and PDFs preview without leaving Alfred
Triggering something while away from the keyboard	Alfred Remote on an iPhone or iPad	A button is easier to remember than a hotkey you use weekly

The last row is the one most people never set up. Alfred Remote is a separate iOS app that maps buttons on an iPhone or iPad to Alfred actions on the Mac, including workflows, app launches, system commands and pasting snippets. It is worth distinguishing from actually reaching into the Mac from an iPhone or iPad, which is a different capability with different requirements. Remote sends a trigger; it does not give you the machine.

Building one instead of installing one

The gallery is the obvious starting point, and it is also the reason many people never learn how cheap a bespoke workflow is.

The editor works by connecting objects. A trigger at the front, such as a hotkey or a keyword, then steps that transform or filter, then an action that does something. Alfred 5 added Automation Tasks, prebuilt steps for common macOS operations, so a workflow that renames, moves or converts something no longer starts with a blank script. The vendor describes the editor as higher performance and more accessible than before, which in practice means the graph stays readable past a handful of objects.

Three objects carry most bespoke file work. A list filter presents a fixed set of choices, which is how one keyword can stand in for five. A script filter runs a command and turns its output into Alfred results, which is the bridge for anything a shell already does well. JSON is the documented output format for that bridge, so any language that can print JSON can feed the list.

The reason to build rather than install is not pride. An installed workflow encodes someone else's folder layout, someone else's naming convention, and sometimes a dependency they installed years ago. A workflow built around your own two or three real paths has nothing to drift out of date, and it is usually twenty minutes of work.

The same logic argues against large general purpose workflows that try to manage files in the abstract. The specific one that knows exactly where your invoices go will still work next year.

Where the terminal boundary sits

For file work, the honest limit of Alfred is visible in its own terminal documentation, and it is worth understanding before building a workflow around it.

Prefixing a command with a greater than sign launches Terminal and runs the command. The prefix can be changed in preferences, and the macOS Terminal app is what is supported by default. Choosing the Custom option lets you supply your own AppleScript for terminal actions, wrapped between an alfred_script declaration and its end, which is how people point it at a different terminal application. For iTerm2 specifically, the documentation points to integration scripts maintained by a community member on GitHub rather than shipping them. Workflows can also launch a Browse in Terminal action, and the manual suggests workflows rather than the prefix for anything genuinely complex.

Read that again and the boundary is clear. Alfred launches a terminal. It does not hold one. The command runs in another application's window, the folder you were looking at is back in the Finder, and the output is in a third place. For a one shot command that is fine. For work that alternates between looking at a folder and running something against it twenty times an hour, the switching cost is the whole problem, and no workflow removes it because the workflow is not where the cost lives.

This is the distinction worth keeping in mind when comparing Mac tools that overlap in what they search. A launcher is optimised for getting to a thing. A file manager is optimised for staying with a set of things and acting on them repeatedly. Installing more workflows does not turn the first into the second.

When Alfred cannot find a file, it usually is not Alfred

This is the most common support thread and the answer sits in Alfred's own troubleshooting documentation.

There is a built in file troubleshooter under Help, in the Troubleshooting section. It runs against a file you drop into it and attempts to diagnose why that file is not being found. The documented outcomes are telling: either the folder needs adding to Alfred's search scope, or there is a metadata warning or failure, which the documentation says will almost always be resolved by rebuilding the macOS metadata.

In other words, Alfred is reading the same index the rest of the system reads. When search goes wrong, the question is whether the index has the file, not whether the launcher is configured correctly, and the tools that report on the index are part of macOS rather than part of Alfred. That also means a folder excluded from indexing to stop a fan spinning disappears from Alfred at the same time, which is a trade worth making deliberately rather than discovering later.

Keeping the set small on purpose

The Gallery makes installation and updates safe and easy, which is exactly why collections grow past the point of usefulness. Two habits keep it under control.

Review the list on a fixed cadence and delete anything not triggered in the last month. A workflow whose keyword you have to look up is costing more attention than it saves, and the cost is invisible because it shows up as hesitation rather than as failure.

Prefer one workflow that does three related things over three workflows that each do one, because the keyword is the scarce resource, not the workflow. A single keyword leading to a list of actions is easier to remember than three keywords with similar prefixes, and the list filter object exists precisely to make that pattern cheap to build.

The workflows that last, in practice, are the boring ones: a project scope, a command against the current selection, a snippet, a preview. They survive because they sit on top of something already being done daily rather than proposing something new.

What to change first

Before installing anything else, spend twenty minutes in preferences: one File Filter per active project, the Universal Actions hotkey set and Accessibility granted, and the three file keywords learned properly. Then look at what is left over, and if most of the remainder is running commands against folders you are already looking at, the missing piece is not another workflow but a window where the folder and the terminal sit together, which is what Atriens is for.