page_type | description | products | languages | extensions | urlFragment | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
sample |
This sample app demonstrate is how to incorporate basic conversational flow into a Teams application. |
|
|
|
officedev-microsoft-teams-samples-bot-conversation-java |
Bot Framework v4 Conversation Bot sample for Teams.
This bot has been created using Bot Framework. This sample shows how to incorporate basic conversational flow into a Teams application. It also illustrates a few of the Teams specific calls you can make from your bot.
This sample is a Spring Boot app and uses the Azure CLI and azure-webapp Maven plugin to deploy to Azure.
- Intall Java 1.8+ Java
- Install Maven
- Setup for Java and Maven Setup
- An account on Azure if you want to deploy to Azure.
- Microsoft Teams is installed and you have an account
- ngrok or equivalent tunnelling solution
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 -host-header=rewrite 3978
-
Setup for Bot
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 Azure Active Directory 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 ngrok. Append with the path/api/messages
-
Clone the repository
git clone https://github.com/OfficeDev/Microsoft-Teams-Samples.git
-
Update the
resources/application.properties
file configuration in your project, for the bot to use the Microsoft App Id and 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.) -
From the root of this project folder: (
samples/bot-conversation/java
)- Open a terminal and build the sample using
mvn package
command - Install the packages in the local cache by using
mvn install
command in a terminal - Run it by using
java -jar .\target\bot-teams-conversation-sample.jar
command in a terminal
- Open a terminal and build the sample using
-
This step is specific to Teams.
- Edit the
manifest.json
contained in theteamsAppManifest
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
forvalidDomains
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
. - Zip up the contents of the
TeamsAppManifest
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
You can interact with this bot by sending it a message, or selecting a command from the command list. The bot will respond to the following strings.
- Result: The bot will send the welcome card for you to interact with
- Valid Scopes: personal, group chat, team chat
- Result: The bot will respond to the message and mention the user
- Valid Scopes: personal, group chat, team chat
- Result: The bot will send a 1-on-1 message to each member in the current conversation (aka on the conversation's roster).
- Valid Scopes: personal, group chat, team chat
You can select an option from the command list by typing @TeamsConversationBot
into the compose message area and What can I do?
text above the compose area.
You may encounter permission-related errors when sending a proactive message. This can often be mitigated by using MicrosoftAppCredentials.TrustServiceUrl()
. See the documentation for more information.
To learn more about deploying a bot to Azure, see Deploy your bot to Azure for a complete list of deployment instructions.