Sign in to confirm you’re not a bot
This helps protect our community. Learn more

Beginning

0:00

Login to Power Virtual Agents and Create a New Bot

0:11

Create a New Topic

1:05

Choose a Couple of Triggers or Key Phrases for the Bot and Give it a Name

1:30

Add Text to the Message for the Bot's Initial Response

1:45

Rename the Trigger

1:55

Add a New Node for Call To Action to Open Power Automate

2:14

Add a Step Between the Default Connectors to Get Query Results from Azure

2:39

Create New String Variable to Store Query Results

3:51

Add New Action to Apply To Each Value from the Query Results

4:36

Add New Action to Append Data to the Query Results Variable Including ID and Title

5:00

Add an Output to the Final Power Virtual Agent step for Text using the Query Results as the Value

6:23

Rename Flow

7:05

Return to Power Virtual Agent and Create a New Call To Action Using the New Flow

7:16

Add a new Action to Display a Message Containing the Query Results Variable

7:30

Test the By Clicking the Icon in the Upper Right and Passing In the Trigger Phrase

8:20

Fix error in the URL

8:39
How to Create an Azure Boards Chatbot with Power Virtual Agents - No Code Micro Workshop Part 4
17Likes
2,254Views
2022Aug 17
[4 of 4 - #NoCode Micro Workshop] 🚩 The Problem I want to have specific information from Azure DevOps made available (or spoon fed) to me in my own custom way, via Microsoft Teams (or some other chat platform). As comfortable as I have become with the Azure DevOps interface, sometimes just asking someone (i.e., a bot) for help is the fastest path to success. ✏️ Step 1: Create and a Power Virtual Agent Bot and Set Trigger Phrases 00:00 - Beginning 00:11 - Login to Power Virtual Agents and Create a New Bot 01:05 - Create a New Topic 📌 NOTE 📌: It could take a few seconds for the bot is finished being built and before you can create a new topic. 01:30 - Choose a Couple of Triggers or Key Phrases for the Bot and Give it a Name 01:45 - Add Text to the Message for the Bot's Initial Response 01:55 - Rename the Trigger 02:14 - Add a New Node for Call To Action to Open Power Automate ✏️ Step 2: Create New Power Automate Flow to Retrieve Query Results and Store in String 02:39 - Add a Step Between the Default Connectors to Get Query Results from Azure 03:51 - Create New String Variable to Store Query Results ✏️ Step 3: Add New Nodes to Bot Conversation to Retrieve and Display Flow String 04:36 - Add New Action to Apply To Each Value from the Query Results 05:00 - Add New Action to Append Data to the Query Results Variable Including ID and Title 06:23 - Add an Output to the Final Power Virtual Agent step for Text using the Query Results as the Value 07:05 - Rename Flow ✏️ Step 4: Finalize, Test and Publish Bot 07:16 - Return to Power Virtual Agent and Create a New Call To Action Using the New Flow 07:30 - Add a new Action to Display a Message Containing the Query Results Variable 08:20 - Test the By Clicking the Icon in the Upper Right and Passing In the Trigger Phrase 08:39 - Fix error in the URL Links: Get Started with Azure DevOps (Docs) - https://jhand.co/nocode-01 Introduction to Azure DevOps (Learn) - https://jhand.co/nocode-02 Get Started with Azure DevOps (Learn) - https://jhand.co/nocode-03 Overview for Azure Logic Apps (Docs) - https://jhand.co/nocode-04 Introduction to Azure Logic Apps (Learn) - https://jhand.co/nocode-05 Power Automate vs Logic Apps - https://jhand.co/nocode-06 Built-in Connectors in Azure Logic Apps (Docs) - https://jhand.co/nocode-07 Overview - Power Virtual Agents (Docs) - https://jhand.co/nocode-08 Introduction to Power Virtual Agents (Learn) - https://jhand.co/nocode-09 Get Started with Power Automate (Learn) - https://jhand.co/nocode-10 Azure Signup - https://jhand.co/nocode-11 Azure DevOps Signup - https://jhand.co/nocode-12 Power Virtual Agents - https://jhand.co/nocode-13

Follow along using the transcript.

Microsoft Developer

589K subscribers