SoftTech AI Registry
UiPath · UiPath Agents

Conversational agent tool execution

A UiPath Conversational Agent reasons over the tools configured for it and selects and invokes those tools during its own runtime conversation. UiPath describes tools as the mechanism that connects agent reasoning to real actions. Tool types include Integration Service connector activities, API workflows, RPA automations, other agents, functions, IXP document-processing tools, MCP servers and client-side tools. Distinct from Maestro process orchestration, where a process decides when an agent runs as one step.

Recorded characteristics

Function
UiPath documents tools as "the mechanism that connects agent reasoning to real actions by granting access to business data and executable capabilities." A Conversational Agent is given tools with descriptions and instructions, and during a conversation the agent decides which configured tool to invoke. Documented tool types: Integration Service activities (connector tools making "direct, governed API calls to target business applications"), API workflows, RPA automations, other agents, functions, IXP document-processing tools, MCP servers and client-side tools. Not every tool changes state: tools may retrieve data, compute, or perform actions. UiPath's design guidance names persistent actions: a tool that "creates an event, sends an email, updates a business record, or triggers an automation with external side effects." Since the July 2026 runtime change, when the agent calls multiple tools in parallel the runtime processes them sequentially. Client-side tools use the same tool mechanism: when the agent calls one, "the runtime pauses, delegates the tool call to the client, and resumes once the client returns a result"; the handler runs in the user's browser or host application rather than in UiPath's server runtime. MCP-server tools are recorded here as another tool type available to the agent. Authoring path: Agent Builder or Maestro Flow (Preview); the authoring path is not a separate action capability.
Data access
Tools can access business data through connector activities, API workflows, automations, MCP servers and client-side tools, within the connections and folder resources the deployment grants. Client-side tools can access client-local data and device capabilities unavailable server-side. Specific data scopes depend on the tools configured by the builder.
Actions
Can take actions
External actions
Yes
Human confirmation
Conditional
Permission basis
Mixed
Administrative control
Human confirmation: per-tool "Require confirmation" setting. When enabled, execution pauses before the tool runs and the proposed inputs are shown; the user may approve, modify inputs and approve (tool runs with modified inputs), or reject ("the tool does not run"). UiPath states confirmations are configured per tool and should be enabled for tools that should not run until the user reviews the proposed action; confirmation may be left off for tools allowed to run automatically. Escalations (distinct from tool-call confirmation): powered by Action apps in Action Center, route decisions to a human for validation, approval or manual assistance; the conversation pauses until a human resolves the escalation; an agent can be designed to escalate before a tool runs, but escalation does not mean every action requires approval. Guardrails: deterministic rules that can filter tool inputs/outputs, block execution (recommended for sensitive data in production) or trigger escalation; guardrail evaluation is not itself human confirmation. Identity and connection settings: per-tool Account setting "Inherit parent job identity"; connections "configurable by users" for personal connections (Public Preview); shared connections in the Orchestrator folder; unattended robot account for anonymous channels; Orchestrator folder permissions and host-folder/serverless machine template requirements.
Default state
Conditional
Availability
Action execution requires configuration: creating the conversational agent, adding and describing tools, connections, Orchestrator folder permissions, host-folder/runtime configuration, publishing and deployment, and per-tool identity/connection settings; confirmation is separately configurable. Access to UiPath Agents alone does not make arbitrary tools executable. Deployment channels documented include Instance Management, Assistant (Autopilot for Everyone), Microsoft Teams, Slack, iFrame/Apps embedding, anonymous access and the UiPath TypeScript SDK. Maturity is mixed: Maestro Flow authoring is Preview; personal connections are Public Preview with the full experience only in select deployment channels; agent memory is Preview. No explicit GA statement for the complete Conversational Agents capability is recorded.
Licensing
UiPath documents a hybrid licensing model for chat agent executions; Flex licensing consumes Agent Units, and when monthly limits and top-ups are spent conversational agents continue by drawing on further consumption as described on the licensing page. Entitlements are not inferred beyond the page.
External model or provider
No single model or provider. Customers select from UiPath-supported models (a your-own-model subscription option is Preview; gemini-3.5-flash added August 2026). Integration Service activity tools are not supported when using Gemini models. UiPath documents regional availability with automatic cross-region request routing where a model is unavailable locally. Supported models do not all provide identical tool functionality.
Limitations and uncertainty
Two identity layers: (A) UiPath runtime identity; (B) the credential/connection used against the target application. Since July 2026, signed-in conversational agents run as the UiPath Cloud user's identity; anonymous channels use an unattended robot account. An individual tool runs under the user's identity only when its Account is set to "Inherit parent job identity". Personal connections (Public Preview) let users select their own Integration Service connections; personal connections take precedence, and where none is configured for a connector the agent falls back to the shared connection in the Orchestrator folder; this fallback is documented for connectors only. Unresolved: no explicit GA statement for the complete capability; personal connections are Public Preview and the experience varies by deployment channel (the investigation noted Slack is not supported for some features; not generalised here); not every tool type is documented as inheriting the chat user's identity; external identity for MCP-server tools and client-side tools is not fully established; connector tools are not supported with Gemini models; regional/runtime differences (July 2–16 2026 phased rollout; cross-region routing) may remain relevant; the methodological boundary of "UiPath Agents in Flow" (GA September 15 2026) relative to #126 and Maestro is unresolved. Pre-July 2026 behaviour is historical only.

Evidence