# Running unattended bots via UiPath Cloud Orchestrator

**Cloud vs. On-Premise:** These instructions are for the UiPath Cloud Orchestrator. For On-Premise Orchestrator support, contact <sales@pixiebrix.com>

### Configuring the UiPath Cloud Orchestrator Service

{% hint style="info" %}
**Private vs. Shared Credentials:** Currently, the UiPath Cloud Orchestrator Service can only be configured as a Private Service in the Browser Extension. Configuring UiPath as a Shared Service is coming soon
{% endhint %}

#### Locating Your UiPath API Credentials

The UiPath documentation has detailed instructions for [Viewing API Access Information](https://docs.uipath.com/automation-cloud/docs/about-api-access). As an administrator, open the Admin tab in UiPath Automation Cloud:

<figure><img src="/files/CczkpxN346ysqRKRQw5x" alt=""><figcaption></figcaption></figure>

Click the Cloud Icon ☁️ in the Orchestrator row to view the API Information

#### Configuring the Service Credentials

1. Open the PixieBrix Extension (visit [app.pixiebrix.com](https://app.pixiebrix.com/) and click "Open Browser Extension")
2. Open the Configure Services page from the Sidebar
3. From the "Configure a new service dropdown", select UIPath Cloud Orchestrator<br>

   <figure><img src="/files/iEeVVvTWyyHhYx5Ccyr3" alt=""><figcaption></figcaption></figure>
4. Enter your UiPath Cloud Orchestrator API information

* accountName: the "Account Logical Name" field the API Information dialog. You can also locate the account name in the URL you use to access Cloud Orchestrator

  ```yaml
  <https://cloud.uipath.com/**>[Account Name]**/[Tenant Logical Name]/orchestrator_/
  ```
* tenantName: the "Tenant Name" field in the API Information dialog. You can also locate the tenant name in the URL you use to access Cloud Orchestrator. The default UiPath tenant name is `DefaultTenant`

  ```yaml
  <https://cloud.uipath.com/>[Account Name]/**[Tenant Logical Name]**/orchestrator_/
  ```
* clientId: The "Client Id" field in the API Information dialog
* userKey: The "User Key" field in the API Information dialog
* folderId: the folder id **number** (not name), that can be found as the `fid=` URL parameter when you select the folder in UiPath Cloud Orchestrator

<figure><img src="/files/5wcXowB9sPmmy62nHCEu" alt=""><figcaption></figcaption></figure>

### Running the Process

Go to the Page Editor's and add the "Run a UiPath process" brick to your mod.<br>

<figure><img src="/files/nqbdyjqo3YB7KiP1wEDk" alt=""><figcaption></figcaption></figure>

Select the Process Release from the "release" dropdown. You should see all of the Release that are in the folder you configured above

<figure><img src="/files/u0240qeQuaUTuDHrSJ3I" alt=""><figcaption></figcaption></figure>

Select a Strategy for running the Process:

* JobsCount (default): run the process *X* times across when the bots become available
* All: run the process on all unattended bots
* Specific: run the process on one or more bots that you select

Finally, configure the Input Arguments for your Process. PixieBrix automatically displays which Input Arguments are available. For example, the following screenshot shows configuring a "Crunchbase.Lookup" process that one argument, "OrganizationSlug":

<figure><img src="/files/tOF1IsqX0keHpZ7OI8wq" alt=""><figcaption></figcaption></figure>

#### Creating and Managing Process Arguments

You can learn how to create/manage input arguments for process in the UiPath documentation: [Managing Arguments](https://docs.uipath.com/studio/docs/managing-arguments)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.pixiebrix.com/integrations/uipath/running-unattended-bots-via-uipath-cloud-orchestrator.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.