No-Code Workspace — Block Reference

SystemBlock usage recipe

System (SYSTEM)

Runs Android system commands

Documented for app version 1.0.50Updated: October 2, 2026

What Does It Do?

Runs 46 system commands: navigation (Home, Back, Recents, notification and quick settings panels), screen, sound, ringer, Do Not Disturb, flashlight, vibration, opening apps and URLs, Send Intent, typing text and the clipboard, device-state readings (battery, charging, package name, screen) and pausing/stopping the macro.

Pro note: the command matrix has different input rules

The required inputs change by command in SYSTEM. Home and open_app do not need the same fields, so the docs must make that clear.

When to Use?

Use it to:

Open an app and wait until it is in front

Press Back or Home

Send safe allowlisted intents

Decide based on battery or screen state

How to Use?

"Add Block" → "System (SYSTEM)"

Pick the command and enter a Value if needed: package name, https address, intent action, text or result variable

Open App's Advanced section: Don't reopen if already in foreground, Wait until app is in foreground with a Wait timeout (100-60000 ms), Wait after opening (0-60000 ms)

Parameters

System Command

46 commands: navigation, screen, sound, apps, text, readings, macro control

Value / Optional Target

Command-specific value; optional target package for Send Intent

Parameter	Description
System Command	46 commands: navigation, screen, sound, apps, text, readings, macro control
Value / Optional Target	Command-specific value; optional target package for Send Intent

Example Usage

Scenario 1: Open an app

SYSTEM: Open App → "com.example.targetapp", Wait until app is in foreground

Verify the ready screen with IMAGE

Scenario 2: Open a settings screen

SYSTEM: Send Intent → "android.settings.WIFI_SETTINGS"

Verify the screen with TEXT

Combinations / Used With

COMBINATIONS:

SYSTEM + IMAGE: Verify the command worked

SYSTEM (battery level) + COMPARE: Stop on low battery

TEXT + SYSTEM: Press Back when a text appears

Tip

Runs Android system commands

Warnings / Cautions

WARNING:

Send Macro Handler to Background cannot close another app

If the foreground wait times out, the block raises an error

Send Intent and Open URL reject targets outside the allowlist

There is no command that locks or turns off the screen

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

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

Basic

The SYSTEM block runs Android's device-level commands and toggles: home, back, recents, the notifications/quick-settings panel, torch, volume (up/down/mute), ringer mode, Do Not Disturb, brightness, rotation lock, open app, send Macro Handler to the background, open URL, screenshot, and more. You pick a command and, when needed, provide one or two parameters. It is the no-code equivalent of pressing physical buttons and performing system operations.

Advanced

Pick from the command list; some commands need no parameter (home, back, recents, notifications, quick_settings, torch_on/off, volume_up/down, volume_mute/unmute, ringer_normal/vibrate/silent, dnd_on/off, auto_brightness_on/off, rotation_lock/auto, screenshot, split_screen, close_app, pause/resume/stop). close_app does not force-stop a third-party app; it only sends Macro Handler safely to the background. Some take arg1: open_app (target package name, e.g. com.example.targetapp), open_url (https address), brightness and screen_dim_on (0-100 level), vibrate (ms), toast/alert (message), copy_clipboard/input_text (text). Read commands write the result into a variable: battery_level, is_charging, package_name, is_screen_on, screen_width, screen_height, get_clipboard, is_paused. send_intent is special: arg1 is the intent action and arg2 the optional target package — and the runtime passes it through a safe allowlist. open_app's Advanced (Open App) section has four settings: Don't reopen if already in foreground, Wait until app is in foreground with a Wait timeout (100-60000 ms; the block raises an error when it expires), and Wait after opening (0-60000 ms). The wait fields can be bound to variables with the lightbulb.

Pro

send_intent and open_url pass through a safe allowlist at runtime: action/package pairs and unsafe schemes outside the allowlist are rejected. This is a deliberate defense. The open_app result and optional foreground wait are checked; if the app cannot open, the flow errors before a later touch can run on the wrong screen. Verifying completed loading with IMAGE/TEXT is still a safe practice. Android exposes no supported API for force-stopping a third-party app, so close_app only sends Macro Handler to the background. Combine read commands (battery_level, is_screen_on, screen_width) with IF_ELSE/COMPARE to branch on state. If you change system settings like brightness/DND/rotation, consider restoring the prior state at the end; some toggles may require special OEM permissions.

Real-World Scenarios — Step-by-Step Recipes

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

Open app, wait for load, verify

1SYSTEM → command: open_app, arg1: com.example.targetapp; enable Wait until app is in foreground, Wait timeout 10000 ms
2Use IMAGE to find the app's ready screen
3If not found, record diagnostics with LOG and return to a safe state in a TRY_CATCH error path
4Do not use close_app to force-stop a third-party app

Stop automation safely on low battery

1SYSTEM → command: battery_level, result variable: bat
2COMPARE → is bat < 15?
3If true: SYSTEM → dnd_off (restore prior state if any), LOG "Low battery, stopping", SYSTEM → stop
4If false: continue the macro

Which Blocks to Pair With — Pro Combinations

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

+ WAIT

Gives the device time to finish after commands like open_app, so the next step doesn't run on the wrong screen.

+ IMAGE

Visually confirms the system action actually happened — did the app open, did the screen change.

+ COMPARE

Branches on the result of read commands like battery_level, is_charging, screen_width, building state-aware automation.

+ IF_ELSE

Runs two distinct paths based on flags like is_screen_on or is_charging; e.g. screen_on first if the screen is off.

+ TRY_CATCH

open_url/send_intent may be rejected by the allowlist or blocked by a missing permission; you handle the error path cleanly.

Common Mistakes and Fixes

Running the next step immediately after open_app. The app hasn't loaded yet, so taps miss. Fix: verify the launch with WAIT + IMAGE/TEXT.

Entering the wrong package name (e.g. typing the app label). A wrong package won't open the app. Fix: get the real package name from Settings → Apps → App Info.

Mistaking send_intent silently doing nothing for a bug when the action is off-allowlist. That's a deliberate security shield. Fix: use only safe, allowlisted action/package pairs.

Changing settings like DND/brightness/rotation without restoring them. It leaves the user's device in an unexpected state. Fix: revert with the opposite command (dnd_off, auto_brightness_on) at the end.

Pro Tips

Bind wait fields such as Wait Before and Wait After to a variable with their lightbulbs. Runtime limits still apply.

Coming soonv1.0.51The same lightbulb menu has a Random option: enter two bounds (for example 300 – 800) and the block picks a new wait from that range every time it runs. Runtime limits still apply.

Read commands (battery_level, is_charging, is_screen_on, screen_width/height) are powerful triggers; pair them with COMPARE to condition automation on device state.

If you flip a toggle in a session (dnd_on, rotation_lock, brightness), restore it with the opposite command at the end — a clean 'set and revert' pattern feels professional.

Read screen_width/screen_height and compute coordinates proportionally so the macro taps the right spot across different resolutions.

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 _systemResult1 = System.notifications()
if _systemResult1 ~= true then error("SYSTEM notifications failed") 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 →