UiPath Chatbot Connector - Preview

The UiPath Chatbot Connector Guide

The User Interface


The Chatbot Connector Preview is deprecated effective July 1st ‘21

The service is deprecated and will be unavailable after October 2021. Learn more

All Connections

After successfully accessing the UiPath Chatbot console, the All Connections page is displayed.

This is the main page displaying all the chatbots previously configured, the Dialogflow agent, Orchestrator service, and the channels each chatbot is connected to along with the status of their connections to Dialogflow and Orchestrator.

The following actions are available:

  • Create a new connection: simply click the Create new + button and give your connection a suitable name.
  • Rename or Delete a connection: click the three-dotted icon '...' displayed next to its tile and select the needed action.

Connection Page

For each Connection the below modules are displayed:


The Build page allows you to configure/edit the connection to an NLP agent in Google Dialogflow and an Orchestrator service.

Click the Connect/Edit button corresponding to the Dialogflow agent and/or Orchestrator service to launch the corresponding configuration wizard.



The Map page allows you to configure the intents to process. This page displays the list containing all intents from the connected Dialogflow agent, the processes mapped to each of them along with the option to map/unmap any of them.



The Launch page allows you to configure the option for the targeted audience to send messages to your chatbot. The following options are available:

  • Configure an integration with a Slack bot and make your chatbot available in Slack.
  • Connect your chatbot to the UiPath provided web widget, test it with RPA fulfillment before making it available to your target audience, and use the embed code to add it to your internal and external web pages.

Updated about a year ago

The User Interface

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.