No-Code Workspace — Block Reference

SystemBlock usage recipe

HTTP PUT (HTTP_PUT)

Updates data with a fixed PUT request

Documented for app version 1.0.50Updated: October 2, 2026

What Does It Do?

Sends an HTTPS PUT request that updates an existing record; Body and Content-Type are available. The status code goes into <result>_code.

Pro note: preserve update semantics

HTTP_PUT communicates update flows without mixing them with POST creates. Verify the target URL and payload carefully.

When to Use?

Use it to:

Change a remote setting

Update an existing API resource

Keep create-via-POST and update-via-PUT separate

How to Use?

Enter the target HTTPS URL

Put the new value in Body ({{ }} supported)

Set Content-Type

Check <result>_code; turn on retry for transient errors

Parameters

URL / Header Lines

HTTPS address and one "Header: Value" per line

Body / Content-Type

Text or JSON and its type

HTTP retry

1-4 attempts on 408, 425, 429, 500, 502, 503, 504 and network errors, doubling the delay

Result Variable

Response body; <name>_code is the status

Parameter	Description
URL / Header Lines	HTTPS address and one "Header: Value" per line
Body / Content-Type	Text or JSON and its type
HTTP retry	1-4 attempts on 408, 425, 429, 500, 502, 503, 504 and network errors, doubling the delay
Result Variable	Response body; <name>_code is the status

Example Usage

Scenario: Update a setting

HTTP_PUT → Body: {"enabled":true}, retry: 3

COMPARE → http_result_code == 200

Combinations / Used With

COMBINATIONS:

HTTP_PUT + COMPARE: Confirm the update

COMPARE + HTTP_PUT: Update only when the value changed

Tip

Updates data with a fixed PUT request

Warnings / Cautions

WARNING:

HTTPS on public hosts only

A wrong target changes existing data; verify the URL

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

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

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

Basic

HTTP_PUT sends an HTTPS PUT request that updates an existing resource or configuration record. The method is fixed; the URL points at the target record and Body carries the updated value. It is the clear choice when you want to keep the "create with POST, update with PUT" distinction.

Advanced

Put the full HTTPS address of the record to update in URL (e.g. .../config/macro-1), the new state in Body, and the body type in Content-Type. PUT semantics usually mean "replace fully": the body you send becomes the record's new state, and omitted fields may be treated as removed. Header lines are used for authentication. Timeout bounds the network response. The result variable holds the server's reply; you can confirm the update with JSON_PARSE. Because a wrong URL can overwrite existing data, verify the target before sending.

Pro

PUT should be idempotent: sending the same body twice should yield the same result. So when http_result_code comes back -1 you can safely retry PUT — unlike POST, there's no duplicate-record risk. For conditional updates, first read the current value with HTTP_GET, check for a difference with COMPARE, and only send PUT when needed; needless writes mean extra traffic and server load. Keep credentials in a header, not the body. If you want a partial update and the API supports PATCH, HTTP_REQUEST + PATCH is more correct; PUT may remove omitted fields.

Real-World Scenarios — Step-by-Step Recipes

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

Update remote configuration

1HTTP_PUT → URL: https://api.example.com/config/macro-1, Content-Type: application/json
2Body: {"enabled":true}
3COMPARE → if http_result_code == 200, JSON_PARSE the updated confirmation
4Otherwise LOG "PUT failed (code {{http_result_code}})"

Update only when changed

1HTTP_GET → fetch current state (verify the code), JSON_PARSE to current_state
2COMPARE → is current_state != target_state?
3If not equal: HTTP_PUT → Body: {"state":"{{target_state}}"}
4If equal: LOG "No change, PUT skipped"

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 success via http_result_code; when the code is -1, PUT is idempotent so you can safely retry.

+ HTTP_GET

Reads the current value first, giving you a comparison source so you avoid needless writes when nothing changed.

+ COMPARE

Compares current and target state so you only send PUT on an actual difference, cutting traffic and server load.

+ JSON_PARSE

Extracts the server's update confirmation so you verify the PUT actually took effect.

+ LOG

Records the update result and skipped PUTs, making the behavior easy to audit later.

Common Mistakes and Fixes

Sending PUT to the wrong URL overwrites a different existing record. Fix: verify the id variable that builds the address with LOG before sending.

Assuming PUT means partial update; omitted fields may be treated as removed. Fix: send the full body, or use PATCH via HTTP_REQUEST if the API supports it.

Sending an unconditional PUT on every run. Writing even when the value is unchanged creates needless load. Fix: check for a change first with HTTP_GET + COMPARE.

Pro Tips

Because PUT is idempotent, you can safely turn on the retry setting (2-4 attempts) so transient network and server errors recover on their own. POST does this only with an Idempotency-Key header.

For critical records, snapshot the current value with HTTP_GET before PUT (LOG or KV_SET); you'll have the prior state to undo a bad update.

Decide whether you truly want a full replace or a field update; the wrong choice makes PUT silently lose data.

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:put()
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 →