page_type | description | products | languages | extensions | urlFragment | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
sample |
This is an sample application which showcases how to invoke Dialogs (referred as task modules in TeamsJS v1.x) from adaptive and hero cards. |
|
|
|
officedev-microsoft-teams-samples-bot-task-module-nodejs |
Bot Framework Teams Dialog (referred as task modules in TeamsJS v1.x) sample.
This bot has been created using Bot Framework. It shows how to fetch a Dialog (referred as task modules in TeamsJS v1.x) from a Hero Card button and receive input from an Adaptive Card in the Dialog (referred as task modules in TeamsJS v1.x).
- Bots
- Tabs
- Dialogs (referred as task modules in TeamsJS v1.x)
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 Dialog (referred as task modules in TeamsJS v1.x): Manifest
- Microsoft Teams is installed and you have an account
- NodeJS
- dev tunnel or ngrok latest version or equivalent tunnelling solution
- Teams Toolkit for VS Code or TeamsFx CLI
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
- Select File > Open Folder in VS Code and choose this samples directory from the repo
- 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.
-
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
In Azure portal, create a Azure Bot resource. - For bot handle, make up a name. - Select "Use existing app registration" (Create the app registration in Microsoft Entra ID beforehand.) - If you don't have an Azure account create an Azure free account here
In the new Azure Bot resource in the Portal,
- Ensure that you've enabled the Teams Channel
- In Settings/Configuration/Messaging endpoint, enter the current https
URL you were given by running the tunneling application. Append with the path /api/messages
-
Clone the repository
git clone https://github.com/OfficeDev/Microsoft-Teams-Samples.git
-
In a terminal, navigate to
samples/bot-task-module/nodejs
-
Install modules
npm install
-
Update the
.env
configuration for the bot to use the<<MicrosoftAppId>>
,<<MicrosoftAppPassword>>
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.)<<MicrosoftAppTenantId>>
will be the id for the tenant where application is registered.
-
Set "MicrosoftAppType" in the
.env
. (Allowed values are: MultiTenant(default), SingleTenant, UserAssignedMSI) -
Replace
<<BaseUrl>>
in the.env
as per your application like the ngrok forwarding url (iehttps://xxxx.ngrok-free.app
) after starting ngrok and if you are using dev tunnels, your URL will be like: https://12345.devtunnels.ms. -
Replace
<<MicrosoftAppId>>
and <> with your MicrosoftAppId and BaseUrl in the.TaskModuleTab.js
file.
-
Run your bot at the command line:
npm start
-
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<<YOUR-MICROSOFT-APP-ID>>
(depending on the scenario the Microsoft App Id may occur multiple times in themanifest.json
) - Edit the
manifest.json
for<<Valid-Domain>>
with base Url domain. E.g. if you are using ngrok it would behttps://1234.ngrok-free.app
then your domain-name will be1234.ngrok-free.app
and if you are using dev tunnels then your domain will be like:12345.devtunnels.ms
. - Zip up the contents of the
appManifest
folder to create amanifest.zip
(Make sure that zip file does not contains any subfolder otherwise you will get error while uploading your .zip package) - Upload the
manifest.zip
to Teams (In Teams Apps/Manage your apps click "Upload an app". Browse to and Open the .zip file. At the next dialog, click the Add button.) - Add the app in personal/groupchat/team scope (supported scopes)
- Edit the
Note: If you are facing any issue in your app, please uncomment this line and put your debugger for local debug.
Note this
manifest.json
specified that the bot will be installed in "personal", "team" and "groupchat" scope which is why you immediately entered a one on one chat conversation with the bot. You can at mention the bot in a group chat or in a Channel in the Team you installed it in. Please refer to Teams documentation for more details.
You can interact with this bot by sending it a message. The bot will respond with a Hero Card and Adaptive Card with buttons which will display a Dialog (referred as task modules in TeamsJS v1.x) when clicked. The Dialogs (referred as task modules in TeamsJS v1.x) demonstrate retrieving input from a user, or displaying custom web page content.
- Personal Scope Interactions:
- Dialog (referred as task modules in TeamsJS v1.x) Tab:
- Group Chat Scope Interactions:
To learn more about deploying a bot to Azure, see Deploy your bot to Azure for a complete list of deployment instructions.