JSON

JSON lets later script steps work with structured data: extract a typed value, check whether a path exists, measure length, or return formatted JSON text. This introduction builds the shortest useful example: SetVariable prepares the JSON String, JSON extracts one property, and PromptMe displays its result.

Create and rename a new Blank script. Manually drag all three commands into the live script in this order: SetVariable → JSON → PromptMe. Do not edit an existing script.

In SetVariable, keep Single and This Script Only, select String, name it s1, and enter this exact example:

{"status":"Ready","count":2,"price":1.5,"enabled":true,"tags":["Demo","Guide"]}

• Mode: Extract returns a typed value; Exists checks whether a path is present; Length counts array items, object keys or String characters; Stringify returns valid Compact or Pretty JSON text. This guide keeps Extract.
• JSON String: s1 names a prior String variable containing JSON. The JSON command does not accept a literal document, file, network response, clipboard or screenshot directly; use an earlier command to prepare the String.
• Scope: keep This Script Only. Script Thread is available when outputs must be visible to called scripts within the same run.
• Path Source: Text for a fixed path, or String var for a path prepared by an earlier command. The video shows the variable field first, then returns to Text and enters $.status.
• Path grammar: $ selects the root; $.status selects the case-sensitive status property; $.tags[0] selects the first tag. Nested dot names and double-quoted bracket keys such as $["key with spaces"] are supported. JSON array indexes start at zero. Wildcards, filters, recursive descent, expressions, slices and negative indexes are unsupported.
• Output Type: keep String and enter s2. String returns text without JSON quotation marks; a JSON null becomes an empty String. A non-String value fails this output type. Other supported outputs are Integer, Decimal, Boolean, String Array and JSON Text.
• Optional outputs: independently enable Success Boolean b1 and Error String s3 under Save Outputs. Bad JSON, invalid or missing paths, and type mismatches fail safely. Success leaves Error empty. Keep these separate from the extracted value.
• Test: previews the current configuration using available values without saving it. This example reports Success and Count 1. If required runtime values are unavailable, the editor explains that limitation. Always play the full script to verify the complete flow.

Save JSON, then configure Standard PromptMe with Header s2 and a Done button using Boolean b2. Play displays the actual extracted Ready text. Done closes the confirmation and the script finishes automatically.

True operation changes clear fields owned only by the operation being left. Ordinary output-enable gates preserve their child destinations. Select the intended operation before filling its settings. Text outputs are capped at the normal String limit; an optional Error output can report truncation even when the operation succeeds. Input JSON is not changed. JSON's own Run Log entries do not include the full input text; an earlier source command may log its own supplied value.

Extract Integer gives later math and conditions a whole number from structured JSON data. This guide reuses the exact object and source command built in Intro, then selects its count property.

• Keep Extract, JSON String s1, Text Path Source and This Script Only.
• Change Path to $.count, choose Integer, and name the active Integer output i1. The unquoted JSON number 2 becomes Integer 2; the original JSON text is unchanged.
• The selected JSON value must be numeric, whole and within signed 32-bit bounds, −2147483648 through 2147483647. Quoted numeric Strings, non-whole fractions, null, arrays, objects and out-of-range values fail this output type.
• Keep optional Success Boolean b1 and Error String s3 from Intro. Check them before relying on a result in a larger script.
• Manually drag Display into the script and place it after JSON, before PromptMe. Choose Once, Source Variable i1, manual Area top-left 100,300 and bottom-right 440,440, and Lifespan 5000 ms. Keep default appearance. These coordinates are only for this example's 540×960 emulator.
• Set Standard PromptMe Header to Complete and keep Done Boolean b2. PromptMe's Header resolves String variables, so Display makes the Integer result visible directly.

Play shows the actual number 2 for five seconds. Display then disappears, PromptMe confirms completion, and Done ends the script. Neither JSON nor Display types into or changes the underlying app.

Extract Decimal makes a JSON number available to later calculations as a Decimal variable. This follow-up reuses the source JSON from Intro and the four-command script built in Extract Integer.

• Keep Extract, JSON String s1, Text Path Source and This Script Only.
• Change Path to $.price, choose Decimal, and name the active output d1. The unquoted JSON number 1.5 becomes Decimal 1.5; the input String is unchanged.
• Use this type for JSON numeric values, including fractional numbers. Quoted numeric Strings, Boolean values, null, arrays and objects do not match Decimal output.
• Keep optional Success Boolean b1 and Error String s3. In a larger script, check them before relying on the extracted result.
• In the existing Display, change Variable i1 to d1. Keep Once, Area 100,300–440,440, Lifespan 5000 ms and default appearance. The coordinates belong to this example's 540×960 emulator; use an appropriate area on your device.
• Keep Standard PromptMe Header Complete and Done Boolean b2. Display shows the number directly; the prompt confirms the script continued afterwards.

Play shows the actual 1.5, then Complete. Done finishes the script. No command in this example types into the underlying app. See Intro for the source object and manual command drags, and Extract Integer for Display insertion and Area setup.

Extract Boolean turns a JSON true or false value into a Boolean variable that later commands can use in conditions. This follow-up reuses the source object from Intro and the four-command example from Extract Integer and Extract Decimal.

• Keep Extract, JSON String s1, Text Path Source and This Script Only.
• Change Path to $.enabled, choose Boolean, and name the active output b3. The unquoted JSON true becomes Boolean True.
• This output type requires a JSON Boolean. Quoted words, numbers, null, arrays and objects do not match it. A successfully extracted false is a valid value, not an extraction failure.
• Keep optional Success Boolean b1 and Error String s3. b3 is the selected value; b1 separately reports whether extraction succeeded. Check status before relying on the result in a larger script.
• Change Display Variable d1 to b3. Keep Once, Area 100,300–440,440, Lifespan 5000 ms and default appearance. These coordinates are for the example's 540×960 emulator; choose an appropriate area on your device.
• Keep Standard PromptMe Header Complete and Done Boolean b2. Display shows the Boolean directly; the prompt confirms execution continued.

Play shows the actual True, then Complete. Done finishes the script. Nothing types into the underlying app, and s1 is unchanged. See Intro for source setup and manual command drags, and Extract Integer for Display insertion and Area setup.

Extract String Array makes the items in a JSON list individually available in consecutive String variable slots. This follow-up starts from Intro and manually adds one supporting TextTransform Join so both results can be displayed in a single PromptMe header.

• Keep Extract, JSON String s1, Text Path Source and This Script Only. Set Path to $.tags and Output Type to String Array.
• Set Array to s and Start to 4. The example's two tags become s4 = Demo and s5 = Guide. These are destination slots, not JSON source indexes.
• Start accepts a positive whole number or an Integer variable prepared earlier. Keep the whole destination range within 1–4096, and avoid overlapping the input or other needed outputs.
• Non-null items are converted to text. Nested objects and lists are serialized as compact JSON text inside their slots. A null item causes a type mismatch. The source JSON String is unchanged.
• Enable optional Save Count and set its Integer destination to i1. Keep Success Boolean b1 and Error String s3; check status before relying on the returned values in a larger script.
• Manually drag TextTransform into the script, choose Join, and use Array s, Start 4, Count i1, Text delimiter | , and output String s6. Keep Join's optional status outputs off.
• Drag Join before PromptMe, then set the Standard prompt's Header to s6. Keep Done Boolean b2.

Play displays the genuine Demo | Guide result. JSON returned count 2, which Join used to read the two extracted slots. Done finishes the four-command script. Join is only for this visible confirmation; later commands can use the extracted slots separately. See Intro for source setup and original manual command drags, and the TextTransform Join guide for that supporting operation.

Extract JSON Text keeps a selected JSON value in JSON form inside one String variable. Use it when a later command needs a whole nested object or list rather than separate variable slots.

• Continue from Intro's three-command example and original manual command drags. Keep Extract, JSON String s1, Text Path Source and This Script Only.
• Set Path to $.tags, choose JSON Text, and enter s2 in its active String destination. JSON Text has its own output setting; the original source in s1 stays unchanged.
• The example saves ["Demo","Guide"] together in s2. Unlike String Array, it does not distribute the items into separate slots.
• Objects and lists retain their JSON structure. Strings are quoted and escaped; numbers, Booleans and null retain their JSON representation. This mode emits compact JSON text.
• Keep Success Boolean b1 and Error String s3. Check these outputs when the input or path may be invalid.
• The existing Standard PromptMe Header s2 displays the actual extracted list. Done sets b2 and completes the three-command script.

See Intro for source setup, path and scope details, and the original manual command insertions.

Exists checks whether a JSON path is present and saves a Boolean result. Use it before later commands, such as IF, that need to handle optional data.

• This follow-up reuses the four-command Boolean example. See Intro for the source JSON and Extract Integer for Display's original manual insertion.
• Keep JSON String s1, Text Path Source and This Script Only. Change Mode from Extract to Exists, set Path to $.missing, and enter b3 in the independent Boolean destination.
• A present value counts even when it is false, zero, an empty String or null. Exists checks presence, not truthiness, and does not extract the selected value.
• Keep Success Boolean b1 and Error String s3. A valid path that is absent returns False in b3 while the check succeeds. Invalid JSON or invalid path syntax is an error.
• The existing Display reads b3 in Once mode, with manual Area 100,300–440,440 and lifespan 5000. Keep custom styles off.
• Standard PromptMe displays the literal header Complete and Done Boolean b2. It confirms that execution continued after Display.

The actual example displays False because the property is absent, then shows Complete. Its run has b3=False, b1=True, an empty error string and no warnings or errors. Done completes the script; the original JSON in s1 is unchanged.

Length measures a selected JSON value and saves an Integer for later decisions or loops. It measures the selected value; it does not extract a property that already stores a number.

• This follow-up reuses the four-command Extract Integer example. Intro covers the JSON in s1; Extract Integer shows Display's original manual insertion.
• Keep JSON String s1, Text Path Source and This Script Only. Change Mode from Extract to Length, enter Path $.tags, then enter i1 in the independent Integer destination.
• A list returns its item count. An object returns its own key count, not a recursive count of nested values. A String returns its Unicode code-point count; joined emoji may use several code points.
• Empty lists, objects and Strings return zero successfully. A missing path, number, Boolean or null cannot supply a length. Keep Success Boolean b1 and Error String s3 to distinguish zero from failure; malformed JSON and invalid path syntax are errors too.
• Display already reads i1 in Once mode, using manual Area 100,300–440,440 and lifespan 5000, with all custom styles off. Standard PromptMe then shows the literal header Complete and Done Boolean b2.

The genuine example displays 2 because tags contains Demo and Guide, then Complete. Four commands finish with no warnings or errors: i1=2, b1=True, an empty error string, and unchanged source JSON in s1.

Stringify formats a selected JSON value into a String for later commands. Compact avoids extra layout; Pretty adds line breaks and indentation to structures. This one guide demonstrates both formats using the same list.

• Reuse a new named copy of the four-command Extract Integer example. Intro explains the source JSON in s1, and Extract Integer shows Display's original manual insertion.
• Keep JSON String s1, Text Path Source and This Script Only. Change Mode to Stringify, set Path to $.tags, keep Compact and enter the independent String destination s2.
• Path selects what is formatted: $ alone formats the whole document. Strings are quoted and escaped as JSON; lists and objects retain structure, while numbers, Booleans and null use JSON representation.
• Keep Success Boolean b1 and Error String s3. Invalid JSON, invalid path syntax and missing paths fail. A long result may reach the String byte limit and report output_truncated while Success remains True; check Error before reusing the result as JSON.
• In Display, keep Once and Variable, change i1 to s2, then tap the Area label. Keep top-left 100,300 and bottom-right X 440, increasing bottom-right Y from 440 to 600 so the separate lines have room. Keep lifespan 5000 and all custom styles off.
• Standard PromptMe retains the literal header Complete and Done Boolean b2. Display shows the actual text, including line breaks; PromptMe confirms that execution continued.
• Run Compact and press Done. Expand the overlay, reopen the editor and JSON, change only Format to Pretty, save, close the editor and play again.

The genuine first run displays ["Demo","Guide"] on one line. The second displays the same list on four indented lines. Each five-second Display naturally leads to Complete and Done. Both four-command runs finish without warnings or errors, with b1=True, an empty error String and unchanged source JSON in s1.