*If you would prefer a private instance of Orchestrator, contact us for a trial license.
There are 3 documents that tell you all you need to know about the Orchestrator API:
The best place to start though is with the Postman collection, which can be used out of the box to make API calls to Orchestrator. It handles all authentication/token refreshing and walks you step-by-step through the most common processes.
Typically, you would be doing the following:
- Grab the Release key of the process you wish to start.
- Grab the ID of the Robot on which to run the process.
- OPTIONAL: Set input data to feed to the robot process by writing it to a Queue or to an Asset.
- Start a job using the Release key and a Robot ID gathered earlier. The Robot will pull an item from the Queue or Asset if indicated.
a. Alternatively, you can directly start a job with input parameters.
Yes, as of 2018.3, jobs accept input arguments of primitive types (integer, string, boolean) and may also output values.
You have three options:
- Set up a webhook that alerts you immediately after a job has finished or queue item has been processed. Here's how you set one up.
- Poll the Orchestrator API at regular intervals to check the status.
- At the end of your workflow, add an HTTP Request activity that calls back to the partner platform with the desired information.
Here are some resources to get started:
Of course! Here are 2 simple workflows:
a. A simple Hello World process that displays a message box with the phrase “Hello Beautiful People”. If you are connected to an Orchestrator with an Asset named greeting, the message box will instead display the value of this Asset. Finally, if you call this process via the API and send an input string named greeting, this value will instead be displayed.
b. Topics covered: Job Inputs/Outputs, Assets, Workflow Variables
a. A process that pulls two addends from the Addends Queue in Orchestrator, opens the Windows calculator app, adds the two numbers, and puts the sum in the output field of the Queue.
b. If there are no transaction items in the Addends Queue, one will be created with 10 & 12 as the two inputs. If the Queue does not exist, it must be manually created within Orchestrator.
Please follow the Getting Started Guidelines on UiPath Go!, which will walk you through:
- Creating an account on Go!
- Becoming a Contributor
- Uploading components