Adaptive Cards- Get Input from Card into another flow

Carol Grant · March 2023

I've created an Adaptive Card that is for Record Updates and should be sent to our Records Department. It was fairly easy using the designer, it wrote most of the json for me.

Now I need to know how to get the outputs from the card into another flow when they click Submit. I want to show their updates along with what is currently on the record. I setup my Part 2 flow to be triggered when a HTTP request is received. How do I get the fields into this other flow or connect them?

I found this Action.WebRequest on the Blackbaud site:

{
"type": "Action.Webrequest",
"title": "Mark as deceased",
"url": "https://someWebServiceUrl...",
"data": {
"extraData": "foo"
}
}

I tried putting my url from the HTTP request received but it gave me an error of invalid json.

I am trying to avoid saving the output to a Sharepoint list or Teams. I just want to list it out in a table in an email that is sent to Records. The output/answers from the submitter don't need to be saved anywhere.

Thanks,

Carolyn

Dan Snyder · March 2023

@Carolyn Grant Let me know if I am understanding this right or just DM me and I can talk through with you.

What you found on the website should go at the end of your Compose JSON action in the first flow that is creating the adaptive card. The one card I have set up, my JOSN does not include the data and extra data pieces you got in the sample. The URL is the URL from the HTTP trigger in flow 2. You will have to update the JSON in the When an HTTP request is received in flow 2. I'll give you a sample from mine as an example. Basically I have added Deadline, Proposal Name, Purpose, Planned or Deferred Gift as those are pieces of data collected from the adaptive card.

I think @Ben Lambert describes this process in this blog post.

{

"type": "object",

"properties": {

"uit": {

"type": "string"

},

"context": {

"type": "object",

"properties": {

"recordId": {

"type": "string"

}

},

"data": {

"type": "object",

"properties": {

"Deadline": {

"type": "string"

},

"Proposal Name": {

"type": "string"

},

"Purpose": {

"type": "string"

},

"Planned or Deferred Gift": {

"type": "string"

Ben Lambert · March 2023

Hi @Carolyn Grant,

Dan is correct - the magic trick here is that any of the named fields you define in your adaptive card (meaning, fields you define with an "id" property) will be included in the "data" payload sent to your second Power Automate flow when the webrequest action button is clicked.

Carol Grant · March 2023

@Ben Lambert:
Hi @Carolyn Grant,
Dan is correct - the magic trick here is that any of the named fields you define in your adaptive card (meaning, fields you define with an "id" property) will be included in the "data" payload sent to your second Power Automate flow when the webrequest action button is clicked.

Thank you both!! I missed the second part of Ben's blog.

@Dan Snyder

Heather McLean · March 2023

@Carolyn Grant

Would you be willing to share this project at the user group on 3/21?

Carol Grant · March 2023

@Heather McLean- 3/21 might be too soon for me to get all of the kinks out. I'm still working on the 2nd part of the flow which is sending the email to Records with the updates and what is existing on the record. I would love to in April?

Heather McLean · March 2023

@Carolyn Grant - sure you can absolutely punt to April if that's better for you.

Heather McLean · April 2023

@Carolyn Grant - Are you ready to share this tomorrow at User Group? Would love to see this project!

Carol Grant · April 2023

@Heather McLean- Yes I can share tomorrow.

Adaptive Cards- Get Input from Card into another flow

Comments

Categories