No-Code Workspace — Block Reference

Data and UtilitiesBlock usage recipe

Collection (COLLECTION)

Manages a persistent on-device document collection

Documented for app version 1.0.50Updated: October 2, 2026

What Does It Do?

Manages a named local document collection that persists between runs. Actions: get, put, update, find, list, keys, count, has, delete, clear. It does not sync to the cloud.

When to Use?

Use it to keep the last processed id, an API summary or a small task list between runs.

How to Use?

Pick the action and the collection name

Enter the document id, field, JSON, limit or offset if needed

Write a JSON object for put and update ({{ }} supported)

Take the outcome from the result variable

Parameters

Action and Collection

Action and collection name

Document / Query Fields

Document id, field, value, limit, offset

JSON or Default Value

JSON for put/update, fallback for get

Result Variable

Result of the action

Parameter	Description
Action and Collection	Action and collection name
Document / Query Fields	Document id, field, value, limit, offset
JSON or Default Value	JSON for put/update, fallback for get
Result Variable	Result of the action

Example Usage

COLLECTION put (order_cache, latest, {"status":"ready","updatedAt":"{{nowIso}}"}) → get on the next run → COMPARE

Combinations / Used With

COMBINATIONS:

COLLECTION + JSON_PARSE: Read a document field by field

COLLECTION + FOR_EACH: Iterate a list result

Tip

Manages a persistent on-device document collection

Warnings / Cautions

WARNING:

Does not share data across devices

find, list and keys are bounded (default limit 20)

put writes the whole document; use update for partial changes

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

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

Basic

COLLECTION manages a named local document store on the device. At its simplest you give a Collection name (e.g. sessions), a Document Id and a JSON object and save it with the put action; later you read the same record back with get. The result goes into a Result Variable (default collection_result).

Advanced

Actions: get, put, has, delete, clear, keys, list, find, update, count. put writes a document with documentJson; update partially patches an existing document with patchJson; get reads it (returning defaultValue if missing); has is an existence check, delete removes one document, clear empties the collection. keys returns document ids, list returns documents (paged with limit/offset), count returns the document count. find queries by field with fieldName/fieldValue. The document JSON must be a real JSON object (e.g. {"status":"ready"}); otherwise reads/queries give unexpected results.

Pro

COLLECTION is the only structured store that persists across macro runs (MAP lives only for a single run) — ideal for keeping the last processed id, the last API summary, or a small task queue. A professional pattern: read the previous turn's state with get, COMPARE it against new data, and act only if there is a difference; this eliminates repeated work and needless API calls. Keep collection names workflow-oriented and small (order_cache, seen_ids) — purpose-split small collections are both readable and fast versus one giant bucket. This is not a cloud database but a bounded local store: it does not sync across devices and find/list/keys are bounded (limit defaults to 20), so do not treat it as a large data warehouse. When you need a partial change use update (patchJson) instead of put; put overwrites the whole document while update changes only the fields you provide.

Real-World Scenarios — Step-by-Step Recipes

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

Cache the latest processed order state locally

1Fetch order data with HTTP_REQUEST and JSON_PARSE
2COLLECTION → Action: put, Collection: order_cache, Document Id: latest
3Document JSON: {"status":"ready","updatedAt":"{{nowIso}}"}
4On the next run, read the same record with COLLECTION → get
5Compare the state difference with COMPARE

Track seen ids in a store, skip duplicates

1COLLECTION → Action: has, Collection: seen_ids, Document Id bound to id with the lightbulb
2If TRUE (already seen) skip this turn
3If FALSE process it, then COLLECTION → put to record the same id
4When needed read the total with COLLECTION → count

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

Read the stored document with get and process it field by field with JSON_PARSE.

+ FOR_EACH

Iterate over a list or keys result to process each document one by one.

+ COMPARE

Compare the previous turn's stored state with the new one and act only on change.

+ HTTP_REQUEST

Persist an API response summary to eliminate redundant repeat calls.

+ ERROR_HANDLER

Store the last failure state with put and read it for recovery on the next run.

Common Mistakes and Fixes

Passing the document JSON as plain text or malformed JSON instead of a valid object. Fix: write valid JSON like {"key":"value"} into the put/update field.

Using put for a partial change and overwriting the document's other fields. Fix: use update (patchJson) to change only some fields.

Treating find/list/keys as a large data warehouse and ignoring the limit. Fix: queries are bounded (default 20); set limit/offset for pagination.

Expecting cross-device sharing. Fix: this local store does not sync; use a server via HTTP_REQUEST for central data.

Pro Tips

Keep collection names purpose-driven and small (order_cache, seen_ids); split collections beat one giant bucket in readability and speed.

Use COLLECTION when you need persistence across runs, and MAP when you need temporary in-run state.

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

collection_result = Collection.put("sessions", "session_1", JSON.parse("{\"active\":true}"))

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 →