- Getting started
- Capabilities
- Operate
- Troubleshoot
- Data privacy and governance
- Product availability
- Earlier Autopilot capability sets
- User scenarios
- Prompting guide
- Example prompts
- Best practices and limitations
- Supported models and limits
- Quality-check requirements
- Generate tests for requirement
- Import manual test cases
- Find obsolete tests
- Generate tests for SAP transactions
- Generate synthetic test data
- Generate test reports
- Generate coded test cases
- Search Test Manager project
- Troubleshooting
- Autopilot for Everyone
- About Autopilot for Everyone
- Licensing
- User types
- Data sources
- Toolset automations
- Localization
- Prerequisites
- Autopilot widget
- The Autopilot for Everyone tenant card
- Prerequisites for installation
- Enabling Anthropic models
- Installing Autopilot for Everyone
- Updating Autopilot for Everyone
- Uninstalling Autopilot for Everyone
- Configuring Autopilot for Everyone
- Disabling the Autopilot welcome screen in Assistant
- Configuring an LLM for Autopilot for Everyone
- Deploying toolset automations
- Prompt-to-response flow
- Launching Autopilot for Everyone
- Autopilot settings for business users
- Using a specialized Autopilot
- Using a starting prompt
- Uploading and analyzing files
- Running automations
- Interacting with Autopilot answers
- Using suggested prompts
- Starting a new chat
- Chat history
- Providing general feedback
- Clipboard AI Enterprise version
- Designing relevant automations for Autopilot for Everyone
- Troubleshooting
UiPath operational tasks Autopilot runs through natural-language asks, from folders and jobs to queues, assets, connections, and audit logs.
Autopilot can drive most operational tasks across UiPath — folders, jobs, queues, assets, audit logs, connections, and more — through natural-language asks. It runs against your logged-in session, scoped by the context you give it. This page covers what to ask for, what to expect, and where the boundaries are.
Most Operate capabilities are generally available. Managing solutions, users/roles/permissions, Integration Service connections, and audit logs are in public preview — capabilities and commands may change before general availability.
Prerequisites
- A logged-in session with access to Automation Cloud or Automation Suite.
- Folder access for whichever Operate scope you want to act on — Autopilot inherits your permissions.
What Autopilot can do
Each row groups one operational domain. You state the outcome, not the command — Autopilot picks the right approach.
| Area | What Autopilot can do | Example ask |
|---|---|---|
| Folders & access | List, create, nest, move, delete folders; assign users and roles | "Add alice@x.com to Finance as Automation User" |
| Users, roles, permissions | Inspect role grants, create/edit/delete roles, list permissions, see who has access to what | "Which folders does bob@x.com have access to, and with what roles?" |
| Licenses | Inspect allocations across users and robots | "Add 2 more Unattended runtime licenses to prod-worker-01" |
| Machines & runtimes | List machines, inspect runtimes available in a folder | "What runtimes are currently available in Production?" |
| Sessions | List active robot sessions, see which machine each is on, disconnect stuck sessions | "Show all running unattended sessions in Production and how long they've been active" |
| Processes & packages | Upload packages, list versions, create or update process releases; manage package feeds | "Publish version 2.3.0 of InvoiceBot to Finance" |
| Solutions | Publish, upload, deploy, activate; list deployed versions across tenants and folders | "Deploy v1.4 of the invoice processing solution to Accounting in the staging tenant" |
| Jobs | Start, stop, monitor, fetch execution logs and attachments, group by state | "List every faulted job from yesterday in Production and show their error messages" |
| Assets | List, get, create, update, delete assets across folders | "Copy all assets from folder A to folder B" |
| Credential stores | List, create, update, delete vault integrations; rotate referenced credentials | "Which assets in Production still reference the old CyberArk store?" |
| Queues & queue items | Inspect queue depth, push items, bulk-update statuses | "Which queues have more than 100 NewItems right now?" |
| Storage buckets & files | Create buckets, upload, download, list, delete files | "Download every file from bucket reports/ modified in the last 7 days" |
| Libraries | Publish, list versions, manage releases | "Show all versions of the Email.Utilities library in the tenant feed" |
| Triggers | Create time, queue, and event triggers; manage calendars; list runs; inspect history | "Show me the last 10 runs of triggers for the HR onboarding solution" |
| Webhooks | Create, list, test | "List all active webhooks and the events they listen to" |
| Integration Service connections | List, test, refresh, troubleshoot OAuth tokens; check connection health | "Test every Salesforce connection in Production and report which ones are failing" |
| Audit logs | Filter by user, component, action, date range | "Who deleted the Finance folder last month?" |
| Action Center tasks | List, inspect, reassign, and complete human-in-the-loop tasks | "Show all pending tasks assigned to me in the Finance folder" |
| Feedback | Submit bug reports and product suggestions directly from the chat | "Submit a bug report for the selector healing issue I just hit" |
Read vs. write
Autopilot treats Operate actions in two tiers:
- Read operations —
list,get,logs,audit-logsand similar. Autopilot runs these on its own judgement. - Write operations — anything that creates, updates, or deletes. Autopilot confirms with you before running.
State your expectation up front when an ask is complex. For instance: "Clean up unused process packages, but show me the list first."
Authorization and scope
Autopilot acts as the logged-in session — it inherits your permissions exactly. If you can do something in the UiPath UI with your account, Autopilot can do it; if you cannot, neither can Autopilot.
Autopilot also honors folder context. Operations scope to a specific folder unless you say "across all folders" or similar. If you change folders mid-conversation, restate the scope.
Common multi-step patterns
These are the patterns where Autopilot saves the most time — multi-step asks that would otherwise mean chaining several operations by hand.
Triage faulted jobs
"Triage every faulted job in Production from the last 24 hours. Group by error message and show the top 5 root causes."
Autopilot lists jobs filtered by state and time, fetches logs for each, groups by error signature, and presents a ranked summary. You then decide which to retry.
Promote between tenants
"Promote the invoice processing solution from the dev tenant to the staging tenant. Deploy it under the Accounting folder."
Autopilot pulls the solution from the dev tenant, switches session to the staging tenant, and deploys it into the Accounting folder. It confirms each tenant switch before acting.
Assign a user to folder
"Assign charlie@x.com as Automation User to the Accounting folder, and also assign the VM Machine."
Autopilot assigns the user to the folder with the Automation User role, then assigns the VM Machine to the same folder so the user can run unattended jobs against it.
Audit role grants
"Audit all roles assigned to external users (anyone with an @ outside our domain) and report which folders they can edit."
Autopilot lists users, filters by domain, expands each user's role grants per folder, and surfaces a structured report.