← All nodes
Unstructured Text

JSON Formatter

Make JSON readable with consistent indentation, and find out straight away if it is invalid.

When to use it

Typical uses: Reading API responses while debugging; Tidying configuration files before committing them; Checking that JSON is valid before using it.

In a pipeline

Settings

SettingTypeRequiredDefault or hint
Text columnselect—Text
Indentationselect—2
Generate New Columncheckbox—false
New Column Nametext—Default: <column> Result
Insert Afterselect—After the column
When a value cannot be convertedselect—stop

Example

JSON Formatter: an example

    Text arriving
    Text
    {"name":"TextForge","tools":50,"tags":["text","free"],"owner":{"country":"Canada"}}
    The text after this node
    Text
    { "name": "TextForge", "tools": 50, "tags": [ "text", "free" ], "owner": { "country": "Canada" } }

    Worth knowing

    • Why does valid-looking JSON fail? Common causes are trailing commas, single quotes instead of double quotes, comments and unquoted keys. None of these are allowed in standard JSON.
    • Is my data uploaded? No. Parsing and formatting happen entirely in your browser.
    • Does it change my data? The values stay the same. Very large numbers beyond JavaScript’s safe range may lose precision, and duplicate keys keep only the last value.
    • Works on any text column, not only Text Input's: pick it under Text column. Tick Generate New Column to keep the original next to the result.

    Others in Unstructured Text