Chatbot with Dialog flow

Dialogflow has evolved a lot since this component was created.
Authentication is no longer handled by dialogflow itself, but instead managed via the Google Cloud Console: you need to create a service account with the “Dialogflow API Client” role
Unfortunately, this also means you need to upgrade to the latest node module “@google-cloud/dialogflow” which uses a different API and requires a bit of JS rewrite.

Hi, great suggestion.

You would not be able to directly plug Orchestrator and Dialogflow as Webhooks are not enough to implement the necessary logic on their own, but leveraging Webhooks to forward the result of the Robot work back to the end user would be a lot more efficient than the current polling implementation (which is based only on what was available back in 18.2...)

Hello Mr. Bond, happy to hear the MI6 is looking into this component.

For on-prem Orchestrator, you can simply use the username/password/tenant info to authenticate.

For Cloud Orchestrator, you need to use the API access as documented here:

https://docs.uipath.com/orchestrator/v0/reference/consuming-cloud-api

How these tokens map to the configuration is documented here:

https://docs.uipath.com/orchestrator/v0/reference/consuming-cloud-api

Please note that the dependency in package.json may be a bit old, please double check if you should update to something more recent (latest version on npm is 1.1.3)

If you still face issues, please reach out on the Marketplace category of the forum:

https://forum.uipath.com/c/build/marketplace/81

Good catch!

Some old components were hosted on an outdated account, and stopped showuing apparently.

Please wait a bit, our ops team will get this fixed soon.

This component "Chatbot with Dialogflow" is a basic (and aging) sample demonstrating how to bridge Orchestrator to Dialogflow for chatbot-enabled RPA scenarios.

Rich responses are beyond the scope.

If you are interested in chatbots, please have a look at the dedicated section on our website:

https://www.uipath.com/product/chatbots-automation

The chatbot code of this connector would need to run in your own private environment (inaccessible to UiPath.)

If configured as documented to send data to Orchestrator, your data will only reach a UiPath hosted environment if you rely on UiPath Automation Cloud (on-prem UiPath has no access in the first place.)

Security for our cloud offering is well documented: https://www.uipath.com/legal/trust-and-security

This component is aging though, and targeting a technical audience. I would suggest you to also take a look at our official chatbot page: https://www.uipath.com/product/chatbots-automation

I do not believe this is just about the transition from v1 to v2, but Google actually changes the authentication mechanism.

According to their doc you should be able to Set up authentication with a service account

This also means the version of dialogflow referenced in package.json need to change from "apiai" to "@google-cloud/dialogflow"... This component  really needs a refresh.

Hello,

For Cloud/Community Orchestrator, you need to rely on Cloud authentication:

https://docs.uipath.com/orchestrator/v2019/reference/consuming-cloud-api

As documented in the uipath-orchestrator module's README (see below) the configuration will have to be a bit different:

https://github.com/UiPath/orchestrator-nodejs

"orchestrator": {

    "refreshToken": "qwertyuiopasdfghjkllzxcvbnmQWERTYUIOPASDFGHJK",

    "serviceInstanceLogicalName": "NADefault",

    "path": "naycblzht/NADefault",

"clientId": "qwertyuiopasdfghjkllzxcvbnm"

}

Where "refreshToken" is the "User Key" from the Cloud credentials.

A lot of users also happen to have more than 1 folder, which requires to configure the Orchestrator client further:

1. Find the FolderID that you are using from this URL:

https://cloud.uipath.com/naycblzht/NADefault/odata/Folders

2. add in "orchestrator.js", inside the "setup" function a call to

orchestrator.switchOrganizationUnitId(12345);

Where 12345 is your FolderID

A lot has happened for Orchestrator since 18.1 which was the base for developing this component.

I really need to update the instructions to make it more relevant for today's product.

I am not familiar with RASA myself, but assuming the HTTP API exposes roughly similar functionality, I guess you could reuse the architecture of this component.

That being said, UiPath has evolved quite a lot since the development of this component, and were I to work on it today, I would most likely use webhooks somewhere.

Sorry, but I have no out-of-the-box solution dedicated to RASA in particular.

Well, this isn't much to do with Chatbot or Dialogflow, but OK I'll bite...

"Integrating Python in UiPath" could happen in 2 directions.

UiPath -> Python: you could directly invoke the python via command line, or use the dedicated Python activity package documented here: https://docs.uipath.com/activities/docs/invoking-a-python-script

Python -> UiPath: in that case we are most likely in the unattended use case, meaning you want your python script to hit the Orchestrator API, either starting a job or creating a queue item. You can find the Orchestrator API reference here: https://docs.uipath.com/orchestrator/reference/api-references

There are certainly parts worth recycling, like the code that interfaces with Orchestrator.

That being said, the current implementation assumes no component like python scripts being part of the setup, so you will need to adapt the code to your own use case.

Hello,

Please double check that you went through each step in the README.pdf under Resources (especially importing the intents in Dialogflow and configuring the Dialogflow token)

Beyond this becomes troubleshooting and I am afraid the "Questions" functionality of Connect is not suited for that.

If you still face difficulties, I would suggest you open a forum thread in https://forum.uipath.com/ (where my handle is qbrandon)