Skip to main content

How to publish your bot on Microsoft Teams

Blip Help
  • Updated
Before including the advanced settings, publish the bot!

Index:

  1. Integration, configuration and construction of the bot in MS Teams
  2. Using the Developer Portal

 

Bot integration, configuration and construction in MS Teams:

1- Run MS Teams on your work area or through the web app (https://teams.microsoft.com);

mceclip27.png

 

2- Run the App Studio application in the left bar. 

mceclip28.png

 

mceclip29.png

 

3- Click on "Create new app"

mceclip30.png

 

4- Fill in the fields below with the bot information:

mceclip31.png

Important note: In the Identification field, you must click the "Generate" button to generate a random App ID. This App ID is extremely important for the configuration of our bots and it will be generated in a completely random way.

Below are the required fields and the used values:

Package name: com.microsoft.teams.app

Version: 1.0.1 (it must be filled in in this format with 3 digits accompanied by periods. Example: 0.0.1 . If the bot undergoes any changes, it is important to update this version number. It is up to the creator which numbers to use)

Note: Fill in the fields according to your business information.

 

 

 

 

5- Then, on the left side menu, select the Bots option and click Set up.

Note: Do not check "My bot is a one-way notification only bot".

mceclip32.png

  • Fill in the required fields and save the generated password, it will be necessary for integration with Blip.
  • Homologation: the bot endpoint must be https://hmg-abs.gw.msging.net/   [ACCOUNT EXTERNAL ID]
  • Production: the bot endpoint must be https://abs.gw.msging.net/ [ACCOUNT EXTERNAL ID]
  • Set up the scope as needed. Checking all options will turn the bot into a human contact in teams.

    Connect the bot that was created in Microsoft Teams with Blip.

  • It is necessary to add some parameters in the Blip advanced configuration:

💡 The domain must be postmaster@abs.gw.msging.net

  • AccountExternalId: external bot identifier. Find it in the application details menu.mceclip33.png
  • ApplicationId: bot communication id. Find it in the Bots menu.mceclip34.png
  •  
  • ApplicationPassword: password generated when creating the bot.
  • AudioSentence:it is the sentence that will appear when a user receives an audio sent by Blip.
  • DocumentSentence: is the sentence that will appear when a user receives a document sent by Blip.
  • GifSentence: I is the sentence that will appear when a user receives a gif sent by Blip.
  • VideoSentence: it is the sentence that will appear when a user receives a video sent to him/her by Blip.
  • WeblinkSentence: it is the sentence that will appear when a user receives a link sent to him/her by Blip.
  • TextButton:it is the sentence that will appear on the button when a user receives any media sent to him/her by Blip.

mceclip35.png

  1. Download the created bot in the menu: Finish> Test and distribute.
    mceclip36.png
  2. Import the downloaded file. The image below shows where the option is.
    mceclip37.png

Using the Developer Portal

 

Access the link https://dev.teams.microsoft.com/home. 

 

1 - Create an App

mceclip38.png

2- Include basic information.

 

 

 

The App ID that appears in the print must be considered as AccountExternalId.

mceclip39.png

 

3- When selecting App features, create a bot for the application.

mceclip40.png

4- After choosing a name, put the endpoint:

 

https://abs.gw.msging.net/ADDHERE  AccountExternalId

 

5- Click on Client Secrets. When generating the secret, save it and consider it as the ApplicationPassword.

mceclip41.png

 

6- After creation, copy the generated number and consider it as ApplicationId.

mceclip42.png

7- After these steps, go back to the Applications selection, select your App and return to the App Features menu. Click Bot again and select the application you just created.

 

 Select the Upload and download files option.

mceclip43.png

8- After saving, continue in App features and add the Group and channel app.

The URL must be the same as the one entered in step 4.

mceclip45.png

9- After saving, continue in App features and add Message and Extension.

Select the same bot that was created and save.

mceclip46.png

10 - Demonstrative photo after the steps taken.

mceclip47.png

11- Click on Publish to Store. Make sure everything is OK and Download your package.

mceclip48.png

12 - Import the downloaded file. The image below shows where the option is.

mceclip49.png

Note: Remember that the AccountExternalId (Step 2), ApplicationId (Step 6) and ApplicationPassword (Step 5) are the ones described above.

  • Connect the bot that was created in Microsoft Teams with Blip.
  • It is necessary to add some parameters in the advanced configuration in Blip:

 

💡 The domain must be postmaster@abs.gw.msging.net

 

AccountExternalId: Bot's external identifier. (step 2)

mceclip50.png

ApplicationId: Bot communication ID. (step 6)

mceclip51.png

ApplicationPassword: password generated when creating the bot. (step 5)

AudioSentence: is the sentence that will appear when the user receives an audio sent by Blip.

DocumentSentence: is the sentence that will appear when the user receives a document sent by Blip.

GifSentence: is the sentence that will appear when the user receives a gif sent by Blip.

VideoSentence: is the sentence that will appear when the user receives a video sent by Blip.

WeblinkSentence: is the sentence that will appear when the user receives a link sent by Blip.

TextButton: is the phrase that will appear on the button when the user receives some media sent by Blip.

mceclip52.png

Supported Elements

 

The elements below behave the same in Blip:

 

  • Text;
  • Emotion;
  • Image;
  • Composition;
  • Carousel.
  • If you want to use payload, only application/json is accepted.
  • If you don't want to use payload, choose web link or text title only.
  • The carousel supports 10 cards per message.
  • Menu.
  • The menu does not position its buttons vertically. Microsoft Teams fills all the horizontal space to break the line.
  • If you want to use payload, only application/json is accepted.
  • If you don't want to use payload, choose web link or text title only.

 

Unsupported elements

 

The elements below are not supported:

 

  • Location

 

Adapted Elements

 

The elements below are not natively supported. An adaptation was necessary for a better user experience:

 

  • Video;
  • Audio;
  • Document;
  • Quick answer;
  • Web link.

 

These elements will be shipped in the same template below:

 

  • 1st Obs.: the button opens the sent media content.
  • 2nd Obs.: The phrase that will be displayed will be the same configured in the Blip.

mceclip53.png

The quick response behaves the same as the menu, where the options are not hidden after the user chooses them.

mceclip54.png

For more information, visit the discussion on the subject in our community or the videos on our channel. 😃

Related articles