The Flow Bot should send the message to the bot that you selected, and you should be able to see the bot's response in Microsoft Teams. You can also use dynamic content to insert information from previous steps in the flow, if needed. If you do not see the name of the bot in the dropdown list, you may need to check that the bot is installed and configured properly in Microsoft Teams.Īfter you have selected the recipient, you can enter the message that you want to send in the "Message" field. They may not work correctly and could block publishing. When I import the chatbot into a new environment, I see an error in PVA that says ' We ran into a problem importing some flows. One of these flows has an Adobe Sign connection to send a document for signature. In the "Recipient" field, you should be able to select the name of the bot that you want to send the message to. 11-24-2020 04:25 PM I have a chatbot that calls a few flows. This will ensure that the message is sent to the Flow Bot, which is the account that will receive the message. In the "Post in" field, choose the "Chat with Flow Bot" option. This will ensure that the message is sent from the Flow Bot account, which is the account used by Power Automate to send messages. In the "Post as" field, choose the "Flow Bot" option. That’s it, through basically no code our PVA bot can interact with our Dataverse instance, ask and answer questions to whoever it is chatting to.To send messages to a bot using Power Automate in Microsoft Teams, you will need to do the following:Ĭreate a Power Automate flow that uses the "Post message in a chat or channel" action. We can see this is the title for our case: On entering a case number, the bot returns the title of the case! Let’s display this in a message to the user: Now back on the PVA authoring canvas, we can tie the case number fields together and we see the output is case title. We will finally output our casetitle variable to PVA: We will then add a new action to set our casetitle variable to the Case Title field of the record returned: Now let’s add an Apply to each control, and we will use the value from the List Rows. Now let’s add a variable called casetitle, which will hold the title that we will return to the bot’s chatter: We will do a FetchXML query and pass the casenumber variable as a filter so we only return the case we are after: Scripted rules and, Microsoft AI chatbots provide automated service. Next, add a List rows connector, with the Cases table selected. A Virtual Agent is a digital replication of an employee created within a software program. This will be passed into our flow from the bot: Next let’s call a new action, and we will create a new Power Automate Flow.įor the input, enter casenumber. The question will be “What is the case number to look up?” and we want to identify the user’s entire response as a text string: Go to the authoring canvas, add a new question: Specifically, we will look at the example where a customer asks about a case, and the bot looks asks which case, then looks it up in Dynamics 365, and finally returns case details.įirst, let’s create a new topic called Lookup Case Number: In this post, we will look at how the bot can ask a person questions, send the person’s answer as a parameter to the dataverse, and return data to the person. In a previous post, we showed how a Power Virtual Agent can look up dataverse data and return it to the person chatting to the bot.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |