Assuming you have your connection, the first thing to do is to configure what we call “Connection Rules”. These are per-channel rules, and each tells which projects, pipelines, operators and integrations your Bot connection will have access to when the users in that channel ask data questions to the bot (which, lets clarify, will need to be in that channel as well in most chat providers).

So, you go to that section:

And click “Add Rule”. Then you’ll see the dialog and then you must properly fill it. For example, if your chat is named “general” (#general in some chat services), you’ll use that name. Also, you’ll choose whether you’ll link integrations to this rule, or projects / pipelines / operators (in this case, you may choose any project you want to add, any pipeline or any operator, and all the related tables will be considered):

There’s something you have to understand here:

Example for a rule which matches entire projects, pipelines, or specific operators.

There’s something you have to understand here:


• If you choose to list integrations, only integrations will be added.


• If you choose to list projects, pipelines and/or operators, only those will be added.


  • To add a project (which implies: adding all the tables associated to it, being them from linked integrations or contained pipelines and their operators) just choose a project, and leave the Pipeline and Operator selectors in “Select” (i.e. empty).


  • To add a pipeline (which implies: adding all the tables associated to it and their operators) choose a project and a pipeline, leaving the Operator selector in “Select” (i.e. empty).


  • To add an operator (which implies: adding all the tables associated to it) choose a project, pipeline, and operator.


  • You’ll quickly get that, for each row you add here, the more you specify means the more restrictive is your allowance in that entry.


  • You can add many entries (in my example, I added 3: One for all the tables in the “Intermedia” project, one for all the tables in the “Sample Pipeline” pipeline in the “Sample Luis’ Project” project, and one for all the tables in the “TRAIN” operator in the “Classification …” pipeline which in turn is contained in the “Diego’s project …” project.


If you don’t define a rule for a channel, the bot will complain when a user tries to interact with him in that channel. One of these rules is always needed for a channel. Due to security reasons, we don’t allow creating a rule granting access to all the projects and integrations implicitly: the rule must always be explicit, following the stated rules earlier.

Extra (Training) Files

You can add up to 19 files to a channel’s connection rule for your workspace. These files serve for the bot to have more available knowledge than the one that can be obtained from the tables you allow it to have by defining integrations, projects, pipelines or operators. The allowed extensions for those files are:The next step is to install the application:

You can add those files in the “training” section: