- Getting started
- UiPath Agents in Studio Web
- UiPath Agents in Agent Builder
- UiPath Coded agents
Agents user guide
Once you have tested, evaluated, and refined your agent, it's time to publish it. This step is necessary for the agent to be available in the Run Job activity.
- Select Publish to publish the
agent to Orchestrator as a process. Select where to publish:
- Orchestrator Personal Workspace Feed - The process is published to your personal workspace and is only be available to you. This is the default selection.
- Orchestrator Tenant Processes Feed - The process is published to the global tenant feed and is available to all users in eligible folders.
- Select a version. A version is generated automatically starting with 1.0.0 when you first publish, and then incremented automatically every time you republish.
- Optionally, you can select Submit as a template to make the agent available as a template in your organization, or Share, to share it with users in your organization.
Using agents as activities means you can incorporate them into workflows to handle parts of larger deterministic processes, have multiple agents act in series, and start agent execution based on triggers.
To incorporate your agent into a workflow, follow these steps:
- Publish your agent to Orchestrator.
- In Studio, use the Run Job activity to integrate your agent into a workflow.
-
Whenever you make changes to your agent, republish the updated agent to Orchestrator and upgrade the corresponding process in Orchestrator.
The Run Job activity always executes the version of the agent currently configured in Orchestrator. This ensures that your workflow consistently uses the most up-to-date version of your agent.
Refer to the System activities guide to learn how to configure and use the Run Job activity in your Studio workflows.
You can start your agentic journey with a set of agent templates, available in the Agents page in Automation CloudTM and in UiPath® Marketplace.
An agent template comes preconfigured for specific tasks. It requires a minimum configuration to be executable in Studio, and you can modify it and tailor it to your specific needs. An agent template has:
- Predefined components – System prompts, activity tools with descriptions, starter evaluation sets.
- Components are generic, not company or organization-specific.
- Components are readily available in the agent definition. Some components (such as activities as tools) may need additional configuration, like creating the necessary connections in Integration Service.
- Components that require additional configuration – Context Grounding indexes, automations and processes as tools, custom escalations, and all affiliated descriptions (instructions
for the agent).
- These components are organization and tenant-specific.
To start using agent templates from the UiPath Marketplace, take the following steps:
- From the Agents page in Automation Cloud, go the Templates tab and select any template.
You are redirected to the template from Marketplace.
- Select Download.
- In the Downloading an agent template window, select Download Solution.
A
.uisfile containing the agent definition is downloaded to your machine. - Agent templates also include Extras, a separate package containing assets for your agent (automations, custom escalations). Select Download Extras.
A
.zipfile is downloaded to your machine. - In Studio Web, import the Agent definition
.uisfile as described in Importing a project downloaded from Studio Web. - Next, go to Solutions. For details, refer to Accessing the Solutions UI.
- Upload the
.zipfile, as explained in Transporting a solution package, then deploy the solution. For details, refer to Deploying the solution. - You can now access your agent template from Studio Web and add any tools deployed to your tenant.
