cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Having issues trying to access nested data from a parsed JSON

I am fairly new to really digging into PowerAutomate, but I have tried so many different methods and cannot seem to get this one figured out. I have a JSON that is coming in from an HTTP Recieve, then being parsed. I can easily access most data and create variables and throw the data into other areas where needed. However, I am having issues accessing a few pieces of data that is tested within my JSON. I've tried a ton of different expressions to get this, as well as trying to set up a For each, and I think I am out of depth on this one for the time being. If anyone can help take a look, I'd greatly appreciate it!

 

I am trying to take the ouput of our phishing submission system (KnowBe4), then grab specific data to send over to our help desk software for metrics. If I can grab Subject and Message-ID, I can store it in Log Analytics to be cross referenced later, when the ticket is to be closed (I am trying to make it so we can open/close tickets without having to go to the help desk system). The field for "trigger_name" is what I will tell the system who to close the ticket as. Lastly, the "field": "clean", "value": "0.00" (near the bottom of the JSON) both are connected and I would rather it just store the value as "clean":"value". This is more for adding reference in the ticket body for fanciness, so is not totally needed.

 

Also, I don't know if it will help, but most of these fields will always be static and will be there for every message, outside of the "trigger_name". Unfortunately, KnowBe4 doesn't just put 'Closed by' for me to go off of. Instead, they use this "trigger_name" all over the place in the history section of a ticket, which will vary in size. It is always "null" unless there is human interaction that closed the ticket, if that makes sense.

 

 

{
    "body": {
        "headers": [
            {
                "sha1": "08f96a6ac4300",
                "headers": [
                    {
                        "Subject": "You missed a VM= | Transcription Available Play Now 02min57se=  3pm|Friday-February-2024 12:21 PM"
                    },

                    {
                        "Message-Id": "<170811486211.6420.16697328371498069029@takahashibussho.co.jp>"
                    },
                    {
                        "Content-Transfer-Encoding": "7bit"
                    }
                ],
                "filename": "rawHeaders.txt",
                "sha256": "89525511f796c492eb",
            }
        ],
        "addresses": {
            "to": [
                "jeom"
            ]
        },
        "links": [],
        "phishml": {
            "confidence_spam": "0.0002689999237190932",
            "confidence_clean": "0.00001319524653808912",
            "category": "threat",
            "confidence_threat": "0.9997478127479553"
        },
        "history": [
            {
                "date": "2024-02-16T16:08:21-05:00",
                "events": {
                    "phishrip_started": {
                        "queried_fields": [
                            "from",
                            "subject"
                        ],
                        "time_range": {
                            "start_time": "2024-02-15T16:08:15-05:00",
                            "end_time": "2024-02-16 21:08:15 +0000"
                        },
                        "quarantine": "true",
                        "id": "7dd22796-c400-4b9f-9c74-3f198272a36d",
                        "status": "processing"
                    }
                },
                "causer_name": "Threat Email Notification for Reporter"
            },
            {
                "date": "2024-02-16T16:08:15-05:00",
                "trigger_name": "One of three different names here",
                "causer_type": "Action",
                "event_type": "other",
                "trigger_type": "User",
                "events": {
                    "emails": [
                        {
                            "action_email_id": "c4ba53c9-8932-40a7-a347-f0cb74d04f15",
                            "to": [
                                ""
                            ],
                            "email": "Threat Email Notification for Reporter",
                            "status": null
                        }
                    ],
                    "changed_fields": {
                        "action_status": [
                            "received",
                            "resolved"
                        ]
                    }
                },
                "causer_name": "Threat Email Notification for Reporter"
            },
            {
                "date": "2024-02-16T16:07:56-05:00",
                "trigger_name": null,
                "causer_type": "User",
                "event_type": "other",
                "trigger_type": null,
                "events": {
                    "changed_fields": {
                        "viewed": [
                            false,
                            true
                        ]
                    }
                },
                "causer_name": "NAME HERE"
            },
            {
                "date": "2024-02-16T15:22:35-05:00",
                "trigger_name": null,
                "causer_type": "Action",
                "event_type": "other",
                "trigger_type": null,
                "events": {
                    "emails": [
                        {
                            "action_email_id": "0ebd75cc-23ea-4f91-8459-023f81e6c891",
                            "to": [
                                "",
                            ],
                            "email": "Threat Email Notification for Admin",
                            "status": null
                        }
                    ],
                    "tags": {
                        "added": [
                            "MANUAL"
                        ]
                    },
                    "changed_fields": {
                        "severity": [
                            "unknown_severity",
                            "critical"
                        ],
                        "category": [
                            "unknown",
                            "threat"
                        ]
                    }
                },
                "causer_name": "Threat Notification for Admin"
            },
            {
                "date": "2024-02-16T15:22:34-05:00",
                "trigger_name": null,
                "causer_type": "Rule",
                "event_type": "other",
                "trigger_type": null,
                "events": {
                    "tags": {
                        "added": [
                            "KB4:SPF_PASS"
                        ]
                    },
                    "changed_fields": {
                        "pipeline_status": [
                            "processing",
                            "processed"
                        ]
                    }
                },
                "causer_name": "KB4:URGENCY"
            },
            {
                "date": "2024-02-16T15:22:26-05:00",
                "trigger_name": null,
                "causer_type": "Intert",
                "event_type": "other",
                "trigger_type": null,
                "events": {
                    "report": {
                        "name": "VirusTotal",
                        "results": [
                            {
                                "field": "attachment",
                                "value": "JPQN.png"
                            },
                            {
                                "field": "autoscan",
                                "value": "SHA-256 not found."
                            }
                        ]
                    },
                    "tags": {
                        "removed": [
                            "VT_PENDING"
                        ],
                        "added": [
                            "VT_HASH_NOT_FOUND"
                        ]
                    }
                },
                "causer_name": "VirusTotal"
            },
            {
                "date": "2024-02-16T15:22:22-05:00",
                "trigger_name": null,
                "causer_type": "Integrations::PhishMl::Report",
                "event_type": "other",
                "trigger_type": null,
                "events": {
                    "report": {
                        "name": "Phish ML",
                        "results": [
                            {
                                "field": "clean",
                                "value": "0.00"
                            },
                            {
                                "field": "spam",
                                "value": "0.03"
                            },
                            {
                                "field": "threat",
                                "value": "99.97"
                            }
                        ]
                    },
                    "tags": {
                        "added": [
                            "PML:THREAT"
                        ]
                    }
                },
                "causer_name": "Phish ML"
            },
            {
                "date": "2024-02-16T15:22:10-05:00",
                "events": {
                    "part": {

                        "name": "JPQN.png"
                    }
                },
                "causer_name": null
            },
            {
                "date": "2024-02-16T15:22:10-05:00",
                "causer_name": null
            }
        ],
        "bad_links": [],
        "tags": [
            "SUCCESS_TAG"
        ]
    }
}

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

Screenshot 2024-02-20 165835.pngHI,

 

This is the path to get subject as string variable - 

{
  "type": "InitializeVariable",
  "inputs": {
    "variables": [
      {
        "name": "varSubject",
        "type": "string",
        "value": "@{variables('varObject')['body']['headers'][0]['headers'][0]['Subject']}"
      }
    ]
  },
  "runAfter": {
    "Initialize_variable": [
      "Succeeded"
    ]
  }
}
 

Please give kudos and mark as solution if it helps.  

  

Thanks, 

Sandeep Mishra

View solution in original post

8 REPLIES 8
cchannon
Multi Super User
Multi Super User

Well, that's a lot of questions all rolled into one, so I don't think I will be able to answer all of them at once for you but let me try to point you in the right direction.

 

Assuming you are using the ParseJSON Action to convert this JSON into a deserialized Power Automate object, then accessing its members is as simple as walking the JSON tree; even if sometimes the editor window doesn't show you the members.

 

So, for example, to access Subject and Message-Id in Headers[], you will just want to ApplyToEach loop over

MyJSON.Body.Headers

then check each item for the key of "Subject" or "Message-Id" and write those off into a variable or wherever you want to store them.

 

Likewise, to access Trigger-name you would do a ApplyToEach loop over 

MyJSON.Body.History

and, I assume, append each one to an array variable so you can extract them one at a time.

 

And lastly, to access those field/value objects you would nest ApplyToEach loops. Start with a Loop on MyJSON.Body.History, then create another loop inside there for items('Apply_to_each') (or whatever the generated syntax is for your iterable) so that inner loop would be on something like 

items('Apply_to_each').events.report.results

 

Hi @mikraphne ,

 

You have already parsed the incoming JSON data.

Ensure that you have used the 'Parse JSON' action to convert the raw JSON into a format that Power Automate can handle.

To extract specific values from nested data, use the 'Compose' action to create variables for the desired fields like Subject, Message-ID, trigger_name etc.

In the 'Compose' action, use expressions to access the nested properties within your parsed JSON.

For Subject:
outputs('Parse_JSON')['Subject']
For Message-ID:
outputs('Parse_JSON')['Message-ID']
For trigger_name:
outputs('Parse_JSON')['trigger_name']

Refer this youtube video - https://www.youtube.com/watch?v=sqx8in2PJlA

 

Please give kudos and mark as solution if it helps.  

  

Thanks, 

Sandeep Mishra 

I guarantee this is all user error on my part, but I keep trying to do this, and set a variable for Subject.

mikraphne_0-1708357943606.png

Whenever it gets to that step it throws this error:

mikraphne_1-1708357977700.png


I know I have tried this process a few times with For Each, since that seemed to be the suggested thing to do, but I feel like I am setting something incorrectly. It is also a little confusing because there is a "headers" under "headers"

mikraphne_2-1708358055575.png


Is this the one I need, or do I need another For Each loop to go one layer down?

Sorry, I know this is probably super simple for everyone else, but I think I have tried so many different things that I am kinda losing track at this point haha

I tried using outputs('Parse_JSON')['Subject'] and still have no luck. Is it because it is nested in another 'headers'?

 

When it runs, I get:

mikraphne_0-1708372480984.png

I even tried what the video said and haven't had any luck.

I am simply getting JSON from a HTTP Connector, then immediately running Parse_JSON on the body of the HTTP connector:

mikraphne_1-1708373960688.png

 

 

Screenshot 2024-02-20 165835.pngHI,

 

This is the path to get subject as string variable - 

{
  "type": "InitializeVariable",
  "inputs": {
    "variables": [
      {
        "name": "varSubject",
        "type": "string",
        "value": "@{variables('varObject')['body']['headers'][0]['headers'][0]['Subject']}"
      }
    ]
  },
  "runAfter": {
    "Initialize_variable": [
      "Succeeded"
    ]
  }
}
 

Please give kudos and mark as solution if it helps.  

  

Thanks, 

Sandeep Mishra

To make it even more confusing, I got it finally running, but then sent another payload over to it and it failed. It is coming from a system I don't have any access to changing, and I wish they would just put in all the fields with "" for the values that are not there. Instead, the values of "Subject" and "Message-ID" end up moving around. I cut a large portion of the data out for my example, but at one point, I had "Subject" working at [17], then the next run with a different payload ended up being [9]. However, these two fields are guaranteed to always be in the array. I unfortunately can't format them to be in a static location though.

hi @mikraphne ,

 

Step 1- put output in a variable "varObject", then create another variable and use this expression to get the subject. that's it 

 

variables('varObject')['body']['headers'][0]['headers'][0]['Subject']

I feel like this is as close as I have gotten! The JSON above is the raw, so the body part is no longer part of it after I parse it. So, I tried it without [body] and it tells me that Subject does not exist, and told me that a different property "Received" was available, since in this run, it was the first property in the array instead of Subject (which, in this run was actually [20], but that will be different every time..

mikraphne_0-1708440221017.png

 

So, I played around with it and made it:

variables('varObject')['headers']?[0]?['headers']?[0]?['Subject']
Since, I figure I just want it to grab the first instance of headers, then the first instance of Subject. However, the value is coming up blank. It is at least marking the step as successful, instead of failing at it.. Not sure if this is a good or a bad sign at this point.
mikraphne_1-1708440367063.png

 

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (1,177)