Automating phones

WarpX Phone uses the same workflow editor as WarpX Browser. The general, data, control-flow and online blocks are the same; in place of the browser's, it has three groups of phone blocks.

The phone blocks

  • UI Interaction — touch, swipe and type, press keys, find and read elements, pictures and text, take screenshots.
  • Device Management — the phone's identity and proxy, what it says it is, radios, clipboard, files and ADB commands.
  • App Management — start, stop, install, clear, back up and restore apps.

The whole list, with WarpX Phone's blocks only, is the block reference for WarpX Phone. A block both apps share says on its page what is different on a phone.

Your first workflow

  1. Open Workflows, create one, and pick a phone in the editor's toolbar — any phone that is online.
  2. Add Start app and type the app's package; the field suggests the phone's apps by name as you type.
  3. Add Element action, choose Inspect and click the button to tap. See Finding elements on a phone.
  4. Add Type text for a field, or Screenshot to keep what the screen showed.
  5. Press Run. The run happens on the phone in the toolbar, and its log is on the Logs page.
A run in progress: Type text typing into the search field the step before found.

The phone a block acts on

Phone blocks do not name a phone. Each acts on the phone its run is on: in the editor, the one picked in the toolbar; for a run from the Control Center or the API, the phone that run was started for. So one workflow runs unchanged on every phone of the shelf.

Run it on many phones

The Schedule page runs WarpX Browser profiles; it does not start runs on phones yet.

  • From the Control Center: tick the phones, then Run automation.
  • From your own code, on a paid plan: WarpX Phone has its own developer key and API on http://127.0.0.1:47310, and an MCP server, warpx-phone, for Claude, Cursor or another assistant. Its Developer API page in the app has the key and the address; the routes are those of the Developer API, with phones in place of profiles.

Blocks that ask first

A few blocks can lose what is on a phone — an ADB command, clearing an app's data, a Backup that copies apps off the phone, a Phone identity that changes whose proxy carries its traffic. When a workflow somebody else made runs one, WarpX Phone lists them and asks before the run starts; a block you approved once asks again only if it changes.