No-Code Workspace — Block Reference

Data and UtilitiesBlock usage recipe

Regex Match (REGEX_MATCH)

Matches, extracts, replaces, or splits with regex

Documented for app version 1.0.50Updated: October 2, 2026

What Does It Do?

Performs regex-based text work when you need precise pattern handling. It is the most powerful builder-side text tool for extracting OTPs, IDs, prices, line patterns, or structured fragments.

Pro note: regex blocks are for cleanup and parsing

REGEX_MATCH is not a full text-processing runtime. It is best used to clean noisy text, extract one target value, and strengthen a control condition. Keep patterns short and intentional.

When to Use?

Use it for:

Pattern-based extraction such as OTPs, order IDs, or prices

Find/replace cleanup

Checking whether a pattern exists

Splitting text by regex

How to Use?

Add REGEX_MATCH

Type the source text or bind the field to a variable with the lightbulb

Enter the regex pattern

Choose the mode: match (first matching text), matchAll (list of all matches), find (true/false), replace, or split

Save the result in a result variable

Parameters

Source

Text that the regex will run against

Pattern

Regular expression pattern

Mode

match, matchAll, find, replace, or split

Result Variable

Variable that receives the regex result

Parameter	Description
Source	Text that the regex will run against
Pattern	Regular expression pattern
Mode	match, matchAll, find, replace, or split
Result Variable	Variable that receives the regex result

Example Usage

Scenario: Extract an 8-digit code from an order message

REGEX_MATCH -> source bound to message with the lightbulb

pattern = [0-9]{8}

mode = match

resultVar = orderCode

Combinations / Used With

COMBINATIONS:

TEXT / CLIPBOARD_READ + REGEX_MATCH: precise extraction from raw text

REGEX_MATCH + COMPARE: branch if the pattern exists

REGEX_MATCH + FILE_WRITE: export cleaned output

Tip

A wrong regex is hard to recover from later. Validate your patterns against small examples first.

Warnings / Cautions

WARNING:

Overly broad patterns can create false matches

In replace mode, a bad pattern can wipe more text than expected

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

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

Basic

REGEX_MATCH works with regular expressions when you need more precise text handling. You choose the source text, the pattern, and the mode; the result is stored in the Result Variable. It is the most powerful text tool for extracting OTPs, order numbers, prices, or a specific line pattern.

Advanced

Mode choices: match (returns the complete first matching text, group 0, anywhere in the source; nil when there is no match), matchAll (returns all matching texts as an ordered list), find (returns only true/false for pattern presence, not the matching text), replace (replaces all matches with replacement and returns text), and split (uses the pattern as a separator to split the text). match is not implicitly anchored to the start; use ^ when the start is required. A successful zero-length match returns an empty string, which is distinct from nil for no match. Fill the replacement field for replace. The source field takes what you type as plain text; to scan a variable, bind the field with the lightbulb. matchAll and split return a Lua table for FOR_EACH; configure the next block for the selected mode's result type.

Pro

Make REGEX_MATCH the precise tool for fixed-pattern extraction: use [0-9]{6} for a 6-digit OTP from an SMS/notification, a prefixed pattern for an order code, a decimal pattern for a price, and take the first matching text with match. Avoid overly broad patterns; greedy ones like .* capture more than intended and, especially in replace mode, cause large data loss. The most robust pipeline is usually light cleanup with STRING_OP first, then a narrow REGEX_MATCH. Validate your pattern against small samples first; a wrong regex is hard to fix later. You can iterate a matchAll output with FOR_EACH and route each match to a MAP or separate processing.

Real-World Scenarios — Step-by-Step Recipes

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

Extract an 8-digit code from a message

1CLIPBOARD_READ or TEXT -> resultVar = message
2REGEX_MATCH -> source bound to message with the lightbulb, pattern = [0-9]{8}, action = match, resultVar = orderCode
3IF_ELSE -> if orderCode is not empty, continue

Collect all error codes in a log

1FILE_READ -> path = logs/run.txt, resultVar = logText
2REGEX_MATCH -> source bound to logText with the lightbulb, pattern = E[0-9]{3}, action = matchAll, resultVar = codes
3FOR_EACH -> list = codes (type the bare name; {codes} would be read as a different name), write each code into a MAP

Which Blocks to Pair With — Pro Combinations

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

+ TEXT / CLIPBOARD_READ

The standard input for extracting precise data (OTP, ID, price) from raw on-screen or clipboard text.

+ COMPARE

Branches on whether a pattern was found; the basis of presence-driven decisions.

+ FOR_EACH

Since matchAll/split return a table, it's the natural partner to process every match element by element.

+ STRING_OP

Cleaning noise with STRING_OP first, then applying a narrow regex, reduces false matches.

Common Mistakes and Fixes

Using an overly broad pattern (greedy like .*). Fix: narrow the pattern (e.g. [0-9]{6}) and validate it against small samples first.

Wiping more text than expected with a bad pattern in replace mode. Fix: use match to inspect the first captured text and matchAll to inspect all matches before replace.

Forgetting matchAll/split return a table, not a single string. Fix: process those outputs with FOR_EACH rather than COMPARE.

Pro Tips

When capturing an OTP/code, add boundaries: an anchored pattern instead of bare [0-9]{6} filters out false positives (dates, balances).

While developing, log the text captured by match; use find only for a presence check. Once the pattern is right, switch to matchAll or replace.

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

regex_val = Regex.match("h.*o", "hello")

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 →