Autopilot should be able to understand and resolve UiPath platform resources that the current user is authorized to access.
From a developer’s perspective, the experience should be simple: when building a workflow, the developer should be able to refer to a resource by its friendly name or business purpose, and Autopilot should identify the correct platform resource and configure the workflow accordingly.
For example:
“Use the invoice extraction model I created in my Document Understanding project.”
If the developer created the model or has permission to use it, Autopilot should be able to discover the relevant project and model, resolve the required internal identifier, and select the most appropriate supported integration method—whether that is a native activity, connector operation, or API call.
Document Understanding is one example. In this case, an extraction request may require an extractor ID. The developer had access to the DU project and had created the extraction model, but Autopilot could not retrieve the extractor ID automatically. The developer therefore had to call the extractor metadata API manually, inspect the response, and copy the GUID into the workflow.
There may be a better native or platform-supported way to invoke DU extractors than using the REST API. The request is not intended to prescribe that implementation. The broader requirement is that Autopilot should understand the platform resources available to the current user and resolve the correct resource automatically.
Technically, Autopilot should have a permission-aware resource context that can:
- Discover resources visible to the current user.
- Resolve friendly names to internal resource identifiers.
- Understand relationships between projects and their resources.
- Identify the appropriate activity, connector, or API operation.
- Populate required IDs and dependent parameters automatically.
- Respect tenant, folder, project, and resource-level RBAC permissions.
- Distinguish between permissions to view, use, edit, and administer a resource.
- Ask the user to choose when multiple resources match.
- Explain clearly when a resource cannot be used because of permissions or configuration.
- Revalidate resource access when the workflow is executed.
This capability should apply beyond Document Understanding, including:
- Models and extractors
- Integration Service connections
- Orchestrator processes
- Queues and assets
- Storage buckets
- Data Fabric entities
- Apps and automations
- Agent tools
- Published workflows
- Other platform resources
A developer should not need to open Swagger, call a metadata endpoint, inspect JSON, and manually copy GUIDs when the resource is already accessible within UiPath Cloud.
The expected outcome is that Autopilot becomes context-aware of the UiPath platform and can safely use the resources available to the current user, while remaining fully governed by RBAC and platform security controls.
CC: @diana.gray @Vibhor.Shrivastava @zell12 @Akhil_Padgilwar_qbotica