No-Code Workspace — Block Reference

Data and UtilitiesBlock usage recipe

File Read (FILE_READ)

Reads text from a file path

Documented for app version 1.0.50Updated: October 2, 2026

What Does It Do?

Reads text from the configured file path and stores it in a variable. Useful when the builder needs to reuse local logs, exports, or text files created by previous steps.

Pro note: route file reads into validation

FILE_READ can return empty, stale, or malformed content. Validating the result immediately with COMPARE, REGEX_MATCH, or ASSERT makes builder flows safer.

When to Use?

Use it when you want to:

Read text saved by a previous run

Reprocess an exported report

Load file-based state or configuration

How to Use?

Add FILE_READ

Enter the file path

Set the Result Variable

Process the content with STRING_OP, JSON_PARSE, or REGEX_MATCH afterward

Parameters

File Path

Path inside the macro's own file area (e.g. cache/report.json); can be bound with the lightbulb

Result Variable

Variable that will receive the file content

Parameter	Description
File Path	Path inside the macro's own file area (e.g. cache/report.json); can be bound with the lightbulb
Result Variable	Variable that will receive the file content

Example Usage

Scenario: Reprocess a previously saved JSON file

FILE_READ -> path = .../cache/report.json

JSON_PARSE -> extract the needed field

Continue with COMPARE or LOG

Combinations / Used With

COMBINATIONS:

FILE_READ + JSON_PARSE: local JSON pipelines

FILE_READ + REGEX_MATCH: log analysis

FILE_READ + STRING_OP: raw text cleanup

Tip

Place file reads at deliberate data handoff points, not randomly in the middle of a flow.

Warnings / Cautions

WARNING:

If the file is missing, the block raises an error and the macro stops; catch it with TRY_CATCH or ERROR_HANDLER

Files larger than 10 MB are not read and the result stays empty

The path field does not resolve {{ }} templates; bind it to a variable with the lightbulb for a dynamic path

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

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

Basic

FILE_READ reads the text at the path you provide and stores it in the Result Variable you pick. It is the simplest way to load back a log, report, or config a previous run saved. The content comes back as plain text; for structured data, process it next with JSON_PARSE or REGEX_MATCH.

Advanced

The path always resolves inside the app-owned sandbox directories; paths that escape the sandbox or are invalid are rejected. The generated code checks File.exists first and raises an error when the file is missing, so you get a clear failure instead of a silent empty value. A file larger than 10 MB is not read: the result stays empty and a log entry is written; re-reading very large files inside the builder is wasteful anyway. The path field does not resolve templates; for a dynamic path build it with SET_VARIABLE (e.g. path = reports/{{day}}.txt) and bind the field to that variable with the lightbulb. The path still passes sandbox validation at runtime.

Pro

Use FILE_READ to carry state between macro runs: read the JSON a previous run left with FILE_WRITE, then feed it into JSON_PARSE. Caching the result of expensive steps (OCR, HTTP) to a file and reading it back lets you skip noisy network calls or screen scans on later runs. In critical flows wrap the read in ERROR_HANDLER or TRY_CATCH; because a missing/inaccessible file raises an error, your recovery branch takes over. Keep the path stable and meaningful (e.g. cache/report.json) and share the same path with FILE_WRITE as a single source of truth.

Real-World Scenarios — Step-by-Step Recipes

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

Reprocess the previous run's JSON cache

1FILE_READ -> path = cache/report.json, resultVar = rawJson
2JSON_PARSE -> source = rawJson, path = data.value, resultVar = lastValue
3COMPARE -> compare lastValue against a threshold
4Record the outcome with LOG

Scan a local log file for a pattern

1FILE_READ -> path = logs/run.txt, resultVar = logText
2REGEX_MATCH -> source bound to logText with the lightbulb, pattern = ERROR.*, action = match, resultVar = firstError
3IF_ELSE -> if firstError is not empty, NOTIFY_TOAST

Which Blocks to Pair With — Pro Combinations

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

+ JSON_PARSE

Turns the raw JSON text read from disk into a structured field; the core of local data pipelines.

+ REGEX_MATCH

Extracts precise patterns (error lines, codes, IDs) from log or free-text files.

+ STRING_OP

Cleans the raw text with trim/replace/split and normalizes it before branching.

+ FILE_WRITE

A write/read pair sharing one path is the basis for carrying durable state across runs.

Common Mistakes and Fixes

Giving an absolute path outside the sandbox (e.g. /sdcard/...). Fix: use relative paths inside the app-owned sandbox (cache/..., logs/...); paths that escape are rejected.

Assuming the file exists. Fix: the block already checks File.exists and errors when missing; in critical flows wrap the read in ERROR_HANDLER/TRY_CATCH.

Re-reading a very large file inside a loop. Fix: keep the file under 10 MB (larger files are not read) and read once outside the loop, keeping the result in a variable.

Pro Tips

Cache expensive OCR/HTTP results with FILE_WRITE and read them back with FILE_READ to skip network/screen scans on repeat runs.

Log the read text immediately to see the actual content; tuning JSON paths or regexes against real data is far faster.

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 fileText = nil

local _file_path1 = "scripts/input.txt"
if not File.exists(_file_path1) then
 error("FILE_READ target missing or inaccessible")
end
fileText = File.readText(_file_path1)

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 →