page_type | description | products | languages | extensions | urlFragment | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
sample |
This sample app illustrates how to utilize action previews in Teams Messaging Extensions, allowing users to create cards from input in a Task Module. It showcases bot interactions that enhance user engagement by attributing messages to users. |
|
|
|
officedev-microsoft-teams-samples-bot-msgext-action-preview-python |
Experience a hands-on demo of a Microsoft Teams bot utilizing Action-Based Messaging Extensions. This sample showcases the integration of card creation through user inputs in a Task Module, featuring interactive messaging, command execution, and full support for bot interactions.
Messaging Extensions are a special kind of Microsoft Teams application that is support by the Bot Framework v4.
There are two basic types of Messaging Extension in Teams: Search-based and Action-based. This sample illustrates how to build an Action Based Messaging Extension and demonstrates creating a simple card based on parameters entered by the user from a Task Module.
- Bots
- Message Extensions
- Action Commands
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 Messaging Extensions Action Preview: Manifest
- Microsoft Teams is installed and you have an account
- Python SDK version 3.7
- dev tunnel or ngrok latest version or equivalent tunnelling solution
The simplest way to run this sample in Teams is to use Teams Toolkit for Visual Studio Code.
- Ensure you have downloaded and installed Visual Studio Code
- Install the Teams Toolkit extension and Python Extension
- Select File > Open Folder in VS Code and choose this samples directory from the repo
- Press CTRL+Shift+P to open the command box and enter Python: Create Environment to create and activate your desired virtual environment. Remember to select
requirements.txt
as dependencies to install when creating the virtual environment. - Using the extension, sign in with your Microsoft 365 account where you have permissions to upload custom apps
- Select Debug > Start Debugging or F5 to run the app in a Teams web client.
- In the browser that launches, select the Add button to install the app to Teams.
If you do not have permission to upload custom apps (sideloading), Teams Toolkit will recommend creating and using a Microsoft 365 Developer Program account - a free program to get your own dev environment sandbox that includes Teams.
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.
-
Clone the repository
git clone https://github.com/OfficeDev/Microsoft-Teams-Samples.git
-
Run ngrok - point to port 3978
ngrok http 3978 --host-header="localhost:3978"
Alternatively, you can also use the
dev tunnels
. Please follow Create and host a dev tunnel and host the tunnel with anonymous user access command as shown below:devtunnel host -p 3978 --allow-anonymous
-
Create Bot Framework registration resource in Azure
- Use the current
https
URL you were given by running the tunnelling application. Append with the path/api/messages
used by this sample - Ensure that you've enabled the Teams Channel
- If you don't have an Azure account you can use this Bot Framework registration
- Use the current
-
Bring up a terminal, navigate to
Microsoft-Teams-Samples\samples\msgext-action-preview\python
folder -
Activate your desired virtual environment
-
Install dependencies by running
pip install -r requirements.txt
in the project folder. -
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.) -
This step is specific to Teams.
- Edit the
manifest.json
contained in theappManifest
folder to replace your Microsoft App Id (that was created when you registered your bot earlier) everywhere you see the place holder string${{AAD_APP_CLIENT_ID}}
(depending on the scenario the Microsoft App Id may occur multiple times in themanifest.json
) - Zip up the contents of the
appManifest
folder to create amanifest.zip
- Upload the
manifest.zip
to Teams (in the Apps view click "Upload a custom app")
- Edit the
-
Run your bot with
python app.py
Note the
manifest.json
specifies that this bot will be available in theteam
scope and the command will be available in thecompose
,commandBox
andmessage
contexts.
Click the Messaging Extension icon in the Compose Box's Messaging Extension menu.
To learn more about deploying a bot to Azure, see Deploy your bot to Azure for a complete list of deployment instructions.