Study guide
9.3 macOS Automation: Native Apps, Office Apps & AppleScript
UiPath Automation Developer Professional UiPath-ADPv1
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & Blueprint Map
1.1 About the UiPath-ADPv1 Exam: Format, Fees & Policies 1.2 The Exam Topics Mapped to This Guide & a Study Plan
2 Chapter 2: REFramework Architecture & State Dynamics
2.1 State Machine Architecture & The Four Core States 2.2 Configuration Management: Settings, Constants, and Assets 2.3 Transaction Types & The Dispatcher vs. Performer Architecture 2.4 Adapting REFramework: Tabular Data, Collections & Linear Processes
3 Chapter 3: REFramework Exception Handling & Recovery
3.1 BusinessRuleException vs. System.Exception Handling Patterns 3.2 Retry Mechanisms: Queue Retries vs. REFramework MaxRetryNumber 3.3 Consecutive System Exceptions & Graceful Process Termination
4 Chapter 4: State Machines, Custom Log Fields & REFramework Testing
4.1 Building State Machine Projects in Studio 4.2 Logging Levels, Robot Logs & Custom Log Fields in REFramework 4.3 Testing a REFramework Project With and Without Orchestrator Queues
5 Chapter 5: LINQ Queries & DataTable Operations
5.1 LINQ Essentials for Collections & Filtering 5.2 Advanced DataTable Querying with LINQ 5.3 In-Memory DataTable Transformations & Column Operations
6 Chapter 6: Regex, DateTime, JSON & Invoke Activities
6.1 Regular Expressions & Text Parsing for Automation 6.2 DateTime Formatting, Timezone Conversions & TimeSpan Calculations 6.3 JSON Parsing, JSONPath & Serialization with Newtonsoft.Json 6.4 Invoke Method & Invoke Code Activities 6.5 Data Referencing in Invokes: DataTable, List & Dictionary Arguments
7 Chapter 7: Modern UI Automation & Unified Targeting
7.1 Modern Design Experience & The Unified Target Concept 7.2 Anchors, Relative Elements & UI Automation Activities 7.3 Dynamic Selectors, Variables & Wildcards in Selectors
8 Chapter 8: Object Repository, Computer Vision & Remote Runtime
8.1 Object Repository & UI Descriptor Libraries 8.2 AI Computer Vision for Unattended & Remote Interfaces 8.3 Automation in Virtual Environments & UiPath Remote Runtime
9 Chapter 9: Advanced UI Automation: Browser Modes, Agentic UI & macOS
9.1 Browser Automation with the WebDriver Protocol 9.2 Agentic UI Automation: ScreenPlay, Semantic Activities & Healing Agent 9.3 macOS Automation: Native Apps, Office Apps & AppleScript
10 Chapter 10: Advanced Control Flow & Exception Architecture
10.1 Flowcharts, Sequences & Parallel Control Flow Patterns 10.2 Global Exception Handler Architecture & ErrorAction Directives 10.3 TryCatch, Retry Scope & Custom Exception Architectures
11 Chapter 11: Orchestrator Queues & Transaction Management
11.1 Queue Architecture, SpecificContent & Transaction Lifecycles 11.2 Queue Items SLA, Postpone, Deadlines & Priority Scheduling 11.3 Bulk Operations, Transaction Status Updates & Queue Triggers
12 Chapter 12: Orchestrator Tenant & Folder Entities
12.1 Asset Types, Per-Robot Assets & External Credential Stores 12.2 Modern Folder Hierarchy, User/Robot Assignment & Permissions 12.3 Storage Buckets, Webhooks & Environment Promotion 12.4 Orchestrator Tags: Labels, Properties & Governance
13 Chapter 13: Unattended Execution, API Triggers & Cloud Robots
13.1 Unattended Job Execution: Folders, Priorities, Background vs. Foreground & Runtimes 13.2 API Triggers: Starting Jobs from External Systems over HTTP 13.3 Serverless and Cloud VM Robots: Cloud-Hosted Execution Options
14 Chapter 14: Monitoring, Recording & Solutions Management
14.1 Orchestrator Monitoring, Trigger Alerts & Job Health 14.2 Job and Transaction Recording: Troubleshooting Faulted Unattended Jobs 14.3 Solutions Management: Packaging and Deploying Automations with Their Resources
15 Chapter 15: Debugging, Remote Debugging & Profiling
15.1 Studio Debugging Tools: Breakpoints, Panels & Execution Control 15.2 Remote Debugging: Remote Machine and Unattended Robot Connections 15.3 Profile Execution: Finding Performance Bottlenecks in Studio
16 Chapter 16: RPA Testing & Test Suite
16.1 UiPath Test Suite Overview, Test Cases & Given-When-Then Structure 16.2 Data-Driven Testing, Test Verification Activities & Mock Activities 16.3 CI/CD Pipelines with uipcli & Test Manager Traceability
17 Chapter 17: Long-Running Workflows, Action Center & Apps
17.1 Long-Running Workflows: Persistence, Suspend and Resume 17.2 Action Center & Human-in-the-Loop Orchestration 17.3 UiPath Apps: Action Apps, Automations & Integration Service
18 Chapter 18: Trigger-Based Attended Automation & Callouts
18.1 Trigger-Based Attended Automation: Forms, Triggers & Global Variables 18.2 Running Local Triggers & the Event Inspection Tool 18.3 Callouts & Forms for Attended Guidance
19 Chapter 19: UiPath Assistant & Robot Sessions
19.1 UiPath Assistant: Automations, Reminders, Widgets & Configuration 19.2 Robot Session (Picture in Picture): Child Session vs. Virtual Desktop
20 Chapter 20: Autopilot for Developers & Autopilot for Everyone
20.1 Autopilot for Developers: AI Assistance in Studio and Studio Web 20.2 Autopilot for Everyone: Chat, Automations & Clipboard AI
21 Chapter 21: API Automation & Integration Service
21.1 Integration Service: Connectors, Connections & Connector Activities 21.2 API Workflows in Studio Web 21.3 HTTP Requests: Web APIs, the Orchestrator API & Connector Requests 21.4 Connector Builder: Custom Integration Service Connectors 21.5 Integration Service Event Triggers: Connected and Disconnected 21.6 GenAI Activities: Generative AI Inside Workflows
22 Chapter 22: Data Service, Context Grounding & Coded Workflows
22.1 Data Fabric (Data Service) Entities: Modeling Business Data 22.2 Data Fabric Activities and the Platform Connector 22.3 Context Grounding: Retrieval-Augmented Generation with Company Data 22.4 Coded Automations: Structure, Arguments & Invoking Workflows 22.5 Coded Automation Services: Orchestrator, UI Automation, Microsoft 365 & Custom Services
23 Chapter 23: Integrated Scenario Practice
23.1 Integrated Scenario Practice: Designing an End-to-End Solution
9.3 macOS Automation: Native Apps, Office Apps & AppleScript
Key Takeaways Explain This Topic AI
macOS runs only cross-platform automations, built in Studio Web or as cross-platform projects in Studio Desktop; local feeds are not supported, so packages come from Orchestrator.
UiPath Assistant for Mac supports macOS 10.15 and newer, and web automations need the UiPath extension for Chrome or for Safari.
Native macOS UI automation was a Java-app preview in 2024.10 and became generally available for any Mac desktop app in the 2025.10 (June 2025) release.
The Apple Scripting package provides Invoke Apple Script and Invoke Apple Shortcut, which run only on macOS.
Debug from Studio Web with Debug on Local Machine (Assistant for Mac required) or from Studio Desktop with Remote Debugging.
Last updated: September 2026
9.3 macOS Automation: Native Apps, Office Apps & AppleScript
Core Concept: UiPath automations can run on Apple computers through UiPath Assistant for Mac and the macOS Robot. The exam description lists three macOS skills: UI automation for native macOS apps , Office desktop automation , and scripting , such as AppleScript. Everything starts with the rule that macOS runs only cross-platform projects.
The Platform Pieces
Piece What to know
Project type Build cross-platform projects in Studio Desktop, or build in Studio Web , whose automations are cross-platform. Windows or Windows-Legacy projects do not run on a Mac.
UiPath Assistant for Mac Runs cross-platform automations and connects the robot to Orchestrator; compatible with macOS 10.15 (Catalina) and newer, with downloads for Intel and Apple Silicon.
Package feeds Local feeds are not supported on macOS; automations come from Orchestrator.
Browser extensions Web automations need the UiPath extension for Chrome or the UiPath extension for Safari on the Mac.
Browser Automation on macOS
Browser automation is supported in Chrome and Safari . You design the automation in Studio Web, using either browser, and start it from the macOS Assistant. A local macOS Robot, installed in advance and connected to Orchestrator, carries out the run.
Native macOS App Automation
UiPath's history here is a common exam trap:
2024.10 LTS (preview). Native UI automation on macOS arrived in preview for Java desktop applications in attended scenarios. You built in Studio Desktop on Windows with a cross-platform project, turned on Enable Java automation (preview) in the project's UI Automation settings, ran on the Mac robot through Assistant, and debugged from Studio Web or with Remote Debugging.
2025.10 release (general availability, June 2025). UI-based desktop automation on macOS became generally available. You can design automations for Mac desktop apps directly on macOS in Studio Web, in Safari or Chrome, and any macOS desktop application is supported. UiPath's examples are Keynote, Numbers, Mail, the Microsoft Office apps, and Java apps such as SAP GUI. The same release added a cross-platform Selection Helper and the Advanced Selector Editor for indicating targets from Studio Web.
For Java apps, the UiPath extension for Java loads into Java AWT/Swing interfaces. It works automatically for Java 8. For Java 9 or newer, the application's runtime must include the jdk.attach module, or the extension is loaded from a custom folder.
Office Desktop Apps on a Mac
Microsoft Word, Excel, and PowerPoint for Mac are native macOS applications. With desktop UI automation generally available, you automate them like any other Mac app: use Application/Browser scopes, indicated targets, and selectors built in Studio Web. Keep two points in mind:
Many Windows Office activities rely on the Windows desktop application and are not part of a cross-platform project. Check each activity's project compatibility before designing for a Mac.
For Apple's own productivity apps, UiPath publishes dedicated activity packages, such as Apple Numbers (Get Sheets, Read Cell, Read Range, Write Cell, Write Range) and Apple Mail (For Each Email, List Accounts, Send Mail). They run only on a Mac with the respective app installed.
Scripting with AppleScript and Shortcuts
The Apple Scripting activities package runs macOS-native automation from a workflow:
- Activity Purpose
- Invoke Apple Script Runs an AppleScript file or inline script content and returns its output to the workflow
- Invoke Apple Shortcut Runs a shortcut from Apple's Shortcuts app
Scripts are useful for tasks the UI does not expose well: telling an application to open a document, reading system settings, or controlling apps that publish an AppleScript dictionary. The packages run only on macOS machines that have the target programs installed.
Building, Running, and Debugging
- Step Studio Web Studio Desktop (cross-platform project)
- Design In Chrome or Safari on the Mac On Windows
Debug on the Mac Debug on Local Machine button, which needs UiPath Assistant for Mac installed Remote Debugging to the Mac robot
- Run in production Publish to Orchestrator, then start from Assistant or run as a job Same
- Worked Example: A Mac-Based Expense Filing Automation
A finance team works on MacBooks and wants an attended automation that files receipts:
Design a cross-platform project in Studio Web, using Chrome on the Mac.
Read the receipt list from a Numbers spreadsheet with the Apple Numbers Read Range activity.
Enter each receipt in the expense web portal with Modern UI activities inside Use Application/Browser; the Chrome extension for Mac must be installed.
Tell Finder to move processed PDFs into an Archive folder with Invoke Apple Script , and read the script's output to confirm the move.
Debug with Debug on Local Machine , which requires Assistant for Mac, then publish to Orchestrator.
Run from UiPath Assistant on each finance user's Mac.
If a colleague later asks to run the same automation on a Windows laptop, it can, because it is cross-platform. The Apple-specific activities, however, work only where macOS and those apps exist, so wrap them in a check or keep them in a Mac-only workflow.
Tip
Autopilot for Everyone can use an automation on macOS only if it was built with cross-platform compatibility. That is one more reason to design Mac-bound automations as cross-platform from the start.