No-Code Workspace — Block Reference

SystemBlock usage recipe

HTTP POST (HTTP_POST)

Sends data with a fixed POST request

Documented for app version 1.0.50Updated: October 2, 2026

What Does It Do?

Sends an HTTPS request with the method fixed to POST; more readable than HTTP_REQUEST for webhooks, forms or JSON payloads. The status code goes into <result>_code.

Pro note: keep webhook sends explicit

HTTP_POST removes method-selection clutter from send flows. Fill payload and Content-Type explicitly; because the block never throws, confirm the send was accepted through the result variable’s _code value (2xx accepted, -1 network failure).

When to Use?

Use it to:

Send webhook notifications

Report events to an API

Upload macro results to a server

How to Use?

Enter the HTTPS URL

Put JSON or text in Body; use {{ }} or the lightbulb for variables

Set Content-Type (e.g. application/json)

Check success with <result>_code

Parameters

URL / Header Lines

HTTPS address and one "Header: Value" per line

Body

Text or JSON; {{ }} or lightbulb

Content-Type

Example: application/json

Result Variable

Response body; <name>_code is the status

Parameter	Description
URL / Header Lines	HTTPS address and one "Header: Value" per line
Body	Text or JSON; {{ }} or lightbulb
Content-Type	Example: application/json
Result Variable	Response body; <name>_code is the status

Example Usage

Scenario: Send a webhook

HTTP_POST → Body: {"event":"done","id":"{{runId}}"}

COMPARE → http_result_code == 200

Otherwise LOG "POST failed: {{http_result_code}}"

Combinations / Used With

COMBINATIONS:

HTTP_POST + COMPARE: Confirm the send via <result>_code

SET_VARIABLE + HTTP_POST: Prepare the payload first

DIALOG + HTTP_POST: Send user input

Tip

Sends data with a fixed POST request

Warnings / Cautions

WARNING:

HTTPS on public hosts only

The block never throws: on a network failure <result>_code is -1

Retry repeats a POST only with an Idempotency-Key header; blindly resending can create duplicates

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

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

Basic

HTTP_POST sends data to an HTTPS address — a webhook notification, a form, or a JSON payload. The method is fixed, so you only fill in URL, Body, and Content-Type. It is a clean, readable block for reporting a macro result to a server or notifying an API of an event.

Advanced

Put the HTTPS address in URL, the payload in Body (usually JSON), and the body type in Content-Type (for example application/json). Header lines use the "Header: Value" format and are the right place for authentication. Timeout (ms) stops a slow endpoint from locking the macro. The result variable carries the server's reply; most webhooks just return 200, but some APIs return a useful body you can read with JSON_PARSE. Content-Type must match Body: if you send JSON, set application/json, otherwise the server misinterprets the payload.

Pro

POST never throws; confirm success via http_result_code (2xx) and think about idempotency: if the network drops, resending the same POST can create duplicate records. Where possible, include a unique id in the payload (so the server dedupes) or retry exactly once, deliberately, when the code is -1. The retry setting repeats a POST only when it carries an Idempotency-Key header. Never embed secret tokens in Body — put them in a header and read the token from KV_GET; the body can land in logs and crash reports. Prepare dynamic payloads with SET_VARIABLE and bind the Body field to that variable with the lightbulb; hand-concatenated strings produce broken JSON from a missed quote. If you'll process the reply, validate a success field with JSON_PARSE first.

Real-World Scenarios — Step-by-Step Recipes

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

Send a secure webhook notification

1HTTP_POST → URL: https://api.example.com/hooks/macro, Content-Type: application/json
2Body: {"event":"done","id":"{{run_id}}"}
3COMPARE → if http_result_code == 200 LOG "Webhook sent"
4Otherwise LOG "POST failed (code {{http_result_code}}), retry later"

Send user input to a server

1DIALOG to collect a value → store in note
2SET_VARIABLE → payload = {"note":"{{note}}"}
3HTTP_POST → Body bound to payload with the lightbulb, header: Authorization: Bearer {{token}}; then check http_result_code
4JSON_PARSE to confirm the server's saved field

Which Blocks to Pair With — Pro Combinations

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

+ COMPARE

Confirms the send was actually accepted via http_result_code: 2xx is accepted, -1 is a network failure. POST never throws, so this is the only source of truth.

+ SET_VARIABLE

Prepares the dynamic payload up front so you feed a clean, validated JSON string into Body.

+ JSON_PARSE

Reads the success field (ok, saved) in the server's reply, catching APIs that return 200 yet report an error in the body.

+ KV_GET

Reads the API key from safe storage into a header so the secret never leaks into the body or logs.

+ DIALOG

Feeds the POST body with input collected from the user to relay it to a remote service.

Common Mistakes and Fixes

Embedding a secret token in Body. The body can surface in crash reports and logs. Fix: read the token from KV_GET and put it in an Authorization header.

Content-Type not matching Body — sending JSON but leaving Content-Type empty. The server treats the body as plain text. Fix: set application/json for JSON.

Blindly resending POST after an error creates duplicate records. Fix: include a unique id in the payload, or retry exactly once, deliberately, when the code is -1.

Pro Tips

Always add a run/id field to the webhook body; on a network hiccup the server can dedupe and your POST stays idempotent.

Don't stitch JSON together piece by piece; build it as one SET_VARIABLE template ({"note":"{{note}}"}). A single missed quote silently sends a malformed request.

If you process the reply, first validate a success field (e.g. ok/saved) with JSON_PARSE; some APIs return 200 yet report an error inside.

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:setContentType("application/json")
_req1:setBody("{\"ok\":true}")
http_result = _req1:post()
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 →