No-Code Workspace — Block Reference

SystemBlock usage recipe

HTTP Request (HTTP_REQUEST)

Sends web request (API, webhook)

Documented for app version 1.0.50Updated: October 2, 2026

What Does It Do?

Sends a GET, POST, PUT, DELETE, or PATCH request. In the builder, this block exposes method, header lines, body, content type, and timeout, plus query parameters and retry. The response goes into the result variable and the status code into <result>_code.

Pro note: keep requests bounded and explicit

HTTP_REQUEST represents one bounded production step: method, headers, body, content type, query parameters (GET and DELETE), timeout, and retry stay explicit in one place. The block does not throw on a network failure; check the result variable’s _code value (-1 on a network failure) with Compare before using the result, and pass the result forward through variables.

When to Use?

Use it to:

Send or fetch API data

Trigger a webhook

Report results to a server

How to Use?

Pick the URL and Method

Add query parameters (GET, DELETE) and header lines

Body and Content-Type (POST, PUT, PATCH, DELETE)

Set Timeout (ms) and retry

Check success with <result>_code

Header, query and body values accept {{ variable }}.

Parameters

URL / Method

HTTPS address; GET, POST, PUT, DELETE, PATCH

Header Lines

One "Header: Value" per line, e.g. Authorization: Bearer {{token}}

Body / Content-Type

Body and its type for POST, PUT, PATCH and DELETE

Timeout (ms)

Up to 60000; below 1000 is applied as 1000

HTTP retry

1-4 attempts, delay 0-10000 ms; 408, 425, 429, 500, 502, 503, 504 and network errors

Result Variable

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

Parameter	Description
URL / Method	HTTPS address; GET, POST, PUT, DELETE, PATCH
Header Lines	One "Header: Value" per line, e.g. Authorization: Bearer {{token}}
Body / Content-Type	Body and its type for POST, PUT, PATCH and DELETE
Timeout (ms)	Up to 60000; below 1000 is applied as 1000
HTTP retry	1-4 attempts, delay 0-10000 ms; 408, 425, 429, 500, 502, 503, 504 and network errors
Result Variable	Response body; <name>_code is the status (-1 = network failure)

Example Usage

Scenario: API call with retry

HTTP_REQUEST → GET https://api.example.com/data, retry: 3

COMPARE → http_result_code == 200

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

Combinations / Used With

COMBINATIONS:

HTTP_REQUEST + COMPARE: Check <result>_code after every call

HTTP_REQUEST + JSON_PARSE: Extract response fields

GROUP + HTTP_REQUEST: Periodic sending

Tip

Sends web request (API, webhook)

Warnings / Cautions

WARNING:

HTTPS on public hosts only; internal addresses are rejected

The block never throws: with no connection or a refused request, <result>_code is -1

Retry works for GET, PUT and DELETE; POST and PATCH only with an Idempotency-Key header

At most 5 MB of the response is read

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

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

Basic

HTTP_REQUEST is the full version of a network call: in one block you get the method (GET, POST, PUT, DELETE, PATCH), header lines, body, content-type, query parameters, timeout, retry settings, and a result variable. Use it for API integration, webhook triggering, or remote data fetching. Whenever the simplified HTTP_GET/POST/PUT blocks aren't enough, this block takes over.

Advanced

Pick the method (GET fetches; POST/PUT/PATCH send a body; DELETE removes). Provide header lines in "Header: Value" format — Authorization lives here. Keep Body and Content-Type aligned. Query parameters are appended to the URL as ?a=1&b=2 for GET and DELETE only, with safe encoding of values; cleaner than hand-editing the URL. A Body is sent with POST, PUT, PATCH and DELETE. The retry section: attempts range 1-4 (default 1, i.e. retry off), initial delay and max delay range 0-10000 ms, and the delay doubles on each attempt. Only 408, 425, 429, 500, 502, 503 and 504 responses and network errors are retried; GET, PUT and DELETE always, POST and PATCH only when they carry an Idempotency-Key header. Timeout goes up to 60000 ms, and values below 1000 ms are applied as 1000 ms. URL, Body, Content-Type, Timeout and the retry fields bind to variables with the lightbulb; header, query, Body and Content-Type values also accept the {{ variable }} template, while the URL takes only a lightbulb binding.

Pro

Check http_result_code after every call — the block never throws; a network failure sets the code to -1, and a flow that skips the check carries on with a broken body. Use retry wisely: GET, PUT and DELETE are idempotent and retry safely; POST and PATCH are retried only when you add an Idempotency-Key header, and only do that when the server dedupes requests with the same key, or you'll double-process. Keep backoff's initial delay small (250 ms) and the max around 1-2 seconds; that way transient 500, 502, 503 and 504 errors self-heal without hammering the server. Manage secrets via header + KV_GET, never in the URL/query/body in the clear. Validate the reply with JSON_PARSE; if there's no success field, check http_result_code/body with COMPARE. For periodic sends, run inside GROUP/REPEAT but place a WAIT between turns to respect rate limits.

Real-World Scenarios — Step-by-Step Recipes

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

Safe API call with retry (GET)

1HTTP_REQUEST → Method: GET, URL: https://api.example.com/data
2Query: limit=20
3Retry: max attempts = 3, initial delay = 250 ms, max delay = 2000 ms
4COMPARE → if http_result_code == 200, JSON_PARSE to extract items, process with FOR_EACH
5Otherwise LOG "API unreachable after 3 attempts (code {{http_result_code}})"

Authenticated webhook (POST)

1KV_GET → webhook_token
2HTTP_REQUEST → Method: POST, URL: webhook address
3Header: Authorization: Bearer {{webhook_token}}
4Content-Type: application/json, Body: {"text":"Macro done","id":"{{run_id}}"}
5COMPARE http_result_code, JSON_PARSE the ok field; if the code is -1, LOG the error

Which Blocks to Pair With — Pro Combinations

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

+ COMPARE

Branch on http_result_code: a timeout/connection error never crashes the macro, it sets the code to -1; an unchecked flow carries on with a broken body.

+ JSON_PARSE

Turns the raw reply into structured data so you can safely extract a success field, a list, or a single value.

+ KV_GET

Reads the token/key from safe storage into a header, keeping the secret out of the URL/query/body.

+ COMPARE

Branches on the reply, routing the flow by status, count, or a success flag.

+ GROUP

Loops the request for periodic send/fetch; with a WAIT between turns you respect the rate limit.

Common Mistakes and Fixes

Never reading the status code. A network error or timeout does not stop the macro; http_result_code becomes -1 and the body is an error message. Fix: COMPARE the code after every HTTP_REQUEST.

Enabling retry for POST while assuming the server dedupes — you get double processing. Fix: use an idempotency key, or keep retry off for POST.

Hand-appending query parameters to the URL without encoding special characters. Fix: use the dedicated Query field; values are encoded safely.

Leaving the backoff max delay too high (10 s) so repeated attempts balloon the macro's total time. Fix: keep the max around 1-2 s.

Pro Tips

Enable retry freely only for idempotent methods (GET/PUT/DELETE); for POST, first confirm the server has duplicate protection.

For transient 500, 502, 503 and 504 errors, max attempts = 3, initial = 250 ms, max = 2000 ms is usually a good balance: self-healing without overwhelming the server.

Always JSON_PARSE the reply for a success field; some APIs return HTTP 200 yet report an error in the body.

Bind URL and Body to variables with the lightbulb and use {{ variable }} in header values; you reuse one block across different endpoints and payloads.

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)
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 →