388ede1f-ab3e-4a07-bc09-cbdc2c920517.jpg

RPA Solution Architect

FAQ1 - How to install and use this connector?

Documentation Link does not work...shows link has expired.

HiPDF download throwing an error.

Great tool. However, I see this is customized to work with the cloud platform. How can this be altered to work with OnPremise Orchestrators? The endpoints is normally not the same and does for instance not use Tenant and Service in the URL etc.

How to handle authentication? I created the custom connector in Flow and tried authenticating UiPath with basic and API authentication methods. Running a test with GetReleases ends up with error message: "You are not authenticated!"Not sure what to try next, any help is appreciated!

Can you please explain this in your json file as it is related your name 

check line 11-14 in your json swagger file.

/Dinesh/Dineshshbe52082/odata/Machines: {}

  /{{tenant}}/{{service}}/odata/Machines: {}

  /{AccountLogicalName}/{ServiceInstanceLogicalName}/odata/Machines: {}

  /{AccountLogicalName}/{ServiceInstanceLogicalName}/odata/Jobs/UiPath.Server.Configuration.OData.StartJobs: {}

As I followed your steps I get the following erros in PA:

Errors

Semantic error at paths./{{tenant}}/{{service}}/odata/Machines
Declared path parameter "{tenant" needs to be defined as a path parameter at either the path or operation level
Jump to line 11

Semantic error at paths./{{tenant}}/{{service}}/odata/Machines
Declared path parameter "{service" needs to be defined as a path parameter at either the path or operation level
Jump to line 11

Semantic error at paths./{AccountLogicalName}/{ServiceInstanceLogicalName}/odata/Machines
Declared path parameter "AccountLogicalName" needs to be defined as a path parameter at either the path or operation level
Jump to line 13

Semantic error at paths./{AccountLogicalName}/{ServiceInstanceLogicalName}/odata/Machines
Declared path parameter "ServiceInstanceLogicalName" needs to be defined as a path parameter at either the path or operation level
Jump to line 13

Semantic error at paths./{AccountLogicalName}/{ServiceInstanceLogicalName}/odata/Jobs/UiPath.Server.Configuration.OData.StartJobs
Declared path parameter "AccountLogicalName" needs to be defined as a path parameter at either the path or operation level
Jump to line 14

Semantic error at paths./{AccountLogicalName}/{ServiceInstanceLogicalName}/odata/Jobs/UiPath.Server.Configuration.OData.StartJobs
Declared path parameter "ServiceInstanceLogicalName" needs to be defined as a path parameter at either the path or operation level
Jump to line 14

Semantic error at paths./{AccountLogicalName}/{ServiceInstanceLogicalName}/odata/Queues/UiPathODataSvc.AddQueueItem
Declared path parameter "AccountLogicalName" needs to be defined as a path parameter at either the path or operation level
Jump to line 97

Semantic error at paths./{AccountLogicalName}/{ServiceInstanceLogicalName}/odata/Queues/UiPathODataSvc.AddQueueItem
Declared path parameter "ServiceInstanceLogicalName" needs to be defined as a path parameter at either the path or operation level
Jump to line 97

Semantic error at paths./{AccountLogicalName}/{ServiceInstanceLogicalName}/odata/Assets
Declared path parameter "AccountLogicalName" needs to be defined as a path parameter at either the path or operation level
Jump to line 98

Semantic error at paths./{AccountLogicalName}/{ServiceInstanceLogicalName}/odata/Assets
Declared path parameter "ServiceInstanceLogicalName" needs to be defined as a path parameter at either the path or operation level
Jump to line 98

Semantic error at paths./{AccountLogicalName}/{ServiceInstanceLogicalName}/odata/Processes
Declared path parameter "AccountLogicalName" needs to be defined as a path parameter at either the path or operation level
Jump to line 99

Semantic error at paths./{AccountLogicalName}/{ServiceInstanceLogicalName}/odata/Processes
Declared path parameter "ServiceInstanceLogicalName" needs to be defined as a path parameter at either the path or operation level
Jump to line 99

Structural error at paths./{tenant}/{service}/odata/Webhooks.post.responses
should define at least one response
Jump to line 169

Semantic error at paths./{tenant}/{service}/odata/Jobs/UiPath.Server.Configuration.OData.StartJobs
Equivalent paths are not allowed.
Jump to line 339

Semantic error at paths./{tenant}/{service}/odata/Queues/UiPathODataSvc.AddQueueItem
Equivalent paths are not allowed.
Jump to line 409

Semantic error at paths./{tenant}/{service}/odata/Processes
Equivalent paths are not allowed.
Jump to line 608


I downloaded the json file and try to make a connector but keep getting an error? I fully have the guide to the end. Is there anyone who can help?

Den angivne swagger har følgende fejl: 'Definitionen er ikke gyldig. Fejl: 'Critical : paths/~1{tenant}~1{service}~1odata~1Webhooks/x-ms-notification-content/schema/properties/Type/x-ms-visibility : The type of the property is incorrect. Expected type 'String', but value is of type 'Null'.'

I am getting this error when trying to add it to Flow. 

Specified swagger has the following errors: 'Definition is not valid. Error: 'Critical : paths/~1{tenant}~1{service}~1odata~1Webhooks/x-ms-notification-content/schema/properties/Type/x-ms-visibility : The type of the property is incorrect. Expected type 'String', but value is of type 'Null'.'

Do you have an estimate when the on-premise version of this will be available? Also, it seems that you aren't replying to many posters with questions.  Are you answering them privately or not all?  It would be helpful to provide answers to questions so that others may benefit otherwise why post anything at all?

Nice tool but not working with on prem orchestrator. Befor 3 months you wrote:

"With the current version, on premise orchestrator is not supported. However the new  with the on premise orchestrator will be released soon" ...

Same issues than OP. Is there any update to this connector ?

When is the on premise version coming out?

I don't see this available in MS Flow anymore..is it decommissioned?

Is the new version available to work with On-Premise Orchestrator

f91a55a8-a2cb-427b-83f6-185a645d3ecc.zip

UiPath is the most popular RPA software in the market. MS Flow is the most popular cloud-based automation tool with tight integration with the Office applications and more than 250 external connectors like LUIS, Azure, Salesforce, Computer vision, ServiceNow, Bitbucket, JIRA, etc.The integration between these two platforms will open up numerous opportunities to automate processes and eliminate some of the existing limitations. Both are widely used in enterprises to achieve automation goals. This integration will ensure a proper connection to bridge the gaps, push the limits and improve automation.Orchestrator API and Webhooks are combined with the MS Flow custom connector creation to define and develop triggers and actions for the Custom Connector framework. The New Uipath cloud and API authentication mechanism are used to build the connector.Triggers added to MS Flow:<ul><li>A job completes successfully;</li><li>A job fails;</li><li>A new item added to a queue.</li></ul>Actions added to MS Flow:<ul><li>Start a job;</li><li>Add a queue item;</li><li>Get all releases;</li><li>Get all processes;</li><li>Get the job status.</li></ul>Technical possibilities:<ul><li>Execute UiPath robots based on various triggers available with MS Flow (inbuilt, custom and third party).</li><li>Examples: Triggers from SharePoint, Outlook, Facebook, Twitter, GitHub, JIRA, Salesforce, Workday, MS Kaizala, Azure, Slack.</li><li>Execute workflows on MS Flow platform with triggers from UiPath.</li><li>Example: Run a skype flow to notify the stakeholders on successful UiPath job completion. Orchestrator webhooks are configured in MS Flow to build a custom connector for UiPath</li><li>Train the models built-in with AI builder and use the processed data in UiPath jobs.</li><li>Connect AI services like LUIS, Face API, computer vision with the UiPath workflows through MS Flow.</li><li>Build PowerApps for Mobile and web to provide an easy user interface to the users to run/monitor the automation.</li><li>Build Microservices combining MS Flow with UiPath using HTTP request feature of MS Flow</li></ul>Use Cases<ul><li>Run UiPath job on a file added or modified to SharePoint, Google Drive, OneDrive.</li><li>Run UiPath job when particular emails are received (e.g. invoices, reports)</li><li>Process invoices/receipt thru trained models in AI builder and execute UiPath jobs with the extracted data.</li><li>Execute other onboarding processes when a new employee is added to the workday.</li><li>Get notified through Skype, MS teams, Slack, SMS, mobile push notifications about UiPath events (job completion, failure, etc.).</li><li>Create and process surveys.</li><li>Setup approval flows.</li></ul>

f7a93f79-82df-463f-83c4-56e9e28a58f0.PNG

a01a6ec8-8d80-4cab-96c7-df664b207258.PNG

483144d4-1f06-4031-8da2-d903e544377a.jpg

3794445e-91a1-4d52-8385-eb02ff9d1323.png

MIT License Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Microsoft Flow Connector

Microsoft Flow Connector