Skip to content

Latest commit

 

History

History
 
 

nodejs

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
Wiki
Wiki
 
 
appPackage
appPackage
 
 
assets
assets
 
 
images
images
 
 
server
server
 
 
.env
.env
 
 
.eslintignore
.eslintignore
 
 
.eslintrc.js
.eslintrc.js
 
 
.gitignore
.gitignore
 
 
Readme.md
Readme.md
 
 
package.json
package.json
 
 

Readme.md

page_type description products languages extensions urlFragment
sample
Demonstrating on how a bot can receive all channel messages with RSC without @mention.
office-teams
office
office-365
nodejs
contentType createdDate
samples
06/10/2021 01:48:56 AM
officedev-microsoft-teams-samples-bot-receive-channel-messages-withRSC-nodejs

Receive Channel messages with RSC permissions

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.

Key features

  • Showing messages based on option selected

Channel messages

Prerequisites

  1. Office 365 tenant. You can get a free tenant for development use by signing up for the Office 365 Developer Program.

  2. To test locally, NodeJS must be installed on your development machine (version 10.14 or higher).

    # determine node version
node --version

  3. 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.

To try this sample

  • Register Azure AD applications

    • Register your bot using bot channel registration in Azure AD portal, following the instructions here.

    • Ensure that you've enabled the Teams Channel

  • Clone the repository

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

  • In a console, navigate to samples/bot-message-with-RSC/nodejs

    cd samples/tab-stage-view/nodejs

  • Run ngrok - point to port 3978

    ngrok http -host-header=localhost 3978

  • Update the .env configuration for the bot to use the MicrosoftAppId (Microsoft App Id) and MicrosoftAppPassword (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.

  • 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

  • This step is specific to Teams.

    • Edit the manifest.json contained in the appPackage 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) also update the <<DOMAIN-NAME>> with the ngrok URL and add some unique Id to your manifest by replacing it with <<manifest_id>>

    • Zip up the contents of the appPackage folder to create a manifest.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 from appPackage, and then select Add to add the bot to your selected team.

App installation

Permissions

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.

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