Power Automate

Understanding Parse JSON Action in Power Automate (With a Simple Example)

Introduction

When working with Power Automate, you often deal with data in JSON format—especially when using actions like HTTP, Power Apps, Compose, SharePoint, or Dataverse.

However, raw JSON is not easy to work with directly.

That’s where the Parse JSON action becomes useful.

What is Parse JSON in Power Automate?

The Parse JSON action is used to convert raw JSON data into structured data so that Power Automate understands each field and makes it available as dynamic content.

In simple words:

Parse JSON helps you read and use individual values from JSON without writing complex expressions.

Why Do We Need Parse JSON?

Without Parse JSON, you often have to write expressions like:

outputs('Compose')?['Email']

After using Parse JSON:

  • Fields appear directly as dynamic content.

  • You can easily use them in Conditions, Emails, Variables, Updates, and other actions.

  • Your flow becomes cleaner and easier to maintain.

Simple Example: Reading User Details from JSON

Step 1: Sample JSON Data

Assume you receive the following JSON from a Compose action:

{
  "Name": "Krish",
  "Email": "[email protected]",
  "Status": "Approved"
}

Step 2: Add Parse JSON Action

Add a Parse JSON action:

  • Content → Select the output of the Compose action.

  • Schema → Generate from the sample JSON above.

The generated schema will look like this:

{
  "type": "object",
  "properties": {
    "Name": { "type": "string" },
    "Email": { "type": "string" },
    "Status": { "type": "string" }
  }
}

Step 3: Use Parsed Values

After adding the Parse JSON action, fields like Name, Email, and Status will appear as dynamic content.

You can now:

  • Send emails using the Email field.

  • Add conditions based on Status.

  • Update SharePoint or Dataverse columns.

No complex expressions are required.

When Should You Use Parse JSON?

Use Parse JSON when:

  • You receive JSON from Power Apps.

  • You use HTTP requests.

  • You work with arrays or nested objects.

  • You want to avoid expression-based field access.

  • Dynamic content is not visible automatically.

Note: Do not use Parse JSON if dynamic content is already available. Use it only when Power Automate does not understand the data structure.

Conclusion

The Parse JSON action is one of the most important actions in Power Automate. It makes flows readable, reliable, and easy to debug, especially when dealing with APIs or Power Apps inputs.

If you work with JSON—even occasionally—Parse JSON will save you significant time and effort.
Membership not found