Block reference / App Management

Is app installed

Answer whether an app is on the phone: true or false.

Only inWarpX Phone

Is app installed checks whether the run's phone has an app, by its package, and hands on true or false. Put a Conditions block after it to send phones with and without the app down different paths. A missing app is an answer here, not an error.

Is app installed finds com.facebook.katana on the phone and hands on true; it checks by package, whether or not the icon is on the home screen.
The Is app installed block's settings, filled in as in the example below.

Settings

Package

The app, by its package name, such as com.shopee.vn. As you type, the field suggests the apps on the phone picked in the editor's toolbar, the apps phone farms run most (typing zalo finds com.zing.zalo) and the packages the workflow already names; tick System apps in the list to include built-in ones. What you type is kept as typed, so a reference such as {{loopData.package}} works too.

Examplecom.facebook.katana
Save the answer (true / false) to a variable

Also stores the answer, true or false, in a workflow variable. On for a new block.

ExampleChecked
Variable namewhen Save the answer (true / false) to a variable is on

The variable to write — installed for a new block. Later blocks read it as {{variables.installed}}, for example in a Conditions path. Left empty, nothing is written.

Exampleinstalled
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 to pick 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 true or false as {{prevBlockData}}, and writes it to the variable when asked. The block has one output, whatever the answer: branch on the variable with a Conditions block.

Example: Note the phones that have no Facebook

  1. Start
  2. Is app installed
  3. Conditions
  4. Start app
Where Is app installed sits in the example workflow.
  1. Add an Is app installed block and pick Facebook (com.facebook.katana) in Package.
  2. Leave Save the answer (true / false) to a variable on, with the variable installed.
  3. Add a Conditions block after it, with one path where {{variables.installed}} equals true.
  4. Connect that path to a Start app block for com.facebook.katana and the rest of the flow.
  5. Connect the Conditions block's fallback path to an Insert data block that writes missing into a facebook column, so the run's table lists the phones to set up by hand.

Good to know

  • The variable keeps the answer for later blocks; {{prevBlockData}} holds it only until the next block runs.
  • Install app from the library or Google Play, and Start app set to install, already do nothing for an app the phone has; you do not need this check in front of them.
  • A value that is not a package name, after references are filled in, fails the block.
  • There is no Device field: the block acts on the run's phone — the one picked in the editor's toolbar, or each phone ticked for Run automation in the Control Center or named in an API run.

See also

  • Is app open — Answer whether an app is on the screen, or running at all: true or false.
  • Install app — Install an app from an .apk on this computer, from the APK library, or from Google Play.
  • Start app — Open an app by its package, installing it first if the phone has not got it.
  • Conditions — Send the run down one of several paths, depending on values, page elements or code.