UiPath Process Mining

The UiPath Process Mining Guide

Setting up Actionable Insights



If you have set up Actionable Insights in earlier versions of UiPath Process Mining you must update the folder name in the installation from actioncenter to orchestrator. You must also make sure to update all the files from the Basic Connector relating to Actionable insights, including the python scripts.


UiPath Action Center is the central portal to track and monitor complex business processes, tasks, people, and robots. You can connect UiPath Process Mining to your UiPath Orchestrator to trigger people or robots based on Process Mining insights. You can use the triggers to add queue transactions for robots, or alert people with actions in UiPath Action Center. This guide describes how to connect with UiPath Orchestrator to enable Actionable Insights.


It is assumed that you have:

  • installed (as an administrator) Python and the following Python packages on the UiPath Process Mining Server:
    • requests,
    • json,
    • python-dotenv.
  • access to a UiPath Cloud Orchestrator cloud or on-prem Orchestrator;
  • access to the UiPath Process Mining installation folder on the server;
  • downloaded the latest version of the UiPath Process Mining Basic Connector.
  • knowledge of UiPath Orchestrator and UiPath Action Center.



If you are using an UiPath Orchestrator on premise, it is recommended to install UiPath Process Mining on a different server.

Step 1: Connect UiPath Orchestrator

The Actionable insights folder in UiPath Process Mining Basic Connector installation package contains the files that you need to connect with your UiPath Orchestrator.
Follow these steps to connect your UiPath Orchestrator.




Unzip the Actionable insights folder in UiPath Process Mining Basic Connector installation package and deploy it in the root folder of your UiPath Process Mining installation . Make sure the folder is setup with a subfolder orchestrator that contains the .env file and the FormTemplate.json file. See illustration below.


Rename the .env file to the name of the tenant for which the connection is set up.
For example, if the tenant is Default, theUiPath Orchestrator config file must be renamed to Default.env. See illustration below.


Make sure that the settings are set and/or added in the <tenant>.env config file as described below.

Settings for using UiPath Orchestrator in the cloud

Set the following settings if your UiPath Orchestrator is in the cloud.

  • ORCH_URL = [url] (see 1 in the illustration below)
  • ORCH_CLIENT_ID = [*Client ID*] (see 2 in the illustration below)
  • ORCH_USER_KEY =[*USer Key*] (see 3 in the illustration below)

Settings for using UiPath Orchestrator on-premise

Set the following settings if your UiPath Orchestrator is in on-premise.

  • ORCH_URL = [url] (see 1 in the illustration below)
  • ORCH_USERNAME: [Your username]
  • ORCH_PASSWORD: [Your password]



Refer to Getting the API Access Information from the Cloud Platform's UI in the UiPath Orchestrator Guide for more information on how to display the API Access panel.

Step 2: Setting up your Workspace

Follow these steps to set up your Workspace for Actionable Insights.




Go to the Superadmin Workspaces tab and create a new folder Actionable insights.


Upload the following files to the Actionable insights folder:

See illustration below.

Updated 11 months ago

Setting up Actionable Insights

Suggested Edits are limited on API Reference Pages

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