page_type | description | products | languages | extensions | urlFragment | |||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
sample |
This sample demos a bot with capability to upload files to SharePoint site and same files can be viewed in Teams file viewer. |
|
|
|
officedev-microsoft-teams-samples-bot-sharepoint-file-viewer-nodejs |
Using this Nodejs sample, a bot with capability to upload files to SharePoint site and same files can be viewed in Teams file viewer.
- Teams SSO (bots)
- Adaptive Cards
- Graph API
- Microsoft Teams is installed and you have an account (not a guest account)
- NodeJS
- ngrok or equivalent tunneling solution
- M365 developer account or access to a Teams account with the appropriate permissions to install an app.
Refer to Bot SSO Setup document.
- Run ngrok - point to port 3978
# ngrok http 3978 --host-header="localhost:3978"
-
SharePoint site configuration
- Login to sharepoint
- Click on
Create site
and selectTeam site
- Enter site name and description of site.
-
From site address eg: 'https://m365x357260.sharepoint.com/sites/SharePointTestSite'
m365x357260.sharepoint.com
- value is sharepoint tenant name.- Click on next. (optional step)Add aditional owner and member.
- Click on Finish.
-
Clone the repository
git clone https://github.com/OfficeDev/Microsoft-Teams-Samples.git
-
In a terminal, navigate to
samples/bot-sharepoint-file-viewer/nodejs
-
Install modules
npm install
If you face any dependency error while installing node modules, try using below command
```bash
npm install --legacy-peer-deps
```
- Update the
.env
configuration for the bot to use the MicrosoftAppId, MicrosoftAppPassword, MicrosoftAppTenantId and ConnectionName generated in Step 1 (Setup for Bot SSO). (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.)
ApplicationBaseUrl
will be your app's base url. For eghttps://xxxx.ngrok-free.app
.SharePointTenantName
will be the tenant name generated in step 3.2.SharePointSiteName
will be the site name created in step 3.
-
Run your bot at the command line:
npm start
- This step is specific to 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<<Microsoft-App-Id>>
(depending on the scenario the Microsoft App Id may occur multiple times in themanifest.json
) - Edit the
manifest.json
forvalidDomains
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
. - 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 to personal/team/groupChat 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.
You can interact with this bot in Teams by sending it a message, or selecting a command from the command list. The bot will respond to the following strings.
-
The
viewfile
command will list all the files that are uploaded to sharepoint site. -
The
uploadfile
command will return a card, which will open a task module from where new files can be uploaded to sharepoint.
To learn more about deploying a bot to Azure, see Deploy your bot to Azure for a complete list of deployment instructions.