Mojave security

I have an Automator workflow that runs a shell script. I’m using Keyboard Maestro to trigger it periodically. It’s been working fine, but after upgrading to Mojave with its stricter security model, I get an error message when it is run. Giving it full disk access solves the problem, but which application should I give this privilege to? When I give full disk access to Terminal, I can run the shell script manually. When I give full disk access to Automator, I can run the workflow from there. But I have tried giving full disk access to Keyboard Maestro and its engine, and I still get the error message when running the macro manually and having it triggered at the specific time.

Why not just run the shell script directly from KM, using an Execute a Shell Script action?

Thanks for the suggestion. I hadn’t thought about that! I made this workflow in Automator originally, and when I wanted to run it periodically, I first tried crontab and then Keyboard Maestro. Today I replicated the functionality from Automator inside of the KM macro, and I got it to work.

1 Like