- Getting started
- Capabilities
- 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
- Product availability
- Prompting guide
- Example prompts
- 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
Guide to writing effective queries for Autopilot search, the one-shot retrieval capability.
Autopilot search is a one-shot retrieval capability: you ask a question, and Autopilot looks it up using its connected sources. There is no multi-step conversation or iterative refinement.
For general prompting tips, refer to Writing effective prompts.
Writing effective queries
Because search returns a single answer, put your full question in one prompt:
- Be specific — include the exact name of the resource, process, or concept you are looking for. For example, "What triggers are configured for the InvoiceProcessing process?" is better than "Show me triggers."
- Add context — mention the folder, tenant, or project scope when applicable. For example, "List all assets in the Finance folder."
- Ask one question at a time — search handles a single query per interaction. If you need multiple answers, submit separate queries.
In Orchestrator
Autopilot search in Orchestrator uses connected retrieval sources (Web Search, Web Reader, UiPath Documentation Search) to answer questions about your environment, documentation, or general UiPath platform topics.
In Test Manager
In Test Manager, Autopilot search lets you search across test objects using natural language — for example, "Find test cases related to invoice validation."