- Getting started
- Capabilities
- Data privacy and governance
- Product availability
- Earlier Autopilot capability sets
- User scenarios
- Prompting guide
- Example prompts
- Autopilot usage pool for testing
- 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
Autopilot as a coding agent for API workflow projects in Studio Web: what you can do and the tools it uses.
Autopilot in Studio Web builds and edits API workflows using natural language — the same coding agent that ships with Studio Desktop, adapted to the API workflow project type.
Use Autopilot to:
- Build an API workflow from a plain-language description — Sequence, Assign, JavaScript, If, ForEach, DoWhile, TryCatch, Wait, and Response activities, including nested control flow.
- Look up and wire HTTP requests or Integration Service connector activities, such as Gmail, Outlook, GitHub, or Slack, using a pinged connection.
- Handle files as attachments — convert a file to base64 for an API call, or a base64 payload back into a file.
- Validate the workflow before you run it.
- Run it locally and test it against an eval set, looping until every case passes.
- Package and publish the workflow to Orchestrator.
- Operate a published workflow — invoke it, manage its Integration Service connections, and check job logs.
Tools
Before making changes, Autopilot reads the API workflow skill for the open project. It scaffolds, validates, packages, and publishes projects through the api-workflow and solution UiPath CLI (uip) command groups. It discovers and wires connector activities through the workflow's own registry lookup.
It also uses the platform skill for connections, assets, queues, and jobs on a published workflow. Running the workflow with authentication, or publishing it, can send real requests or ship to your tenant, so Autopilot asks for your confirmation first. It can also read, edit, and search project files, and create new API workflow projects at the solution level.
Known limitations
Support for API workflows in Studio Web is experimental: review generated workflows before you run or publish them. You can switch back to the classic Autopilot agent experience for API workflows from the chat title bar at any time.