
Mac Shortcuts can fail when they need permission to control another app, access files, or perform an action through macOS automation. The fix is usually to allow the Shortcuts app to control the affected app in System Settings > Privacy & Security > Automation, then run the shortcut again. You may also need to approve access to files, folders, accessibility features, or other protected data.
Quick Answer
- Open Apple menu > System Settings.
- Select Privacy & Security in the sidebar.
- Choose Automation.
- Expand Shortcuts and turn on permission for the app it needs to control.
- If the shortcut accesses files or folders, check Files and Folders and allow the required location.
- Quit and reopen Shortcuts, then run the shortcut again.
- If the permission does not appear, run the shortcut until it fails and look for a macOS permission prompt.
Automation permission is different from allowing an untrusted shortcut. A shortcut can be trusted and still lack permission to control another app.
Why Mac Shortcuts Need Automation Permission
A shortcut can do more than run actions inside the Shortcuts app. It may also ask another app to perform an action, such as:
- Creating or editing a note in Notes
- Sending a message through Messages
- Controlling music in Music
- Opening or modifying a document in another app
- Running an AppleScript or JavaScript for Automation
- Moving information between apps
- Controlling System Events or another background service
macOS treats this as automation because one app is controlling another. It blocks that access by default to protect your privacy and prevent unexpected changes.
When permission is missing, the shortcut may:
- Stop at a particular action
- Display an error saying it is not authorized
- Ask you to grant access to another app
- Complete without producing the expected result
- Show an action as unavailable or unable to run
The exact wording can vary depending on the action and the app involved.
For a general introduction to running and editing shortcuts, see How to Use Shortcuts on a Mac.
Allow Shortcuts to Control Another App
Use these steps when the error involves Shortcuts controlling a specific app.
- Open the Apple menu and select System Settings.
- Click Privacy & Security in the sidebar.
- Scroll down and select Automation.
- Look for Shortcuts in the list of apps.
- Click the disclosure arrow next to Shortcuts to expand its permissions.
- Turn on the switch for the app that the shortcut needs to control.
- Close System Settings.
- Quit the Shortcuts app. To do this, click Shortcuts in the menu bar, select Quit Shortcuts, or press Command-Q while Shortcuts is active.
- Reopen Shortcuts and run the shortcut again.
For example, a shortcut that creates a note may need permission for Shortcuts to control Notes. A shortcut that starts playback may need permission for Shortcuts to control Music.
If the app is not listed
An app often appears in Automation only after a shortcut tries to control it. If you do not see the required app:
- Open the shortcut in Shortcuts.
- Run it until it reaches the action that needs permission.
- If macOS displays a permission prompt, select the option that allows access.
- If no prompt appears, quit and reopen Shortcuts.
- Check System Settings > Privacy & Security > Automation again.
Some shortcuts use actions that do not require automation permission. In that case, the problem may instead involve file access, accessibility access, a damaged action, or an issue with the target app.
Check Files and Folders Permissions
Automation access does not automatically give a shortcut permission to read or write every file. macOS may separately protect folders such as Desktop, Documents, and Downloads, as well as files stored in iCloud Drive or on external drives.
If the shortcut saves, reads, moves, or deletes files, check its file access:
- Open System Settings.
- Select Privacy & Security.
- Click Files and Folders.
- Find Shortcuts in the list, if it appears.
- Expand Shortcuts and turn on access for the folder the shortcut uses.
- Close System Settings and try the shortcut again.
If the shortcut uses a file picker or asks you to choose a location, select the intended file or folder when prompted. Some actions also include an option to ask for a location each time, which can help you avoid hard-coded paths that no longer exist.
Be careful with delete and overwrite actions
Before granting access or rerunning a shortcut, review any action that can delete, replace, move, or overwrite files. A permission change can allow the shortcut to complete an operation that previously failed.
If the shortcut includes Delete Files, Move Files, or a save action that replaces an existing file, confirm the destination and filename first. Do not rerun it repeatedly if you are unsure whether part of the shortcut already completed.
For a shortcut specifically designed to save clipboard content, see How to Create a Shortcut That Saves Clipboard Text to a File on a Mac.
Check Accessibility Permission for UI-Control Shortcuts
Some shortcuts control an app by simulating clicks, keystrokes, or other user-interface actions. These shortcuts may require Accessibility permission rather than, or in addition to, Automation permission.
- Open System Settings.
- Select Privacy & Security.
- Click Accessibility.
- Look for Shortcuts or the app that performs the UI action.
- Turn on the relevant switch.
- Quit and reopen Shortcuts, then test the shortcut.
Only grant this permission when you understand what the shortcut does. Accessibility access can allow an app to interact with other apps and parts of the Mac interface.
If the shortcut uses a script or a helper app, that specific app may need permission instead of Shortcuts. Check the shortcut’s actions to identify which app is performing the interaction.
Reset a Stuck Automation Permission
Sometimes the permission appears to be enabled, but the shortcut still fails. A stale permission record or a changed app installation can cause this behavior.
First, try the least disruptive reset:
- Turn off the affected app under System Settings > Privacy & Security > Automation > Shortcuts.
- Quit Shortcuts and the app it controls.
- Reopen the target app.
- Reopen Shortcuts.
- Run the shortcut and allow access if macOS asks again.
If that does not work, turn the permission off, restart your Mac, and enable it again after running the shortcut.
Remove and reinstall the affected app only as a last resort
If the target app was replaced, moved, or reinstalled, macOS may treat it as a different application. This can leave the old permission associated with an app version that is no longer present.
Do not delete an app unless you know how to reinstall it and your data is stored safely. Removing an app can affect its settings, extensions, or locally stored data. Usually, quitting the apps and granting permission again is safer than reinstalling anything.
Confirm the Shortcut Is Using the App You Expect
A shortcut may fail because an action points to a different app than the one you authorized. This can happen after installing an alternative app, changing a default app, or editing a shortcut copied from another Mac.
Open the shortcut and inspect the action that fails:
- Confirm the selected app, account, folder, or document.
- Check whether the action refers to an old file or location.
- Remove and add the affected action again if its app selector is blank or incorrect.
- Save the shortcut and run it from the Shortcuts app.
If the shortcut always stops at one action, the problem may be with that action rather than permissions. How to Fix a Mac Shortcut That Stops at a Specific Action covers a broader process for isolating a failing step.
Check for Untrusted Shortcut Restrictions
Automation permission and shortcut trust are separate controls.
If macOS says the shortcut is untrusted, you must address that warning before it can run. Open Shortcuts, locate the shortcut, and follow the approval instructions shown by macOS. Do not enable or run a shortcut unless you understand where it came from and what its actions do.
Granting automation access does not make an unknown shortcut safe. Review actions that send data, access files, run scripts, or communicate with online services.
For steps focused on this separate issue, see How to Allow an Untrusted Shortcut to Run on a Mac.
Troubleshooting Automation Permission Errors
The Automation section does not show Shortcuts
Run the shortcut until it reaches the action that controls another app. Then reopen System Settings > Privacy & Security > Automation. The entry may not appear until macOS records an attempted request.
The switch turns on but the shortcut still fails
Quit and reopen both Shortcuts and the target app. If the problem continues, turn the permission off, restart the Mac, and grant it again.
Also verify that the shortcut needs Automation permission. If it accesses a protected folder, check Files and Folders. If it simulates clicks or keystrokes, check Accessibility.
macOS keeps asking for permission
Repeated prompts can indicate that the permission was not saved, the app changed, or the shortcut is calling a different app each time. Check the target app shown in the prompt and authorize the correct one. Then quit and reopen the apps.
The shortcut works manually but fails from a menu bar, keyboard shortcut, or automation
Run the shortcut directly from the Shortcuts app first. If it works there, the trigger may be running under a different context or may not provide the same input.
Check the shortcut’s trigger settings and make sure the required app is open and available. A shortcut that expects selected files, clipboard text, or an active document may fail when launched without that input.
The shortcut can read a file but cannot save one
Reading and writing may require different access. Check the destination folder under Files and Folders, confirm that the destination is writable, and make sure another app is not locking the file.
A script action fails even after permission is enabled
Review which app actually runs the script. A script may involve Shortcuts, Script Editor, Terminal, System Events, or the target app. Each involved app may require its own permission under Automation or Accessibility.
Avoid granting broad permissions until you know which app needs them.
Frequently Asked Questions
Is Automation permission the same as Accessibility permission?
No. Automation allows one app to control another app through supported automation features. Accessibility can allow an app to control the user interface, including simulated clicks and keystrokes. A shortcut may need one or both.
Why can’t I find Shortcuts in Privacy & Security?
Shortcuts may not appear until a shortcut attempts to control another app. Run the shortcut until it fails, then check Automation again. For file or interface access, check Files and Folders or Accessibility instead.
Should I allow Shortcuts to control every app?
No. Allow only the apps required by the shortcut. Limiting permissions reduces the chance of unintended changes and makes it easier to understand what the shortcut can do.
Will resetting permissions delete my shortcuts?
Turning an Automation, Files and Folders, or Accessibility switch off does not delete the shortcuts themselves. However, review any shortcut that changes files or app data before rerunning it.
Why does a shortcut work on one Mac but not another?
Permissions are managed separately on each Mac. The shortcut may also use different apps, file locations, accounts, or installed components. Recheck the required permissions and the action settings on the Mac where it fails.
Can I fix the problem by reinstalling Shortcuts?
Usually, no. Shortcuts is part of macOS, and most permission failures are fixed through System Settings > Privacy & Security. Reinstalling or changing apps may create additional permission records rather than solve the underlying issue.
Final Thoughts
When a Mac shortcut fails because of automation permissions, start with System Settings > Privacy & Security > Automation and allow Shortcuts to control only the app it needs. Then check Files and Folders for protected locations and Accessibility for shortcuts that control the interface. Restart the affected apps, review any file-changing actions, and test the shortcut directly from Shortcuts before using its regular trigger again.