Make Parse JSON: turn text into usable fields

A JSON response can look like one long piece of text. Make's Parse JSON module (opens in a new tab) turns it into fields you can use in later steps.

This practice uses fictional data and built-in modules on Make Free. Keep the scenario Inactive and use Run once.

1. Add the JSON input

1. In Scenarios, click Create scenario. Replace the scenario name at the top left with JSON fields practice.
2. Click the large plus. Choose JSON, then Parse JSON.
3. Leave Data structure empty for this exercise. Paste the example into JSON string.
4. Click the module's Save, then the canvas Save. If the warning only says the output is unused, choose Save anyway.

Enlarge image

Full Make editor showing the Parse JSON input with item Notebook and quantity 2

×

Open full-size image

2. Run the source before mapping it

1. Click Run once. If the same unused-output warning appears, choose Run anyway.
2. Click the result bubble above the JSON module.
3. Under Output, check for one record, called a bundle in Make, with item: Notebook and quantity: 2.

Enlarge image

Full Make editor showing parsed output fields item Notebook and quantity 2

×

Open full-size image

3. Use one field in the next module

1. Close the result panel. Click the plus to the right of the JSON module.
2. Choose Tools, then Set variable.
3. Enter item_label as Variable name.
4. Click Variable value. In the mapping panel, expand JSON 1 - Parse JSON and select item. It should appear as a coloured token.
5. Save the module and scenario. Click Run once again.

Enlarge image

Full Make editor mapping JSON item into the Tools variable item_label

×

Open full-size image

Open the Tools result bubble. Output should contain item_label: Notebook. You have used a parsed field without sending data to another service.

If a field is missing

Run Parse JSON again with representative sample data, then reopen the next module. Check that you selected the token from the JSON module and that the source actually contains that field. Fix invalid punctuation before changing mapping.

This example starts with one object in braces. A top-level array can produce several output bundles, according to Make's JSON documentation (opens in a new tab). Check the bundle count before adding an action that sends or creates records.

When do you need an Iterator? Compare these two shapes while the scenario stays Inactive. Leave Data structure empty for this optional check.

A top-level array

1. Replace JSON string with the array above. Save the module and scenario, then click Run once.
2. Open the JSON result. It contains two output bundles, Notebook and Pencil. The directly connected Tools > Set variable step runs twice, producing one item_label per item. You do not need an Iterator to split these already separate bundles.

Enlarge image

Make Parse JSON showing Notebook and Pencil as two separate output bundles.

×

A top-level array produces two output bundles: Notebook and Pencil.

Open full-size image

An array inside an object

1. Replace JSON string with this second input and save the module. Right-click Parse JSON and choose Run this module only, so the earlier Tools mapping does not run against a different shape.
2. Expand the output. There is one bundle containing an items[] array with both records. Follow the Iterator practice when you need to split an array field into separate bundles.

With an empty root array, [], our direct route produced no output and did not run Tools. Restore the original one-object input and save before returning to the main exercise.

Need an account? Start with Make Free (opens in a new tab). Read the Free-plan guide before turning a practice into a scheduled workflow.