ListBot: Your Ultimate List Management Companion. Powered by advanced AI capabilities, this innovative bot is designed to streamline task list. With the ability to create, update, and search lists and tasks, the ListBot offers a seamless and efficient solution to help you stay on top of your to-do's and maximize productivity. Experience the ease of list management like never before, as the ListBot harnesses the power of AI to simplify your workflow and bring order to your daily tasks and showcases the action chaining capabilities.
It shows Teams AI SDK capabilities like:
Throughout the 'index.ts' file you'll see the scaffolding created to run a Bot, like storage, authentication, task modules, and action submits.
The 'generate.txt' and 'update.txt' files have descriptive prompt engineering that, in plain language, instructs GPT how the message extension should conduct itself at submit time. For example, in 'generate.txt':
This is a Microsoft Teams extension that assists the user with creating posts.
Using the prompt below, create a post that appropriate for a business environment.
Prompt: {{data.prompt}}
Post:
// Register action handlers
app.ai.action('createList', async (context: TurnContext, state: ApplicationTurnState, data: EntityData) => {
ensureListExists(state, data.list);
return true;
});
app.ai.action('deleteList', async (context: TurnContext, state: ApplicationTurnState, data: EntityData) => {
deleteList(state, data.list);
return true;
});
app.ai.action('addItem', async (context: TurnContext, state: ApplicationTurnState, data: EntityData) => {
const items = getItems(state, data.list);
items.push(data.item);
setItems(state, data.list, items);
return true;
});
app.ai.action('removeItem', async (context: TurnContext, state: ApplicationTurnState, data: EntityData) => {
const items = getItems(state, data.list);
const index = items.indexOf(data.item);
if (index >= 0) {
items.splice(index, 1);
setItems(state, data.list, items);
return true;
} else {
await context.sendActivity(responses.itemNotFound(data.list, data.item));
// End the current chain
return false;
}
});
app.ai.action('findItem', async (context: TurnContext, state: ApplicationTurnState, data: EntityData) => {
const items = getItems(state, data.list);
const index = items.indexOf(data.item);
if (index >= 0) {
await context.sendActivity(responses.itemFound(data.list, data.item));
} else {
await context.sendActivity(responses.itemNotFound(data.list, data.item));
}
// End the current chain
return false;
});
app.ai.action('summarizeLists', async (context: TurnContext, state: ApplicationTurnState, data: EntityData) => {
const lists = state.conversation.value.lists;
if (lists) {
// Chain into a new summarization prompt
state.temp.value.lists = lists;
await app.ai.chain(context, state, 'summarize');
} else {
await context.sendActivity(responses.noListsFound());
}
// End the current chain
return false;
});
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.
-
Clone the repository
git clone https://github.com/Microsoft/teams-ai.git
-
In the root JavaScript folder, install and build all dependencies
cd teams-ai/js yarn install yarn build cd samples/04.ai.d.chainedactions.listbot
You can interact with the bot by asking for a summary of the list, adding new items to the list, or removing them. You can also ask the bot to find an item in the list.
The easiest and fastest way to get up and running is with Teams Toolkit as your development guide. To use Teams Toolkit to automate setup and debugging, please continue below.
Otherwise, if you only want to run the bot locally and build manually, please jump to the BotFramework Emulator section.
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
- Update the
.env
file and provide your OpenAI Key key for leveraging GPT - 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.
You can also use the Teams Toolkit CLI to run this sample.
-
Install the CLI
npm install -g @microsoft/teamsfx-cli
-
Open a second shell instance and run ngrok tunneling service - point to port 3978
ngrok http --host-header=rewrite 3978
-
Copy the ngrok URL and put the URL and domain in the
/env/env.local
fileBOT_ENDPOINT=https://{ngrok-url}.ngrok.io BOT_DOMAIN={ngrok-url}.ngrok.io
-
Update the
.env
file and provide your OpenAI Key key for leveraging GPT -
In the repository directory, run the Teams Toolkit CLI commands to automate the setup needed for the app
cd teams-ai/js/samples/04.ai.d.chainedactions.listbot/ teamsfx provision --env local
-
Next, use the CLI to validate and create an app package
teamsfx deploy --env local
-
Finally, use the CLI to preview the app in Teams
teamsfx preview --env local
If you used Teams Toolkit in the above steps, you can upload a custom app to a desktop client using the
/appPackage/appPackage.local.zip
file created by the tools and skip to step 6.
-
In a terminal, navigate to
teams-ai/js/samples/04.ai.d.chainedactions.listbot/
cd teams-ai/js/samples/04.ai.d.chainedactions.listbot
-
Run ngrok tunneling service - point to port 3978
ngrok http --host-header=rewrite 3978
-
Create Bot Framework registration resource in Azure
- Use the current
https
URL you were given by running ngrok. Append with the path/api/messages
used by this sample. - Ensure that you've enabled the Teams Channel
- Use the current
-
Update the
.env
configuration 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.) -
Update the
.env
file and provide your OpenAI Key key for leveraging GPT -
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${{TEAMS_APP_ID}}
(depending on the scenario the Microsoft App Id may occur multiple times in themanifest.json
). If you haven't created an Azure app service yet, you can use your bot id for the above. You're bot id should be pasted in where you see${{BOT_ID}}
. Replace everywhere you see${{BOT_DOMAIN}}
with the domain part of the URL created by your tunneling solution. - Zip up the contents of the
appPackage
folder to create amanifest.zip
- Edit the
-
Run your app from the command line:
yarn start
-
Upload the app file (manifest.zip created in the previous step) in Teams.
Bot Framework Emulator Allows testing bots independently from Channels when developing your bot. If you do not wish to use Teams Toolkit, please follow the steps below to test your bot in Emulator.
- Download and install Bot Framework Emulator
- Launch Bot Framework Emulator
- Run the app you are in the directory for.
yarn start
- Add your app's messaging endpoint to the "Open a Bot" dialog. The endpoint your localhost endpoint with the path
/api/messages
appended. It should look something like this:http://localhost:3978/api/messages
.
- In order to test remote apps, you will need to use a tunneling service like ngrok along with an Microsoft App Id and password pasted into the dialog shown above..
- Channel-specific features (For example, Teams Message Extensions) are not supported in Emulator and therefore not fully-testable.
- If you are building, testing and publishing your app manually to Azure, you will need to put your credentials in the
.env
file.
You can use Teams Toolkit for VS Code or CLI to host the bot in Azure. The sample includes Bicep templates in the /infra
directory which are used by the tools to create resources in Azure.
To configure the Azure resources to have an environment variable for the OpenAI Key:
- Add a
./env/.env.staging.user
file with a new variable,SECRET_OPENAI_KEY=
and paste your OpenAI Key.
The SECRET_
prefix is a convention used by Teams Toolkit to mask the value in any logging output and is optional.
Use the Provision, Deploy, and Publish buttons of the Teams Toolkit extension or from the CLI with teamsfx provision
and teamsfx deploy
. Visit the documentation for more info on hosting your app in Azure with Teams Toolkit.
Alternatively, you can learn more about deploying a bot to Azure manually in the Deploy your bot to Azure documentation.