Skip to content

Latest commit

 

History

History
 
 

python

README.md

page_type description products languages extensions urlFragment
sample
This sample app demonstrates use of different bot conversation events available in bot framework v4 for personal and teams scope.
office-teams
office
office-365
python
contentType createdDate
samples
12-12-2019 13:38:25
officedev-microsoft-teams-samples-bot-conversation-python

Teams Conversation Bot

Bot Framework v4 Conversation Bot sample for Teams (Messages in bot conversations).

This bot has been created using Bot Framework. This sample shows how to incorporate basic conversational flow into a Teams application. It also illustrates a few of the Teams specific calls you can make from your bot.

Included Features

  • Bots
  • Adaptive Cards
  • Teams Conversation Events
  • Immersive Reading Support for Cards

Interaction with bot

BotConversation

Try it yourself - experience the App in your Microsoft Teams client

Please find below demo manifest which is deployed on Microsoft Azure and you can try it yourself by uploading the app package (.zip file link below) to your teams and/or as a personal app. (Sideloading must be enabled for your tenant, see steps here).

Teams Conversation Bot: Manifest

Prerequisites

  • Microsoft Teams is installed and you have an account
  • Python SDK min version 3.6
  • ngrok or equivalent tunnelling solution

To try this sample

Note these instructions are for running the sample on your local machine, the tunnelling solution is required because the Teams service needs to call into the bot.

  1. Clone the repository

    git clone https://github.com/OfficeDev/Microsoft-Teams-Samples.git

  2. Run ngrok - point to port 3978

    ngrok http 3978 --host-header="localhost:3978"

  3. Create Bot Framework registration resource in Azure

  4. In a terminal, go to samples\bot-conversation

  5. Activate your desired virtual environment

  6. Install dependencies by running pip install -r requirements.txt in the project folder.

  7. Update the config.py configuration for the bot to use the Microsoft App Id and App Password from the Bot Framework registration. (Note the App Password is referred to as the "client secret" in the azure portal and you can always create a new client secret anytime.)

  8. This step is specific to Teams.

    • Edit the manifest.json contained in the teamsAppManifest folder to replace your Microsoft App Id (that was created when you registered your bot earlier) everywhere you see the place holder string <<YOUR-MICROSOFT-APP-ID>> (depending on the scenario the Microsoft App Id may occur multiple times in the manifest.json)
    • Zip up the contents of the teamsAppManifest folder to create a manifest.zip
    • Upload the manifest.zip to Teams (in the Apps view click "Upload a custom app")

  9. Run your bot with python app.py

Interacting with the bot

You can interact with this bot by sending it a message, or selecting a command from the command list. The bot will respond to the following strings.

  1. Show Welcome
  • Result: The bot will send the welcome card for you to interact with
  • Valid Scopes: personal, group chat, team chat
  1. MentionMe
  • Result: The bot will respond to the message and mention the user
  • Valid Scopes: personal, group chat, team chat
  1. MessageAllMembers
  • Result: The bot will send a 1-on-1 message to each member in the current conversation (aka on the conversation's roster).
  • Valid Scopes: personal, group chat, team chat

You can select an option from the command list by typing @TeamsConversationBot into the compose message area and What can I do? text above the compose area.

Running the sample

The bot initialization message Message

The bot will send the welcome card for you to interact with WelcomeCard

The bot will respond to the message and mention the user MentionMe

The bot initialization message MessageAllMembers

Deploy the bot to Azure

To learn more about deploying a bot to Azure, see Deploy your bot to Azure for a complete list of deployment instructions.

Further reading