That means your carefully connected automation chain might fall apart. Hazel might not trigger. Shortcuts may throw an error. Alfred workflows? Missing in action. \ud83d\ude24<\/p>\n
First Things First: Design a Simple Map<\/h2>\n
Before we dive into fixing, take a moment to sketch your automation workflow. It doesn\u2019t have to be fancy. Even a sticky note works!<\/p>\n
For example:<\/p>\n
- \n
- Hazel<\/strong>: Watches Downloads folder → Moves PDFs to “Invoices”<\/li>\n
- Shortcuts<\/strong>: Converts PDF into text → Uploads to Notes<\/li>\n
- Alfred<\/strong>: Runs the Shortcut via keyword trigger<\/li>\n<\/ul>\n
This will give you clarity on where things are broken!<\/p>\n
![\"\"](\"https:\/\/savethevideo.net\/blog\/wp-content\/uploads\/2025\/12\/delivery-person-on-scooter-at-crosswalk-macos-automation-shortcuts-hazel-alfred-broken-chain.jpg\")
\nStep 1: Check App Permissions<\/h2>\n
System updates often lock things down. Time to unlock them again:<\/p>\n
- \n
- Go to System Settings<\/em> \u2192 Privacy & Security<\/em><\/li>\n
- Open Full Disk Access<\/strong> and make sure all your automation apps (Hazel, Alfred, Shortcuts, etc.) are enabled<\/li>\n
- Check Automation<\/strong> permissions too and re-enable where needed<\/li>\n
- Reboot your Mac for good measure \ud83d\udd01<\/li>\n<\/ol>\n
After rebooting, re-test one piece of your chain. Does Hazel still trigger?<\/p>\n
Step 2: Reconnect Alfred Workflows<\/h2>\n
Sometimes Alfred loses connection with other apps. If you use it to launch Shortcuts, do this:<\/p>\n
- \n
- Open Alfred Preferences<\/strong><\/li>\n
- Navigate to your Workflows<\/em><\/li>\n
- Check any Script or AppleScript blocks \u2013 these sometimes reference outdated paths<\/li>\n
- Update them with the new ones if needed<\/li>\n<\/ol>\n
Example updated AppleScript:<\/p>\n
\ntell application \"Shortcuts Events\"\n\trun the shortcut named \"Process PDF to Notes\"\nend tell\n<\/pre>\n
Make sure Shortcuts Events has automation permission under Security & Privacy<\/em>.<\/p>\n
Step 3: Reauthorize Shortcuts<\/h2>\n
macOS loves to break Shortcuts after updates. Luckily, the fix is easy:<\/p>\n
- \n
- Open Shortcuts<\/strong> app<\/li>\n
- Manually run each shortcut you’ve integrated to re-prompt permissions<\/li>\n
- Grant access wherever macOS asks<\/li>\n<\/ul>\n
If you see nothing happening, open Console.app<\/em> and filter for “Shortcuts” \u2014 you might spot what’s stopping your shortcut.<\/p>\n
Step 4: Hazel Rules Not Working?<\/h2>\n
Hazel depends heavily on permissions and folder watching. Here\u2019s how to reset it all:<\/p>\n
- \n
- Open Hazel Preferences<\/strong><\/li>\n
- Review each folder\u2019s rules<\/li>\n
- Make sure the folder path still exists and matches your pre-update arrangement<\/li>\n
- Test rules individually by dropping test files into watched folders<\/li>\n<\/ol>\n
Also check this:<\/p>\n
- \n
- Hazel must be granted Full Disk Access<\/strong><\/li>\n
- Automation access must be approved to run scripts, call Shortcuts, etc.<\/li>\n<\/ul>\n
![\"\"](\"https:\/\/savethevideo.net\/blog\/wp-content\/uploads\/2025\/12\/a-computer-screen-with-the-number-99-on-it-macos-settings-antivirus-exclusion-time-machine-paths.jpg\")
\nStep 5: Fix File Paths!<\/h2>\n
Shortcuts and Hazel both rely on specific file paths. Updates may rename or relocate user directories. Sneaky!<\/p>\n
Here’s what to do:<\/p>\n
- \n
- Open broken Hazel rules or Shortcut actions that deal with files<\/li>\n
- Manually reassign folder locations even if they look the same<\/li>\n
- Test again with sample files<\/li>\n<\/ul>\n
Also, tip: avoid using absolute paths (like
\/Users\/you_name\/Desktop<\/code>) and instead use more dynamic references when available.<\/p>\nStep 6: Logs Are Your Friends<\/h2>\n
If you’re still stuck, dig into logs:<\/p>\n
- \n
- Open Console.app<\/strong><\/li>\n
- Search for keywords like Hazel<\/em>, Shortcuts<\/em>, Alfred<\/em><\/li>\n
- Look for red flags\u2014errors, denied permissions, or failed actions<\/li>\n<\/ul>\n
You\u2019ll be surprised how often logs point right at the problem.<\/p>\n
Bonus Tip: Use Universal Actions<\/h2>\n
Newer versions of macOS now let you chain actions through Universal Shortcuts<\/strong>. Try building parts of your automation here instead of just Hazel or Alfred.<\/p>\n
For example:<\/p>\n
- \n
- Use a Shortcut as a middle layer to translate Hazel output into Alfred input<\/li>\n
- Let Shortcuts write log files Hazel can watch<\/li>\n<\/ul>\n
Think of it like automation glue\u2014it connects the tools when direct paths break.<\/p>\n
Step 7: Make a Tester Shortcut<\/h2>\n
Before going live with your full chain, test with a simple one:<\/p>\n
- Search for keywords like Hazel<\/em>, Shortcuts<\/em>, Alfred<\/em><\/li>\n
- Open Console.app<\/strong><\/li>\n
- Automation access must be approved to run scripts, call Shortcuts, etc.<\/li>\n<\/ul>\n
- Navigate to your Workflows<\/em><\/li>\n
- Open Full Disk Access<\/strong> and make sure all your automation apps (Hazel, Alfred, Shortcuts, etc.) are enabled<\/li>\n
- Shortcuts<\/strong>: Converts PDF into text → Uploads to Notes<\/li>\n