How to Restore macOS Automation Chains After System Update Broke Shortcuts + Hazel + Alfred Integration

by
PinLinkedIn

Ever had your perfect macOS automation setup crumble after a system update? Yep, you’re not alone. One day everything works smoothly—Hazel files dropping into place, Alfred commands flying, Shortcuts dancing to your tune—and the next? Total chaos. But don’t worry! We’ll fix it all together step by step, and even have a little fun along the way.

TLDR

System updates can break automations between apps like Shortcuts, Hazel, and Alfred. Check permissions, reauthorize apps, and re-link everything. Use this guide to walk through the repair process. Backup everything before updating in the future.

What Probably Broke

Let’s quickly go over what likely happened. A macOS update can:

  • Revoke app permissions
  • Reset file paths
  • Disable scripts and automations
  • Add new sandboxing limitations

That means your carefully connected automation chain might fall apart. Hazel might not trigger. Shortcuts may throw an error. Alfred workflows? Missing in action. 😤

First Things First: Design a Simple Map

Before we dive into fixing, take a moment to sketch your automation workflow. It doesn’t have to be fancy. Even a sticky note works!

For example:

  • Hazel: Watches Downloads folder → Moves PDFs to “Invoices”
  • Shortcuts: Converts PDF into text → Uploads to Notes
  • Alfred: Runs the Shortcut via keyword trigger

This will give you clarity on where things are broken!

Meet Alfred homepage

Step 1: Check App Permissions

System updates often lock things down. Time to unlock them again:

  1. Go to System Settings → Privacy & Security
  2. Open Full Disk Access and make sure all your automation apps (Hazel, Alfred, Shortcuts, etc.) are enabled
  3. Check Automation permissions too and re-enable where needed
  4. Reboot your Mac for good measure 🔁

After rebooting, re-test one piece of your chain. Does Hazel still trigger?

Step 2: Reconnect Alfred Workflows

Sometimes Alfred loses connection with other apps. If you use it to launch Shortcuts, do this:

  1. Open Alfred Preferences
  2. Navigate to your Workflows
  3. Check any Script or AppleScript blocks – these sometimes reference outdated paths
  4. Update them with the new ones if needed

Example updated AppleScript:

tell application "Shortcuts Events"
	run the shortcut named "Process PDF to Notes"
end tell

Make sure Shortcuts Events has automation permission under Security & Privacy.

Step 3: Reauthorize Shortcuts

macOS loves to break Shortcuts after updates. Luckily, the fix is easy:

  • Open Shortcuts app
  • Manually run each shortcut you’ve integrated to re-prompt permissions
  • Grant access wherever macOS asks

If you see nothing happening, open Console.app and filter for “Shortcuts” — you might spot what’s stopping your shortcut.

Step 4: Hazel Rules Not Working?

Hazel depends heavily on permissions and folder watching. Here’s how to reset it all:

  1. Open Hazel Preferences
  2. Review each folder’s rules
  3. Make sure the folder path still exists and matches your pre-update arrangement
  4. Test rules individually by dropping test files into watched folders

Also check this:

  • Hazel must be granted Full Disk Access
  • Automation access must be approved to run scripts, call Shortcuts, etc.

Step 5: Fix File Paths!

Shortcuts and Hazel both rely on specific file paths. Updates may rename or relocate user directories. Sneaky!

Here’s what to do:

  • Open broken Hazel rules or Shortcut actions that deal with files
  • Manually reassign folder locations even if they look the same
  • Test again with sample files

Also, tip: avoid using absolute paths (like /Users/you_name/Desktop) and instead use more dynamic references when available.

Step 6: Logs Are Your Friends

If you’re still stuck, dig into logs:

  • Open Console.app
  • Search for keywords like Hazel, Shortcuts, Alfred
  • Look for red flags—errors, denied permissions, or failed actions

You’ll be surprised how often logs point right at the problem.

Bonus Tip: Use Universal Actions

Newer versions of macOS now let you chain actions through Universal Shortcuts. Try building parts of your automation here instead of just Hazel or Alfred.

For example:

  • Use a Shortcut as a middle layer to translate Hazel output into Alfred input
  • Let Shortcuts write log files Hazel can watch

Think of it like automation glue—it connects the tools when direct paths break.

Step 7: Make a Tester Shortcut

Before going live with your full chain, test with a simple one:

  1. Create a Shortcut that just says “Hello World” using a notification action
  2. Trigger it via Alfred
  3. Trigger it via Hazel using AppleScript or shell script

If all three work, you now have proof the pipes are connected again!

Step 8: Backup Everything (Seriously)

Now this part is crucial:

  • Export Hazel rules one by one (there’s no batch option 😩)
  • Backup Alfred workflows (right-click → Export)
  • Use iCloud for Shortcuts, or manually export via the sharing button

Store backups in a folder outside your system disk—think cloud drive or external SSD.

Wrapping It All Up

Whew! That’s a lot, but you made it. Once you’ve reconnected Shortcuts, re-plugged Alfred paths, and re-authorized Hazel, your automation empire will rise again! 🎉

Remember, with every system update, there’s a chance something could break. But with this guide and a little patience, you’ll be back to automating like a wizard in no time.

Summary Checklist

  • ✔️ Re-enable permissions in Privacy & Security
  • ✔️ Run each Shortcut manually to reauthorize
  • ✔️ Confirm Hazel rules & folder paths still exist
  • ✔️ Restitch Alfred workflows with updated scripts
  • ✔️ Use logs to find hidden errors
  • ✔️ Backup everything for the future

You’re not just restoring automations—you’re building resilience. 🚀

PinLinkedIn