UiPath

Audience: Low-code Engineers

Skill Prerequisites: Actions, Tokens, Connectors, UiPath account

The UiPath add-on hands work off to a UiPath robotic process automation (RPA) robot. Its main action starts a UiPath process on one or more robots from a form, workflow or scheduled job, and saves UiPath's response in a token. Two more actions create and change the UiPath connectors it signs in with.

note

This add-on is the DnnSharp.UiPath package. It's installed separately and needs the UIPATH feature package in your license. If it isn't licensed, the actions fail with a not-licensed error. If you don't see the UiPath actions, the add-on isn't installed.

Choosing an action

Action	What it does	Use it to
Run Robot	Starts a UiPath process release on the robots you list, passing input arguments, and saves UiPath's response as JSON.	Enter submitted form data into a legacy desktop application, or run a nightly RPA process from a scheduled job.
Add UiPath Connector	Creates a UiPath connector with a tenant, username and password, and saves its ID in a token. It doesn't check the login.	Let each customer or department save its own UiPath account from a form.
Update UiPath Connector	Replaces the title and login details of an existing connector. Empty values clear the saved ones.	Save a new password after it changes in UiPath.

Setting up the connector

Run Robot signs in with a UiPath connector that holds the tenant name, username and password. Create it in the Connectors area or with Add UiPath Connector, change it with Update UiPath Connector, and check it with Test Connector. Neither action contacts UiPath, so a wrong password is saved without an error. When you update a connector, pass the tenant and username again, and use ****** to keep the saved password.

The action signs in with UiPath's older username and password authentication. UiPath has since moved Automation Cloud to OAuth-based external applications, so the sign-in may not work with current tenants. Test it with your UiPath account before relying on it.

What Run Robot doesn't do

• It doesn't wait for the robot. The action only starts the job and returns as soon as UiPath has the request. It doesn't get the robot's results.
• It doesn't check UiPath's answer. An error from UiPath, such as an unknown release key, is saved in the output token like a normal response, and the next actions still run. Read the response with Parse JSON Into Tokens and check it with a condition.
• It doesn't call other UiPath APIs. Use Server Request for those.

For the other connector actions, see the Connectors actions.

Revised 10/02/2026