page_type | description | products | languages | extensions | urlFragment | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
sample |
This sample demonstrates use of various meeting events which are available in bot framework v4 |
|
|
|
officedev-microsoft-teams-samples-meetings-events-nodejs |
Using this Node JS sample, a bot can receive real-time meeting events. For reference please check Real-time Teams meeting events
This feature shown in this sample is currently available in public developer preview only.
- Bots
- Adaptive Cards
- RSC Permissions
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).
Realtime meeting events: Manifest
-
Office 365 tenant. You can get a free tenant for development use by signing up for the Office 365 Developer Program.
-
To test locally, NodeJS must be installed on your development machine (version 16.14.2 or higher).
# determine node version node --version
-
dev tunnel or ngrok latest version or Tunnel Relay
If you are using Ngrok to test locally, you'll need Ngrok installed on your development machine. Make sure you've downloaded and installed Ngrok on your local machine. ngrok will tunnel requests from the Internet to your local computer and terminate the SSL connection from Teams.
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: The free ngrok plan will generate a new URL every time you run it, which requires you to update your Azure AD registration, the Teams app manifest, and the project configuration. A paid account with a permanent ngrok URL is recommended.
- Setup for Bot
-
Register Azure AD application resource in Azure portal
-
In Azure portal, create a Azure Bot resource.
-
Ensure that you've enabled the Teams Channel
-
While registering the bot, use
https://<your_tunnel_domain>/api/messages
as the messaging endpoint.NOTE: When you create your bot you will create an App ID and App password - make sure you keep these for later.
- Setup NGROK
-
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
- Setup for code
-
Clone the repository
git clone https://github.com/OfficeDev/Microsoft-Teams-Samples.git
-
In a console, navigate to samples/meeting-events/nodejs
-
Install modules
npm install
-
Navigate to
samples/meeting-events/nodejs
and update the.env
configuration for the bot to use theMicrosoftAppId
(Microsoft App Id) andMicrosoftAppPassword
(App Password) from the app registration in your Azure portal or from 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.
-
Run your bot at the command line:
npm start
-
Install modules & Run the NodeJS Server
- Server will run on PORT: 3978
- Open a terminal and navigate to project root directory
npm run server
-
This command is equivalent to: npm install > npm start
- Setup Manifest for Teams (This step is specific to Teams.)
-
Modify the
manifest.json
in the/appManifest
folder and replace the following details-
<<App-ID>>
with your Microsoft Entra ID app registration id -
<<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
-
- Upload the
manifest.zip
to Teams- Select Apps from the left panel.
- Then select Upload a custom app from the lower right corner.
- Then select the
manifest.zip
file fromappManifest
.
- Upload the
-
Note: If you are facing any issue in your app, please uncomment this line and put your debugger for local debug.
MeetingEvents command interaction:
End meeting events details:
MeetingParticipantEvents command interaction:
To utilize this feature, please enable Meeting event subscriptions for Participant Join
and Participant Leave
in your bot, following the guidance outlined in the meeting participant events documentation
End meeting events details:
Once the meeting where the bot is added starts or ends, real-time updates are posted in the chat.
To learn more about deploying a bot to Azure, see Deploy your bot to Azure for a complete list of deployment instructions.