No-Code Workspace — Block Reference

Data and UtilitiesBlock usage recipe

JSON Parse (JSON_PARSE)

Parses JSON and extracts a field via dot-path

Documented for app version 1.0.50Updated: October 2, 2026

What Does It Do?

Parses JSON text coming from HTTP, files, clipboard, or variables and extracts a field through dot-path addressing. It is the main builder block for turning raw text into structured data.

Pro note: treat JSON output as a small contract

Use JSON_PARSE to extract the fields the builder flow actually needs instead of carrying the full raw payload forward. Keep field paths stable and meaningful.

When to Use?

Use it for:

Extracting fields from HTTP responses

Reading structured data from local JSON files or cache

Processing JSON-like content coming from clipboard or other inputs

How to Use?

Add JSON_PARSE

Point Source to the JSON text or variable

Enter a dot-path such as data.user.name

Store the extracted result in the result variable

Parameters

Source

Name of the variable holding the JSON text, a lightbulb binding, a {{ }} template, or inline JSON

JSON Path

Dot path to the field; square brackets for array items, starting at 0 (e.g. items[0].name)

Result Variable

Variable that receives the extracted JSON value

Parameter	Description
Source	Name of the variable holding the JSON text, a lightbulb binding, a {{ }} template, or inline JSON
JSON Path	Dot path to the field; square brackets for array items, starting at 0 (e.g. items[0].name)
Result Variable	Variable that receives the extracted JSON value

Example Usage

Scenario: Extract a user name from an API response

HTTP_REQUEST -> resultVar = apiResponse

JSON_PARSE -> source = apiResponse, path = user.name, resultVar = userName

Show it with LOG "User: {{userName}}"

Combinations / Used With

COMBINATIONS:

HTTP_REQUEST + JSON_PARSE: API-driven flows

FILE_READ + JSON_PARSE: local config loading

JSON_PARSE + COMPARE: branch on structured data

Tip

When the source is raw JSON text, logging the payload first makes path debugging much easier.

Warnings / Cautions

WARNING:

A wrong path or a missing field makes the result nil

Parsing fails if the source is not valid JSON; the result becomes nil and the macro continues, so check it with COMPARE

Step-by-Step Mastery: Basic → Advanced → Pro

The same block at three levels: a quick start, the real options, and professional techniques.

Basic

JSON_PARSE parses the JSON in a variable or inline text and extracts the field you want via a dot-path. For example the path data.value pulls 1 out of {"data":{"value":1}}. The result is stored in the Result Variable you pick. It is the main block for turning raw text into structured data.

Advanced

The generated code calls JSON.parse inside pcall: if the source is not valid JSON the parse fails but the macro does not crash — the result becomes nil. The dot-path walks segment by segment (data -> value); at each step, if the current value is not a table the result safely falls to nil. So a wrong path or unexpected shape yields an empty result rather than an error. In the source you can type a variable's name directly (e.g. apiResponse), bind it with the lightbulb, or write a {{ }} template or inline JSON. Array items use square brackets in the path and start at 0 (e.g. items[0].name). Leaving the path empty gives you the whole parsed root.

Pro

Make JSON_PARSE the heart of API-driven flows: read remote state and decide with HTTP_REQUEST -> JSON_PARSE -> COMPARE. For deep fields you can chain levels; a single block's path descends multiple levels via dots (e.g. user.profile.name). For arrays, don't address a specific element by path — grab the array first and process it with FOR_EACH or LIST logic. If the parse comes back empty, log the raw source first to see the real shape; most errors come from wrong casing or an unexpected wrapper layer (e.g. data.data.value). In a cache pattern, FILE_READ -> JSON_PARSE loads local config so you can run without the network.

Real-World Scenarios — Step-by-Step Recipes

Small, reproducible examples that combine several blocks — build them straight into your own macro.

Extract a user name from an API response

1HTTP_REQUEST -> resultVar = apiResponse
2JSON_PARSE -> source = apiResponse, path = user.name, resultVar = userName
3Show it with LOG "User: {{userName}}"

Read a threshold from local config and branch

1FILE_READ -> path = cache/config.json, resultVar = cfg
2JSON_PARSE -> source = cfg, path = limits.maxRetry, resultVar = maxRetry
3COMPARE -> is counter < maxRetry
4Continue or stop the loop with IF_ELSE

Which Blocks to Pair With — Pro Combinations

This block is useful on its own — but it shines when paired with the right partners.

+ HTTP_REQUEST

Turns the API response into structured fields; the standard partner for remote-data flows.

+ FILE_READ

Reads local JSON config or cache so you can load parameters without the network.

+ COMPARE

Branches on the extracted structured value; the core of data-driven decision logic.

+ MAP

Collects several JSON_PARSE outputs into one map for a readable state bundle.

Common Mistakes and Fixes

A path typo (wrong casing or a missing level). Fix: log the raw source and verify the real field names and any wrapper layer.

Assuming the source is real JSON. Fix: because the parse is pcall'd, invalid JSON silently yields nil; check for empty before using the result.

Trying to address an array element by path. Fix: fetch the array first, then process it element by element with FOR_EACH/LIST.

Pro Tips

An empty result usually comes from an unexpected wrapper layer; try variants like data.data.value instead of data.value.

When you need many fields from one response, extract each with its own JSON_PARSE and collect them in a MAP; the flow stays readable and debuggable.

This Block's Code (Editor View)

Lua

The Lua below is what the Code Editor generates for this block with sample settings. Adding cases, branches, actions or loops, or changing settings, extends the generated code accordingly. Study it to see what the block does under the hood, to learn Lua, or to copy and adapt it. Use the Copy button (top-right) to paste it into the Code Editor, or “Try in Editor →” to run it in the live editor.

lua

Try in Editor →

local json_val = nil

local _jsonOk1, _json_parsed1 = pcall(JSON.parse, "{\"data\":{\"value\":1}}")
if not _jsonOk1 then _json_parsed1 = nil end
json_val = _json_parsed1
if type(json_val) == "table" then json_val = json_val["data"] else json_val = nil end
if type(json_val) == "table" then json_val = json_val["value"] else json_val = nil end

Note: generated code can evolve across versions; helper names (e.g. _reg1, m1) and internal optimizations may change. The logic and the called APIs reflect the block’s behavior.

Block ↔ Lua Mapping →

Shared Controls for This Block Family

The guidance below is not identical for every block. It summarizes the professional controls that most often repeat in the selected block family.

🗃Source and Destination

Use file paths, key names, regex sources, and JSON paths with clear naming discipline.

🧷Default Value

Define default outputs clearly so the builder flow does not collapse when data is missing.

🔄Write Then Read Back

For KV or file writes, verifying the result in the next block is healthier in production-grade flows.

🪶Narrow Output Design

Instead of carrying large raw payloads, extract the value you need and pass it forward via a result variable.

Builder vs Lua Boundary

Raw touch pointer lifecycle stays code-first

TOUCH and TOUCH_BREAK cover recipe-style touch flows. Raw pointer choreography such as Touch.down, Touch.move, Touch.up, Touch.dispatch, Touch.reset, Touch.breakAll, and Touch.releaseAfter is not exposed as a first-class builder block.

Touch.downTouch.moveTouch.upTouch.dispatchTouch.resetTouch.breakAllTouch.releaseAfter

Bounded dialog design is builder-backed; freer composition stays code-first

The DIALOG block and dialog designer cover a bounded field set in the builder: Info Text, Text Input, Checkbox, Description, Radio Group, Dropdown, Multi Select, Tab Group, Date Time, Number Range, Slider, Image Picker, Color Picker, File Picker, Recorder Picker, Tag, Signature, and Spacer. The buttons are designed too: the Positive button and Negative button tabs set each button’s text, background, and border color, corner radius, and minimum height next to a preview. Freer Setting.builder composition, multi-step wizard flows, and mixed HUD/dialog choreography still do not map 1:1 into the builder.

Coming soonv1.0.51Two more fields: Agent Detect references (agent_detect_editor) lets the user pick a saved reference set or add and edit references, and Save confirms the selection; Navigation setup editor (navigation_editor) edits a saved map, marker and route from the Dialog and returns the setup and route selection without moving the character.

Setting.builderDialogHudTextViewAgentDetectEditorNavigationEditor

Advanced HTTP request chaining stays code-first

HTTP_GET, HTTP_POST, and HTTP_PUT cover common fixed-method flows; HTTP_REQUEST covers one bounded request with method, header lines, body, content type, query parameters (GET and DELETE), timeout, and a bounded retry. These blocks never throw; they write the status code (-1 on a network failure). Cookie handling, chained request objects, and lower-level client flows still need the code editor.

Request()Request.setCookieRequest.getCookiesCUSTOM_CODE

General programming surfaces stay code-first

The MAP, LIST, JSON_PARSE, REGEX_MATCH, and METRICS blocks cover the everyday cases: map actions, a static list, reading a value from a JSON path, regex match, find, replace, and split, and metrics actions. The rest of the Map, Array, JSON, Regex, and Metrics APIs (for example Array sort, filter, and map) is broader than the builder recipe model and stays on the CUSTOM_CODE and code editor side.

MapArrayJSONRegexMetrics

Low-level runtime and Lua composition stays code-first

Runtime helpers, raw Request objects, Lua built-ins such as print/pcall/xpcall, and free-form object chaining patterns are represented through CUSTOM_CODE or the code editor.

RuntimeRequestprintpcallxpcallCUSTOM_CODE

Debug Mode and Breakpoints

Each block card now exposes an independent breakpoint toggle. When enabled, the breakpoint preference is stored with the block.

Breakpoints are only emitted into runtime code when Debug Mode is enabled from Visual Builder settings. When Debug Mode is off, breakpoints stay saved but do not pause execution.

Use ASSERT for fail-fast validation, and use breakpoints for step-by-step tracing and controlled pauses in the same flow.

Variable Scope

Variables defined with SET_VARIABLE are accessible throughout the macro (global scope). All blocks can read/write the same variable.

However, a variable defined inside a GROUP will be 'nil' (undefined) until the GROUP executes. Blocks outside the GROUP using this variable may produce unexpected results.

FOR_EACH loop variables (item and index) only carry valid values inside the loop body. Outside the loop they are outside local scope and should not be used.

TRY_CATCH error variable is only valid within the catch block. If the try block succeeds, the catch branch is not entered and the error variable remains undefined.

TIP: Before using a variable inside a GROUP, assign a default value with SET_VARIABLE outside the GROUP. This way the variable won't be nil even if the GROUP has not run.

Inline Expressions

You can embed variable values and calculations into text fields using {{ expression }} syntax. Expressions inside double curly braces are evaluated as Lua code and the result is inserted into the text.

Syntax

{{ expression }}

Examples

Skor: {{ score + 1 }} → "Skor: " .. tostring(score + 1)

{{ name }} kazandı! → tostring(name) .. " kazandı!"

X:{{ x }} Y:{{ y }} → "X:" .. tostring(x) .. " Y:" .. tostring(y)

Supported Blocks

SET_VARIABLELOGCOMPARECLIPBOARD_WRITENOTIFY_TOASTKV_SET

Security Note

Expressions are checked by the sandbox policy. Security-sensitive calls like loadstring, require, debug are automatically blocked.

General Tips

Keep scan regions as small as possible — improves speed, reduces false matches.

Always add an exit condition when using infinite loops (BREAK, timeout, or conditional exit).

Use network operations and error-prone steps inside TRY_CATCH.

If you need global error handling, use the Error Handler (ERROR_HANDLER) block as a singleton in the project.

Small coordinate offsets (CLICK/SWIPE) improve tap accuracy across different DPI and screen scales.

Customize macros with Dialog block — different parameters each run.

Define repeating steps once with GROUP_CALL, call from many places.

Cross-macro local library

Local Shared Macro Area

The Local Shared Macro Area moves blocks, variables, dialog fields, gallery assets, and imported media dependencies between macros on the same device. It is device-local, not cloud sync, not Firebase sharing, and not a replacement for public macro sharing.

Professional usage model: put a reusable login flow, common scan region, shared dialog form, variable group, template image, color profile, replay recording, or imported PLAY_SOUND media file into the shared area from one macro, then import it from the relevant + menu in another macro.

VISUAL_BLOCKSVARIABLESDIALOG_FIELDSTEMPLATE_IMAGECOLOR_SWATCHREPLAY_RECORDMEDIA_FILE

Send to the shared area

When one item or a multi-selection is active, the shared-area button can copy the selected part from the workspace, group, true/false action branch, dialog, and variables surfaces into the device-local library.

Import into another macro

The shared-area entry under the + menu imports the selected item into the surface that opened it. Main workspace, group, action branch, dialog, and variables each receive the compatible item type.

Share gallery assets

Gallery items include template images, color swatches, replay records, and imported audio/media files. They can move between macros on the same device so repeated templates, colors, recordings, and PLAY_SOUND media assets do not need to be captured again.

Keep it clean

The shared area is not a permanent dumping ground. Delete stale shared items from the shared-library panel; imports create a copy in the target macro and do not rewrite the source macro flow.

Checkpoint: after importing, review block names, linked template/image/color/record/media assets, and variable names in the target macro. The shared area creates a copy; delete stale shared items from the shared-library panel to keep the library clean.

AI assistant

Build a block chain with MH AI in natural language

Tell MH AI what you want in plain language; it proposes the right block sequence and lands it in the workspace after you approve. In the current release it works with cloud providers such as Gemini, Claude, and OpenAI; on-device local models are on the roadmap.

Learn more →