- Getting started
- UiPath Agents in Studio Web
- UiPath Coded agents
Agents user guide
Limitations and FAQ
We are actively working on adding new capabilities. Please be aware of the following current limitations:
| Capability | Description |
|---|---|
| User prompt | User prompts are not required. These agents do not rely on predefined prompts to collect input. Instead, they consume messages in real time and respond accordingly, one turn at a time. |
| Data manager | Data Manager is currently disabled. Since outputs are emitted dynamically by the conversational agent throughout the conversation, there is no need to configure output arguments. The ability to configure inputs, which would be high-level parameters to initialize a conversation, will be available in a future release. |
| File uploads | You must add a file analysis tool such as Analyze Attachment, an IXP tool, or a workflow which can process uploaded files. We recommend only uploading image files (png, jpg, jpeg, tif, tiff) and PDF files smaller than 5MB. |
| Local desktop automation | The agent cannot run automations that interact with the your local desktop (e.g., via Assistant). We are working on this capability in a future release. |
| Personal connections | You cannot run tools using your personal Integration Service connections. Only Shared connections are available. |
| Voice interaction | You can only interact with the agent via text commands. Push-to-talk and two-way voice interaction will be available in preview in a future release. |
| Tool confirmation | The agent does not ask for confirmation before executing a tool. |
FAQ
If your conversational agent fails to start in Instance Management, check the following requirements:
- Make sure you have assign an unattended robot to the solution folder that contains your agent.
- Make sure you are in the correct tenant where your conversational agent solution resides.
Without these resources, the agent won’t initialize or run when triggered from Instance Management.
Why am I getting a connection error when running tools?
The agent needs to have access to the same connections you used at design-time to debug the agent. If your solution uses Integration Service connections, create and manage those connections in a shared Orchestrator folder. Use the shared connections during design time, then publish the solution as a subfolder within the same shared folder. This setup ensures the solution automatically inherits the parent folder’s connections.
How can I enable voice interaction for my conversational agents?
We are still working on enabling push-to-speak and always-on modes for conversational agents, as well as IVR integrations. This will be available in a future release.
How can I embed conversational agents in my application?
You can embed conversational agents using the iFrame approach outlined in this documentation. We are working closely with the UiPath SDK team to enable usage of our APIs with custom front-ends and applications. This will be available in a future release.
