Chatbot with Dialog flow

true

Hello,

Please have a look at the Orchestrator client configuration.

As you can see in the module's README, you can support self-signed certificates by using the "invalidCertificate" option.

Hello, a common issue since 19.10 is that one needs to configure the folder ID where the queue is.

You can login to Orchestrator and access this endpoint "/odata/Folders" to find the numeric ID of the appropriate folder.

Then configure your Orchestrator client instance with the switchOrganizationUnitId method documented here.

Hi Venkata, and thank you for looking into this component.

You are in luck, we just started the public preview of UiPath's chatbot connector service:

https://forum.uipath.com/t/chatbot-connector-now-in-public-preview/210724

It too is based on Dialogflow.

Please have a look, as we have now come a long way since early 2018 (when this component was developed)

Hi,

I am going to go out on a limb here and assume that you mean pushing a message to the user past the timeout to respond to the intent fulfillment.

If that is what this is about, the answer is simple: you cannot push messages to the user through Dialogflow. This is the very reason the chatbot component here is designed with Dialogflow as a service used by the connector, and not standing in between the chat system and the connector.

I know that Dialogflow is already supporting a lot of integrations out of the box (Slack, Skype, Google Assistant to only name a few) but unfortunately, RPA requires more than 6 seconds to be able to do something, so you will need to handle the integration with the chat service yourself to work around this limitation.

Under the "Resources" tab of this component, you can find a Readme.pdf file to provide resources about the configuration process.

The config file's "orchestrator" object is where you would configure your credentials for Orchestrator.

If you use on-premise, follow the instructions here

If you want to use platform.uipath.com, you will need to see the note about the experimental support of cloud authentication (see the mention of refreshToken here)

If you still get stuck, how about starting a forum thread about this and mention me? My handle is qbrandon.

Please have a look at the first question from Davendra Patel:

> Error for "127.0.0.1": Error: Unexpected status code: 400

The answer was as bellow:

> If you are using platform, please see the section about refresh token in the module used to interface with Orchestrator:

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

> The util to get your refresh token can be found here:

> https://github.com/UiPath/orchestrator-nodejs/tree/master/tools/platform

If you are not using platform.uipath.com, but an on-premise Orchestrator instance, and you are facing authentication issue, then it could be something else, but please do have a look at the module above, especially the configuration options.

Well, I have to admit that Amazon may not have been the best choice of sample for datascraping...

I have also noticed the success or failure of scraping may depend on the request itself, so I would suggest trying a variety of input, like book titles, cd titles, movie titles, etc... which may result in different presentation layouts, some working and some not...

If you are using platform, please see the section about refresh token in the module used to interface with Orchestrator:

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

The util to get your refresh token can be found here:

https://github.com/UiPath/orchestrator-nodejs/tree/master/tools/platform

Well, the module itself has been updated, so with a little of DYI, you can get it to run:

1. edit package.json so uipath-orchestrator targets 1.1.0
2. have a look at the following page to know how to get and configure the refresh token

https://www.npmjs.com/package/uipath-orchestrator

I need to update the component, but that will cover more things, at the very least, it needs to use Dialogflow API V2. And that will be a little later (but hopefully before the end of October which is when V1 will be taken down IIRC)

Hello Aju,

Unfortunately, newer platform account rely on OAuth rather than Basic Authentication (username/password)

I need to update the underlying Node.JS Orchestrator module to handle this type of credentials.

For a detailed information about how OAuth token consumption works (if you wish to understand why this project is not ready) you can look at this section of the Orchestrator doc:

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

That being said, Basic Authentication is very much usable on non-cloud Orchestrator instances, so if you have access to any one of these, feel free to give it a try.

Best regards,

Quentin

• Software reqs: UiPath Studio and Node.JS
• In Dialogflow (project/agent needed) import the provided amazon intent and entity
• Create a queue "pendingTasks"
• Publish "persistentRobot" package on Orchestrator, create a process, and manually run the job (this is an always-running robot)
• Extract the "chatbot-bridge", cd into it, and run `npm install` to pull the Node.JS dependencies
• Edit the bridge configuration file "config/default.json" to match your environment:
• server.{host,port} to establish the local HTTP endpoint that will serve the chat WebUI
• orchestrator as the constructor options (see https://github.com/UiPath/orchestrator-nodejs/wiki/Reference)
• dialogflow is the "Client access token" under the general settings of your agent (V1 API)
• log is the configuration passed to log4js (see https://log4js-node.github.io/log4js-node/)
• Run the bridge process `node index.js`

Open http://127.0.0.1:6543 , ask the chatbot to search something for you on Amazon.