page_type | description | products | languages | extensions | urlFragment | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
sample |
Demonstrating on how a bot can receive all channel messages with RSC without @mention. |
|
|
|
officedev-microsoft-teams-samples-bot-receive-channel-messages-withRSC-nodejs |
Using this Node JS sample, a bot can receive all channel messages with RSC without @mention. For reference please check Receive Channel messages with RSC
This feature shown in this sample is currently available in Public Developer Preview only.
-
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
-
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.
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
-
Register a bot with Azure Bot Service, following the instructions here.
-
Ensure that you've enabled the Teams Channel
-
While registering the bot, use
https://<your_ngrok_url>/api/messages
as the messaging endpoint.NOTE: When you create your app registration in Azure portal, 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 -host-header=localhost 3978
- Setup for code
-
Clone the repository
git clone https://github.com/OfficeDev/Microsoft-Teams-Samples.git
-
In the folder where repository is cloned navigate to
samples/bot-receive-channel-messages-withRSC/nodejs
-
Install node modules
Inside node js folder, open your local terminal and run the below command to install node modules. You can do the same in Visual Studio code terminal by opening the project in Visual Studio code.
npm install
-
Update the
.env
configuration for the bot to use theMicrosoftAppId
(Microsoft App Id) andMicrosoftAppPassword
(App Password) from the AAD app registration in Azure portal or from Bot Framework registration.
NOTE: the App Password is referred to as the
client secret
in the azure portal app registration service and you can always create a new client secret anytime.
-
Run your app
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
NOTE:This command is equivalent to: npm install > npm start
-
Run your app
npm start
-
Setup Manifest for Teams
-
Edit the
manifest.json
contained in theappPackage
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
)<<DOMAIN-NAME>>
with base Url domain. E.g. if you are using ngrok it would behttps://1234.ngrok.io
then your domain-name will be1234.ngrok.io
. Replace <> with any GUID or with your MicrosoftAppId/app id -
Zip up the contents of the
appPackage
folder to create amanifest.zip
-
Sideload in a team to test
- Select or create a team
- Select the ellipses ... from the left pane. The drop-down menu appears.
- Select Manage Team, then select Apps
- Then select Upload a custom app from the lower right corner.
- Then select the
manifest.zip
file fromappPackage
, and then select Add to add the bot to your selected team.
-
Adding bot UI:
Hey command interaction:
1 or 2 command interaction:
Adding App to group chat:
Group chat interaction with bot without being @mentioned:
Interacting with the bot in Teams
Select a channel and enter a message in the channel for your bot.
The bot receives the message without being @mentioned.
To learn more about deploying a bot to Azure, see Deploy your bot to Azure for a complete list of deployment instructions.
- Bot Framework Documentation
- Bot Basics
- User Specific Views
- Sequential Workflows
- Up to date cards
- Universal Bot Action Model
- Azure Portal
- Activity processing
- Azure Bot Service Introduction
- Azure Bot Service Documentation
- Azure CLI
- Azure Portal
- Language Understanding using LUIS
- Channels and Bot Connector Service
- dotenv
- Microsoft Teams Developer Platform