Tapvexa documentation
Is element exists
Is element exists checks whether an element is present on the screen.
Select an element, right-click it, then choose Is element exists. If the result shows true, the element is present on the screen.
Facebook = "true" — the element is on screen.Pair it with an If block to branch: if the element exists, continue; otherwise wait or skip. There is also an Is element exists (image) variant that matches by a captured image, for elements without a stable id.
Tap element
Tap element lets you click (tap) on an element.
Right-click an element, then choose Tap element.
There is also a Tap element (image) variant that taps wherever a captured image is found on the screen.
Input text
Input text lets you type data into an empty field you want to fill in.
Right-click the field, then choose Input text….
When you click Input text, a dialog opens — type the text you want to enter into the field there.
There is also an Input text (image) variant that locates the field by a captured image. The text can be fixed, or pulled from the Data Vault for data-driven runs.
Open / Close app
Open app lets you open an app. In Inspect mode, right-click the app you want to open and choose Open app.
After you click Open app, a dialog opens — just enter the app's package name there.
Close app works the same way — right-click and choose Close app to force-stop the app.
Deeplink
A deeplink is a link that takes you straight to a specific part of an app. For example:
fb://settingfb://homepagetiktok://profile
Right-click, choose Open URL / deeplink, then enter the link.
Swipe coordinates
Swipe from one point to another using screen coordinates — scroll feeds, dismiss dialogs, or move between pages. Set the start and end X/Y and the swipe duration.
Step-by-step guide and screenshots coming soon.
What is DI mode and DOI mode?
When you run a flow, Tapvexa asks you to choose a device mode. Pick the one that matches your setup.
DI mode
The mode you normally use for phones. All your devices are already open and connected, with ADB already set up — actions run directly on the connected devices.
DI mode has two ways to run:
- Start all — runs every device at the same time with one script.
- Start sequentially — runs your devices in batches. Select all your devices; the number on Start sequentially is how many run at once in each batch.
Example: select 20 devices and set the number to 2 → the tool runs 2 devices at a time until all 20 are done. Repeat is how many rounds to run — set it to 2 and the tool runs 2 full rounds over the 20 devices.
DOI mode
The mode you normally use for emulators (usually LDPlayer). Here the flow opens the LD instances itself using the built-in LD module, then controls each LD or phone one at a time, not all at once.
Because of that, every tap / swipe must name which device (adb serial) it acts on. Point to the device in the Device field — fill it with [[LD_SERIAL]] from Check adb LD.
How to import data from PC to devices (emulator/phone)
To push data from your PC to a device, use the Phone action module.
Inside it you'll find the Send file to phone action.
As you can see below, there is a PC file or folder field — this is where you add a .txt file, an image folder, or any data you want to send.
The Phone folder is set to /sdcard/Pictures/ by default, so any images you push land straight in the phone's Pictures (gallery) folder.
Next, enter the path to the file you want to send. For example, to send an image named 1.png, put its full path in PC file or folder, then press OK.
As you can see, the file is now on the device — in this case the image lands in the phone's Pictures gallery.
How to connect devices
To connect a phone and start building a workflow, open the Record mode.
In the middle of the screen you'll see a — Select device — dropdown. Click it, choose the device you want to build the workflow on, then press Connect to connect to it.
The device's screen will then appear, and you can start recording your workflow. If your device isn't listed, press the refresh button next to the dropdown to rescan.
How to control and inspect a device
After entering Record mode and connecting a device, you'll see two features at the top: Control and Inspect.
- Control — drive the phone and interact with it however you like.
- Inspect — click any element and its app info appears in the right-hand column.
How to write a script that runs smoothly
To write reliable scripts, use a For loop together with Is element exists, and add a short 1–2 second wait at the very end.
Why: the app runs and dumps UI elements very fast, and the phone can occasionally lag — so a dumped element may be missed. Re-checking repeatedly (a loop plus Is element exists) makes the script run far more reliably.
You can also use Break loop to exit the loop once the task is done.
How to connect a proxy
To add a proxy, you need the proxy VAT module. It's an app I've used before and it works very reliably.
When you click this module, its dialog opens. The proxy format is IP:PORT:USERNAME:PASSWORD.
Remember to pick the correct proxy type — only then will the proxy work correctly:
httphttpssocks4socks5
