- Getting started
- UiPath Agents in Studio Web
- UiPath Coded agents
Activities
Add Integration Service activities as tools in Agents to make governed API calls directly to target business applications through secure connections.
Agents can use Integration Service activities as tools.
Through secure, governed Integration Service connections and the field configurations described in the following sections, an agent is able to make API calls directly to a target business application.
To use Integration Service activities as agent tools, you must first install connectors and set up connections in Integration Service. For more information, refer to Connectors.
Configuring activities to act as tools
- From the Design tab, under the Tools section, select Add tool.
- In the Toolbox:
- Search for an activity using the search bar, or
- Select Activity and browse by connector. Selecting a connector reveals the list of supported activities.
- Once you add an activity as a tool, you can:
- Edit the tool name and description.
- Select a preexisting Integration Service connection or create a new one.
- Configure the input fields to teach your agent how to use the activity.
Each activity comes with a default description, which you can customize to better guide your agent during runtime. While optional, this step enhances output quality and helps the agent understand how to use the tool for specific use cases.
Defining activity input methods
Agents can automatically infer the information needed to execute an activity successfully, so you typically don't need to define input or output values manually. By default, agents determine the appropriate field values at runtime based on the tool’s description and context.
However, you can override this behavior for any field by selecting a different input method using the context menu. The available input methods are:
- Prompt (default) – The agent infers the field value at runtime using the tool’s description and other relevant information.
- Argument – The field is populated using an agent input argument. You must define the argument beforehand. This option is useful for passing data from a preceding workflow into the agent via the Run Agent activity.
- Static Value – The field is set to a fixed value that remains the same every time the agent runs.
Cascading fields cannot be set to Prompt input method. These are fields where selecting a specific value (for example, an issue type in Jira) changes the structure of the remaining fields in the activity. Because the tool schema cannot dynamically adjust at runtime, agents cannot infer values for such fields. Other fields default to Prompt and can be LLM-inferred at runtime. However, you must ensure the agent has access to the necessary context (for example, via prior tools, prompt wording, or arguments) to infer those values correctly.
Limitations
- Integration Service activity tools are not supported when using Gemini models. When you select a Gemini model, the agent's activity tools are disabled.
- The GenAI web activities (Web Search, Web Reader, and Web Summary) are not available in Automation Suite, so agents cannot use them as tools. For details, refer to GenAI Activities feature availability.