UiPath Integrations

The UiPath Integrations Guide

Welcome to the UiPath Integrations guide. You will find comprehensive guides and documentation to help you start working with UiPath Integrations, as well as support if you get stuck.

In order to download the solutions mentioned here please visit the official UiPath Go! Marketplace here.

*Note that only integrations built in-house at UiPath are detailed below. For a complete list of UiPath's technology partners, see here.


Indicate whether a property is an input or output

There are four directions in which a property can point:

  • In: The most common. Used for input arguments.
  • Out: Used for output arguments, the results of an activity.
  • InOut: Rarely used, but can be handy in activities that take in data, modify it, and output it for use in other activities.
  • None: Discrete types like Booleans and Enums do not require a direction. Use None when creating properties of these types.

Argument Restrictions

Note that Out and InOut properties can only accept variables, not literal values, in UiPath Studio. This makes sense since the activity needs something to which the outputted value can be written.

Activity Creator

Generated Code

The Argument direction is seen in the declaration of each property. Notice that FirstNumber and SecondNumber are both InArguments while Sum is an OutArgument.

#region Properties

public InArgument<int> FirstNumber { get; set; }

public InArgument<int> SecondNumber { get; set; }

public OutArgument<int> Sum { get; set; }


Effect in UiPath Studio

Hover over each property in the Properties Pane to see its direction.

Updated 27 days ago


Indicate whether a property is an input or output

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.