One path leads to larger enterprise providers that depend on consultative services to automate processes. Perhaps the best example of this is The Omni Group’s rich JavaScript-based automation, which lets scripts control Omni’s apps-on iPad, iPhone, or Mac.Within the robotic process automation (RPA) landscape, there are typically three automation paths. On iOS, apps with this level of control tend to use a self-implemented macro engine based on JavaScript or Python. That’s an important part of the user automation story, but another part is the ability to deeply control powerful apps via scripting. The truth is, most automation on iOS has been about building workflows using little pieces of different apps. But Apple has recently been modernizing with features such as Siri Intents. Passing URLs back and forth became the standard method of communication, believe it or not. This leads us to the bigger question: What happens to AppleScript and the Apple Events technology that has kept inter-application communication alive on the Mac for decades? iOS doesn’t have an equivalent to Apple Events. What about the other scripting languages? (I use Homebrew to do it.) On the other hand, if you’re building an automation that relies on one of those scripting languages, you’ll need to install them on any Mac that you want to automate. This is no big deal on one level: you can still install the latest versions of PHP, Perl, and Python on macOS. In macOS Monterey, PHP has already departed, and Perl and Python are older versions that will be removed soon enough. Apple has committed to no longer including common Unix scripting systems with macOS. Shortcuts on the Mac also goes beyond what’s available on iOS and iPadOS by being able to hook directly into Unix scripting and shell support-with one big catch. The Shortcuts app debuted on iOS and was a hit.

Power automate on mac