Just start Power Automate (without the Parsing step) and click on the action that creates the parsed step. Actually, you don't need to write the schema really, just let it create automatically from an example. It is easy to insert this step, but you need to write a JSON scheme in it. We can use values from all the columns that the JSON contains (and since multiple rows are calculated, usually these steps are wrapped in an 'Apply to each' loop). This is usually not enough for us - because we need to reference specific values from columns.īut if we insert the 'Parse JSON' action: They can be written directly, come from an API, or appear in any previous step.īut if they are like this, the next steps can only access the entire object. You need this in almost every workflow - because the structure written in JSON is used very often, even if it is not visible at first glance. This helps extract the data from Excel in a consistent format that is visible to the user. Each object represents a row in the table.

It can 'split' an object, which in Power Automate is often defined by JSON, into specific parts (columns), that can be referenced by subsequent actions in flow. Excel table data can be represented as an array of objects in the form of JSON. The “Parse JSON” action in Power Automate and why is it so important What is Parse JSON for?

Excel parse json