Block reference / UI Interaction

Screenshot

Save the phone's screen as a PNG file on this computer.

Only inWarpX Phone

Screenshot keeps a picture of what the phone shows right now: proof of an order, the state of a screen when something went wrong, a result to check later. The file is saved on this computer, and its full path can go to a variable or the table, so a later block can send or upload it.

Settings

Folder

The folder on this computer to save into; Browse picks it with the system's dialog. Empty saves into phone-screenshots under Downloads.

ExampleC:\Users\anna\Pictures\orders

File name

The file's name. .png is added when the name has none, and a name may hold a folder of its own, such as shots/{{loopData.orders.id}}. Empty names it by the date and time, such as 2026-10-12_22-17-31-884.

Exampleorder-{{loopData.orders.id}}

Assign to variable

Also stores the saved file's full path in a workflow variable.

ExampleChecked

Variable namewhen Assign to variable is on

The variable to write. Later blocks read it as {{variables.shotPath}}; start the name with $push: to add to a list instead of replacing it.

ExampleshotPath

Insert to table

Writes the saved file's full path into the workflow's table, one row per run of the block. Offered once the workflow's table has columns.

ExampleChecked

Select columnwhen Insert to table is on

The table column to write to. Later blocks read the latest row as {{table.$last.screenshot}}.

Examplescreenshot

Delay (ms)

A pause after the block finishes, before the next block starts. Write one number such as 1000, or a range such as 1000,3000 for a random pause in that range on each run.

Example0

Every block also has the shared block settings — a description, Disable block and what to do on an error. Fields that take text accept data from earlier blocks.

What it hands on

Hands on the saved file's full path as {{prevBlockData}}, and writes it to the variable and the table column when asked. Leaves by its single output.

Example: Keep a picture of each order's confirmation

1. Pick the phone in the editor's toolbar. Inside a Loop data with Loop ID orders, build the steps that place one order.
2. After the order is placed, add a Wait for element on the confirmation text, so the screen has finished loading.
3. Add a Screenshot block. Click Browse next to Folder and choose a folder, and set File name to order-{{loopData.orders.id}}.
4. Tick Insert to table and pick a screenshot column.
5. Press Run, then open Table: each row holds the full path of that order's picture.

Good to know

• The picture is the whole screen at the phone's full resolution, taken through adb, so no agent is needed.
• A file with the same name is overwritten. Put something that changes in File name, such as a loop value, to keep one per run.
• Folder and File name both take references, so {{variables.folder}} works for a folder chosen earlier in the run.
• When the block fails, it leaves by its fallback output if one is connected: a phone block comes with On error set to Execute fallback. With nothing connected there, the workflow's On workflow error setting decides.

See also

• Read text (OCR) — Read the text in an area of the phone's screen, by OCR.
• Wait for element — Wait until an element shows on the phone's screen, or until it has gone.
• Image search — Find a picture on the phone's screen, then tap it, wait for it or say whether it is there.