No-Code Workspace — Block Reference

SystemBlock usage recipe

HTTP GET (HTTP_GET)

Fetches data with a fixed GET request

Documented for app version 1.0.50Updated: October 2, 2026

What Does It Do?

Sends an HTTPS GET request without method selection. A simple block for fetching API data and extracting it with JSON_PARSE. The response body goes into the result variable and the status code into <result>_code.

Pro note: separate reads from sends

HTTP_GET keeps read-only flows away from POST/PUT payload settings. That separation improves readability and debugging in larger builder projects.

When to Use?

Use it to:

Read JSON or text from an API

Fetch remote state or configuration

Call read-only endpoints

How to Use?

Enter the HTTPS URL or bind it with the lightbulb

Add Query Parameters and header lines if needed; values accept {{ }}

Set the timeout and retry

Check success with <result>_code

Parameters

URL

Full HTTPS address; can be bound with the lightbulb

Query / Header Lines

One key: value or "Header: Value" per line; values accept {{ }}

Timeout (ms)

Up to 60000; below 1000 is applied as 1000

Result Variable

Response body; <name>_code is the status (-1 = network failure)

Parameter	Description
URL	Full HTTPS address; can be bound with the lightbulb
Query / Header Lines	One key: value or "Header: Value" per line; values accept {{ }}
Timeout (ms)	Up to 60000; below 1000 is applied as 1000
Result Variable	Response body; <name>_code is the status (-1 = network failure)

Example Usage

Scenario: Read status from an API

HTTP_GET → https://api.example.com/status, result: http_result

COMPARE → http_result_code == 200

If yes JSON_PARSE, otherwise LOG "Code: {{http_result_code}}"

Combinations / Used With

COMBINATIONS:

HTTP_GET + COMPARE: Confirm success via <result>_code

HTTP_GET + JSON_PARSE: Extract the response

KV_GET + HTTP_GET: Add a token to a header with {{ }}

Tip

Fetches data with a fixed GET request

Warnings / Cautions

WARNING:

HTTPS on public hosts only; internal addresses are rejected

The block never throws: on a network failure <result>_code is -1 and the result holds the error text

Sends no body; use HTTP_POST or HTTP_PUT to send data

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

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

Basic

HTTP_GET fetches data from an HTTPS address in one clean step. You just type the URL — no method dropdown to fight — and the reply lands in the result variable you name. It is the simplest way to read status from an API, pull a remote JSON file, or check what an endpoint returns. It sends no body; it only reads.

Advanced

Put the full HTTPS URL in the URL field, and add "Header: Value" lines when an endpoint needs them (for example "Authorization: Bearer ..."). Timeout (ms) caps how long the request waits, so a slow server can't hang the macro forever. The result variable holds the response BODY, and a status companion arrives beside it: if your result variable is http_result, http_result_code carries the HTTP status (-1 on a network failure). Use the result with JSON_PARSE, COMPARE, or LOG. To take the address from a variable, bind the URL field with the lightbulb; Query Parameters and header values accept the {{ variable }} template (the URL field itself does not resolve templates). This block deliberately hides Body and Content-Type; switch to HTTP_POST or HTTP_PUT when you need to send data.

Pro

GET never stops the macro on a network error: a dropped connection, DNS failure, or timeout sets the status code to -1. So after every call, COMPARE http_result_code (200 = success, -1 = network failure) and branch. Don't trust the raw reply blindly — run JSON_PARSE to extract the field you expect, then COMPARE to branch, so an unexpected body doesn't crash the flow. If credentials are needed, never put the token in the URL (URLs leak into logs and proxies); read it from KV_GET and place it in an Authorization header instead. When polling, put a WAIT between requests and keep Timeout sane; aggressive loops burn both battery and the server's rate limit.

Real-World Scenarios — Step-by-Step Recipes

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

Read API status and branch

1HTTP_GET → URL: https://api.example.com/status, result: http_result
2COMPARE → is http_result_code == 200?
3If yes: JSON_PARSE → source: http_result, path: ok, result: status; continue when status == true
4If not: LOG "GET failed (code {{http_result_code}}), might be offline"

Pull remote configuration

1KV_GET → read api_token variable
2HTTP_GET → header line: Authorization: Bearer {{api_token}}
3COMPARE http_result_code == 200, then JSON_PARSE to extract feature_enabled
4IF_ELSE to toggle the feature on/off

Which Blocks to Pair With — Pro Combinations

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

+ COMPARE

Lets you branch on http_result_code: 200 is success, -1 is a network failure. GET never throws; a flow that skips the code check carries on with a broken body.

+ JSON_PARSE

Turns the raw reply into structured data so you can safely extract one field and branch on it.

+ COMPARE

Routes the flow based on the parsed value — decisions like is the state 'ok', is the number over a threshold.

+ KV_GET

Stores the token/key safely and feeds it into a header, authenticating without baking the secret into the URL or body.

+ LOG

Surfaces the raw reply or extracted field so, while debugging, you see what the server actually returned.

Common Mistakes and Fixes

Never checking the status code. GET does not throw: when the network drops the status code is -1 and the result body is an error message — an unchecked flow mistakes that body for a real reply. Fix: COMPARE http_result_code == 200 after every GET.

Entering an http:// address. This block only accepts HTTPS; plain http is rejected. Fix: make sure the URL starts with https://.

Putting the token in the URL query string (…?token=abc). The URL leaks into logs and server access records. Fix: place the secret in an Authorization header.

Pro Tips

Never consume the reply directly; pull the single field you expect with JSON_PARSE. That keeps the flow controlled even if the server changes its format.

When polling, keep Timeout short (e.g. 8000 ms) and add a WAIT in the loop; otherwise one stuck request delays the next scan.

Build the address with SET_VARIABLE (url = https://api.example.com/items/{{id}}) and bind the URL field to url with the lightbulb; one block then serves many records.

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

local _req1 = Request("https://example.com")
_req1:setTimeout(15000, 15000)
_req1:setHeader("Accept", "application/json")
http_result = _req1:get()
if type(http_result) == "table" and http_result.getData ~= nil then
  http_result_code = http_result:getResponseCode()
  http_result = http_result:getData()
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.

⚙️Command Type

SYSTEM and PANEL_CONTROL first choose a command type; the rest of the fields only make sense in that context.

🧾Argument Semantics

arg1/arg2 or panel fields do not mean the same thing across every command; fill them according to that command.

🧪Dry-Run Thinking

Testing risky system actions with LOG or NOTIFY before going live makes builder flows safer.

🕒Synchronization Waits

Add short waits after app launches, panel state changes, or settings-navigation steps.

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 →