Study guide
20.2 Autopilot for Everyone: Chat, Automations & Clipboard AI
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
20.2 Autopilot for Everyone: Chat, Automations & Clipboard AI
Key Takeaways Explain This Topic AI
Autopilot for Everyone lets business users chat, analyze files, use grounded company knowledge, and run automations; Clipboard AI helps paste into forms.
Build automations for it as cross-platform projects focused on a single task.
Use String, Int32, Double, Boolean, and DateTime inputs, marking required ones, and outputs ResultMessage or output_html.
Throw business rule exceptions with clear messages instead of exposing stack traces.
Autopilot recommends automations from their descriptions and infers arguments using argument prompt descriptions, so make both distinct and clear.
Last updated: September 2026
20.2 Autopilot for Everyone: Chat, Automations & Clipboard AI
Core Concept: Autopilot for Everyone is a chat assistant for business users. It answers questions, works with uploaded files and company knowledge, and can recommend and run automations that developers built for it. The exam tests how developers design automations so that Autopilot can find, configure, and run them well.
What Users Can Do
Chat with a generative AI assistant, starting with their own prompt, a starting prompt, or suggested prompts .
Upload and analyze files , and use company knowledge made available through context grounding .
Run automations: Autopilot recommends a matching automation, infers argument values from the conversation, asks for missing ones, and runs it.
Use specialized Autopilots configured by administrators for specific teams or tasks.
Paste with Clipboard AI , which maps copied content to the fields of a target form or application.
Users reach Autopilot for Everyone, for example, in the Autopilot tab of UiPath Assistant, which is shown when Autopilot for Everyone is installed in the tenant.
Designing Automations for Autopilot for Everyone
UiPath's best practices for developers:
Project
Build the project cross-platform so Autopilot can use the automation on macOS too.
Focus each automation on a single task , for example one to five activities in one sequence.
Input arguments
Use descriptive names, for example in CamelCase, and mark mandatory arguments as required .
Use only these types, which Autopilot renders as controls:
- Type Rendered as
- String Free text field
- Int32 Whole number picker
- Double Whole or decimal number picker
- Boolean True/False dropdown
- DateTime Date-time picker
- Output arguments
Use only:
ResultMessage : a string shown back to the user, or a string serialization of JSON or a DataTable. Autopilot understands JSON arrays of single-level objects and flat DataTables.
output_html : an HTML string that Autopilot renders in an iFrame. The automation must not be configured as a pre-response automation.
Exceptions
Use business rule exceptions with custom messages for known errors, so the full stack trace is not sent to the chat.
Automation Properties
Autopilot for Everyone recommends automations solely from their descriptions . Give each automation a distinct description so recommendations do not overlap. Additional properties, configured in the Admin App, describe:
- what the automation does,
- how its card appears in the chat,
how to infer each argument, through an argument prompt description for the AI (for example, "The priority of the email. Choices include low, high. If not provided, default is low.") and a description to user shown on the card,
how it should run, and what context it needs.
Returning Data Wisely
Chat sessions have a limited capacity for information. For retrieval automations, return only the relevant data , for example the five most recent orders with three fields each, not the whole order table.
Worked Example: "Where Is My Order?"
A customer service team wants to ask Autopilot about order status.
The developer builds a cross-platform automation GetOrderStatus with a required String input OrderNumber .
It calls the order system through an Integration Service connector and returns ResultMessage as a short JSON array: order number, status, and expected delivery date.
If the order does not exist, it throws a BusinessRuleException with the message "Order not found. Check the number and try again."
The description reads: "Looks up the status and expected delivery date of one customer order by order number."
A user types "What's the status of order 55120?" Autopilot recommends the automation, fills OrderNumber with 55120 from the message, runs it, and shows the result.
Checklist Before Publishing an Automation for Autopilot
The project is cross-platform and does one task.
Every input is String, Int32, Double, Boolean, or DateTime, with required ones marked.
Outputs are ResultMessage or output_html only, and the data returned is short.
Known errors throw business rule exceptions with messages a business user understands.
The description says what the automation does, for which object, and what the user must provide, without overlapping other automations.
Each argument has an argument prompt description that tells the AI how to infer it, including defaults and allowed values.
The automation was tested by typing realistic requests into the chat, including requests that are missing information, to see whether Autopilot asks for the missing values.
Key Terms
Pre-response automation: an automation configured to run before Autopilot responds; such an automation cannot use output_html .
Specialized Autopilot: a configured variant for a team or task, with its own instructions and resources.
Automation card: the chat card that shows the automation, its arguments, and a run button.
Common Traps
Using argument types Autopilot does not render, such as DataTable inputs.
Vague or duplicated descriptions, which lead Autopilot to pick the wrong automation.
Returning huge outputs that exceed the chat's capacity.
Letting system exceptions surface; use business rule exceptions with clear messages.