Resources · Zapier integration

Mobilerun Zapier integrationAutomate Mobilerun with Zapier.

The Mobilerun Zapier integration gives you 1 trigger, 24 actions and 4 searches. The trigger, Task Event, is instant: each time a task on one of your managed devices changes state, a Zap can start right away and pass the news on.

Beta app Zapier still marks this integration as beta.

See the 29 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Mobilerun Zapier integration does for you

Mobilerun runs AI agents on managed mobile devices in the cloud. The integration plugs that into Zapier: a change of state on a task can start an automation, and an event in another tool can start a task, read its results, manage a device or keep the credential vault up to date.

Three results you can build. Status alerts: Task Event starts the automation when a task changes state, and a filter lets only the states you care about reach your team chat. Tasks launched from elsewhere: a new row in your spreadsheet starts Run Task on the device you pick, after Wait for Device if you want the device ready first. A credential vault that follows your records: Create Credential Field, Update Credential Field and Delete Credential keep the logins your agents use in line with the tool where you manage them.

What Zapier does not do here. The only trigger is a change of task state: nothing starts a Zap when a device or a credential changes. No action creates a device, and no search can create what it does not find. The app is also marked as a beta by Zapier, so test each step before you publish. To weigh the same flows on other platforms, open our n8n vs Zapier and Make vs Zapier comparisons.

Vocabulary

Zapier vocabulary in one minute

Eight words come back all over this page. Here they are in plain English, once, before the 29 notes.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time that event happens.
Trigger
The event in an app that starts the Zap. Mobilerun has one: a task on one of your devices changes state.
Action
What the Zap does once it has started: run a task, stop it, fetch its screenshots or update a credential for you.
Task
The unit Zapier bills: one action your Zap completes successfully. Not to be confused with a Mobilerun task, the job an agent runs.
Polling vs instant
Polling: Zapier checks the app on a timer. Instant: the app calls Zapier when the event happens. Task Event is instant.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it there otherwise.
Search step
A step that looks up something that already exists in an app, such as a device or a task, so later steps can use it.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action, a filter or a search turns it into one, and it then needs a paid plan.
Cost

What a Mobilerun Zap really costs

Mobilerun is not a premium app, so it works on the Free plan. The Task Event trigger never costs a task: only actions that succeed are billed, one task each.

  • Task Event trigger0 tasks
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo

A Zap that posts one message per state change uses one task per change; fetch the screenshots first and each run counts two. An action that fails is not counted, and a few actions take more than one task. The Free plan gives 100 tasks a month and unlimited Zaps, each stopping at two steps, so a filter, a search or a second action needs a paid plan. The interval grid below is for polling triggers and does not apply to Task Event, which is instant.

Connect

Connect Mobilerun to Zapier

  1. 01

    Open Apps and add a connection

    In your Zapier account, open the Apps page and click + Add connection. You need an account on Mobilerun, plus read or write access on anything you do not own yourself and want the Zap to touch.

  2. 02

    Pick Mobilerun

    Type the app's name in the search box of the dialog, select Mobilerun, then click Add connection. A new tab opens, and that is where you sign in, on the Mobilerun side.

  3. 03

    Sign in and grant access

    Sign in to your Mobilerun account in that tab, then grant Zapier access to it. The connection is saved once and reused by every step of every Zap that talks to the app.

First Zap

Your first Zap: tell the team when a task reaches the state you watch

GoalEach time a Mobilerun task changes state, let through only the state you care about and post a message in your team chat with what the task returned.

  1. 01

    Create the Zap and set the trigger

    Create a Zap, choose Mobilerun as the app that starts it, pick Task Event as the event, then select the connection you made above.

  2. 02

    Test the trigger

    Run the trigger test. Zapier brings back the three most recent items of the connected account, so you map the next steps on a real task event rather than an empty one.

  3. 03

    Add the filter

    From the plus icon, add a Filter step and fill its three boxes: the field to look at, the rule, the value. A filter makes this a multi-step Zap, which needs a paid plan.

  4. 04

    Add the chat action

    Add the action of your team chat and build the message from what the trigger test returned. Which fields come back depends on the event, so read them at the test.

  5. 05

    Test, then publish

    Test each step once and read what came back. When the message looks right, click Publish to switch the Zap on. For a guided start, see our Zapier training.

Triggers

The Mobilerun trigger

1 event starts a Zap when something happens in Mobilerun, and one of them is instant: the app calls Zapier straight away, whatever your plan.

1

Task Event

Instant trigger

In Zapier“Triggers when a MobileRun task changes state.”

Starts a Zap whenever one of your Mobilerun tasks changes state, and hands that event to the next steps. It is the one door from Mobilerun into your other tools, so every alert, log or follow-up starts here.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your team wants to hear when an agent's task moves on, without keeping the Mobilerun dashboard open all day.
Watch out
every change of state is a run, so put a filter on the state you care about, and read the state values at the test first.
Actions

Mobilerun actions

Mobilerun gives you 24 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Credential Field

Action

In Zapier“Add a field to a credential.”

Adds one more field to a credential that already sits in the vault. The same four boxes are required: Package Name, Credential Name, Credential Type and Credential Value.

When to use it
an existing login needs an extra piece of information next to the one already stored.
Watch out
the credential has to exist; on a brand-new one, use Create Credential Field instead.
2

Connect Device Proxy

Action

In Zapier“Connect a saved MobileRun proxy to a device.”

Links a proxy you saved in Mobilerun to one of your devices. Device and Saved Proxy are both required.

When to use it
a task needs to go out through a given proxy, and you want that set from the same Zap that launches it.
Watch out
the proxy must already be stored in Mobilerun; the step lets you choose one, it does not create it.
3

Create Credential Field

Action

In Zapier“Create a credential and its first field.”

Creates a credential in the Mobilerun vault together with its first field. You fill the Package Name, the Credential Name, the Credential Type and the Credential Value, all four required.

When to use it
a new login to give your agents is recorded in another tool and should reach the vault without copy and paste.
Watch out
dots in the Package Name are normalized automatically for the vault, so the name you see later may differ slightly.
4

Delete Credential

Action

In Zapier“Delete a credential and all of its fields.”

Erases a credential and every field it holds, from the Package Name and the Credential Name.

When to use it
access to an app is revoked for good and nothing of that login should remain for the agents.
Watch out
all of its fields go with it; to remove only one, use Delete Credential Field.
5

Delete Credential Field

Action

In Zapier“Delete a credential field.”

Removes one field from a credential. Package Name, Credential Name and Credential Type are required.

When to use it
a piece of a login is retired in your access tool and should leave the vault while the rest of the credential stays.
Watch out
the Credential Type decides which field goes; read it at the test before you publish.
6

Delete Device

Action

In Zapier“Terminate a MobileRun device and release its resources.”

Terminates a Mobilerun device and releases its resources. The Device is the only required box.

When to use it
a batch of work is over and the device should not stay up once its last task is done.
Watch out
map the device from an earlier step or a search; choosing one by hand would target the same device on every run.
7

Disconnect Device Proxy

Action

In Zapier“Disconnect a device proxy.”

Removes the proxy link from a device, with the Device as the only required box.

When to use it
after a task that needed a proxy, put the device back to its normal route before the next job.
Watch out
check at the test that the device you picked is the one that had the proxy; the step only asks for the device.
8

Get Credential

Action

In Zapier“Get a credential with its fields.”

Retrieves a credential with its fields, from the Package Name and the Credential Name, both required.

When to use it
a later step needs to confirm what the vault holds for an app before updating it.
Watch out
this hands stored secrets to the next steps, so send them only to tools that need them.
9

Get Device

Action

In Zapier“Get a MobileRun device.”

Looks up one Mobilerun device from the Device you pick and passes its details on.

When to use it
a message or a log entry should name the device a task ran on, with what Mobilerun knows about it.
Watch out
the fields returned are shown at the test; do not map anything you did not see there.
10

Get Device Tasks

Action

In Zapier“Get tasks for a device.”

Lists the tasks tied to a device, from the Device alone.

When to use it
before releasing a device, you want to see what it has been running and keep that list in a report.
Watch out
several tasks can come back at once; check at the test how the next step receives them.
11

Get Task

Action

In Zapier“Get a MobileRun task.”

Fetches one Mobilerun task, from the Task you give, so later steps can use its details.

When to use it
the Zap knows which task it is about but needs more about it before writing a summary in another tool.
Watch out
what comes back is shown at the test; map only the fields you saw there.
12

Get Task Screenshot

Action

In Zapier“Get a task screenshot.”

Brings back a single screenshot from a task. Two boxes are required: the Task and an Index.

When to use it
one picture is enough to show what the agent saw, for example to attach it to a note in another tool.
Watch out
check at the test which screenshot a given Index returns before you fix that value in the Zap.
13

Get Task Screenshots

Action

In Zapier“Get task screenshots.”

Collects the screenshots of a task in one step, from the Task alone.

When to use it
a reviewer wants the whole set of images from a run gathered in the place where the team checks the agent's work.
Watch out
read at the test how the images come back before mapping them into a tool that expects one file.
14

Get Task Status

Action

In Zapier“Get the status of a task.”

Returns where a task stands right now, for the Task you name.

When to use it
a step later in the Zap must know whether the job is still going before it acts, for instance before a follow-up message.
Watch out
pair it with a filter on the status you expect, and read the possible values at the test rather than guessing them.
15

Get Task Trajectory

Action

In Zapier“Get a task trajectory.”

Returns the trajectory of a task, for the Task you give, so you can keep a record of it outside Mobilerun.

When to use it
you want an audit trail of each run stored outside Mobilerun, next to the request that started it.
Watch out
read what comes back at the test before you send it to a tool that only accepts short fields.
16

Get Task UI State

Action

In Zapier“Get a task UI state.”

Fetches one UI state of a task. The Task and an Index are both required.

When to use it
you need one UI state of a run, to explain a result to someone who was not watching.
Watch out
check at the test what a given Index returns before relying on it.
17

Get Task UI States

Action

In Zapier“Get task UI states.”

Pulls all the UI states of a task at once, with the Task as the only required box.

When to use it
debugging an agent's run calls for every screen state in order, stored where the team can review them.
Watch out
read at the test how the states come back, then map only what the next tool can take.
18

Initialize Package

Action

In Zapier“Initialize a credentials package.”

Prepares a credentials package for an Android app, from its Package Name, the only required box.

When to use it
you are about to store logins for an app that has no package in the vault yet, and you want that set up from the same Zap.
Watch out
dots in the name are normalized automatically, so map the name you will reuse in later steps from the same source.
19

List Credentials

Action

In Zapier“List all credentials.”

Returns every credential in your Mobilerun vault, with no box to fill.

When to use it
you keep an inventory of the logins your agents can use in a spreadsheet and want to refresh it from a Zap.
Watch out
it covers the whole vault; if only one app matters, List Package Credentials is narrower.
20

List Package Credentials

Action

In Zapier“List credentials for a package.”

Returns the credentials stored for one package, named in the required Package Name.

When to use it
a review of access for a single Android app, without the noise of every other app in the vault.
Watch out
dots in the Package Name are normalized for the vault, so use the same name you used when storing the credentials.
21

Run Task

Action

In Zapier“Start a MobileRun task.”

Starts a Mobilerun task on a device. The Task and the Device are required; Enable Accessibility, Continue on Failure, Enable Reasoning, Enable Stealth and Enable Vision are optional.

When to use it
an event in another tool, such as a new row, should send an agent to work without anyone opening Mobilerun.
Watch out
fill only the optional boxes you need, and read at the test what the step returns before you publish.
22

Stop Task

Action

In Zapier“Stop a MobileRun task.”

Halts a Mobilerun task that is running. You only give the Task, which is required.

When to use it
a cancel signal arrives in another tool and the agent should stop rather than finish a job nobody needs any more.
Watch out
map the right Task from an earlier step or a search; picking it by hand would stop the same task on every run.
23

Update Credential Field

Action

In Zapier“Update a credential field.”

Changes the value of a credential field already in the vault. Package Name, Credential Name, Credential Type and Credential Value are required.

When to use it
a password or token changes in the tool where you manage access, and the agents should get the new one without anyone editing the vault.
Watch out
the Credential Type has to match the field you mean to change; check at the test which one was updated.
24

Wait for Device

Action

In Zapier“Wait until a device is ready.”

Holds the Zap until a device is ready, then lets the next step go on. The Device box is required.

When to use it
place it just before Run Task when the device may still be starting, so the task does not land on a device that is not ready.
Watch out
it is an action like any other, so it counts as a task each time it succeeds.
Searches

Mobilerun searches

4 search steps look for data that already exists in Mobilerun, so a later step can use it.

A search step finds something that already exists in Mobilerun and hands it to the next steps. In the editor, the four searches sit at the bottom of the Action event list, under SEARCH. Adding one makes the Zap multi-step, so it needs a paid plan.

1

Find Apps

Search

In Zapier“Find MobileRun apps.”

Looks up apps known to Mobilerun so a later step can use what it found.

When to use it
a Zap that prepares credentials needs to check the app it targets before it goes further.
Watch out
whether it wants an exact name or something close is decided by Mobilerun, so try both at the test.
2

Find Devices

Search

In Zapier“Find MobileRun devices.”

Finds one of your Mobilerun devices and passes it to the following steps, so you do not pick it by hand.

When to use it
right before Run Task or Wait for Device, when the device to use depends on the data that started the Zap.
Watch out
if several devices match, the setting above decides which one goes on.
3

Find Proxies

Search

In Zapier“Find saved MobileRun proxy configurations.”

Searches the proxy configurations saved in Mobilerun and hands the match to the next step.

When to use it
before Connect Device Proxy, when the proxy to apply changes from one run to the next.
Watch out
it only sees proxies already saved in Mobilerun; a missing one stops the Zap unless you change the setting above.
4

Find Tasks

Search

In Zapier“Find MobileRun tasks.”

Locates a Mobilerun task so the steps that follow, such as Stop Task or Get Task Trajectory, act on the right one.

When to use it
the Zap starts in another tool that knows about the job but not its task in Mobilerun.
Watch out
read at the test what makes two tasks match, so the first result is really the one you want.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and the steps that depended on it are skipped. Switched on, the Zap goes on empty-handed.
  2. Create X if it doesn't exist yet?
    On apps that offer it, this box turns a search into a find-or-create. None of the four Mobilerun searches has that variant, so a search here never creates anything.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When it breaks

When a Mobilerun Zap breaks

Zapier ties no help article to Mobilerun, and no limit specific to the app is documented. What breaks here are the general limits of any Zap.

Each case below comes from the way Zaps work, not from a fault in your account. Read them before you publish, then again when the first real runs come in. If a Zap still misbehaves, our Zapier troubleshooting page is the next stop.

  • Past tasks are not replayed

    A Zap only reacts to what happens after it is switched on. Task state changes that already happened are not picked up; moving that backlog is a separate job.

  • A Zap that sets itself off

    A Zap that writes into the very place its own trigger watches can start itself again and again and burn through your tasks. Check where each action writes before you publish.

  • A sudden huge batch

    After a bulk import or a migration, a trigger that returns a huge batch at once can be held back by Zapier's flood protection.

  • Two steps on the Free plan

    The Free plan builds Zaps of one trigger and one action. A filter, a search or a second action needs a paid plan before the Zap can run.
Need help

Need help automating Mobilerun with Zapier?

A person reads every message.

FAQ

Mobilerun and Zapier: questions

01Is the Mobilerun Zapier integration free?
Yes. Mobilerun is not a premium app, so it runs on the Free plan of Zapier. That plan gives you 100 tasks a month and an unlimited number of Zaps, each limited to two steps: one trigger and one action. A message to your team chat on each task event fits that shape. Add a filter on the state, a search for a device or a second action, and the Zap becomes multi-step and needs a paid plan. Each app page on Zapier says whether the app is premium.
02How many tasks does a Mobilerun Zap use?
One Zapier task per successful action, on every run. The Task Event trigger costs nothing. A Zap that waits for a device, then runs a Mobilerun task, then posts a message counts three Zapier tasks per run, since Wait for Device is an action too. An action that fails is not counted against your plan. A few apps and actions take more than one task when they complete, so read the count of your first real runs before you chain many Get steps after each event.
03Does the Mobilerun trigger run in real time?
Yes. Task Event is an instant trigger: Mobilerun tells Zapier the moment a task changes state, so the Zap starts straight away whatever your plan. The interval grid of the Zapier plans only concerns polling triggers, and this app has none. In the editor, a Zap built on an instant trigger shows a lightning bolt. Each change of state is its own run, so a filter on the state you care about, placed right after it, keeps the Zap quiet the rest of the time.
04What does it take to connect a Mobilerun account?
An account on Mobilerun, plus read or write access on anything you do not own yourself and want the Zap to touch. The connection starts from the Apps page of Zapier with + Add connection; you then pick the app, sign in to Mobilerun in the tab that opens and grant Zapier access. Once saved, that connection is reused by every step of every Zap that talks to Mobilerun, so you set it up a single time.
05Why does the Package Name look different after a credential action?
Because Mobilerun normalizes the dots in the Package Name automatically for its credential vault. Every credential action asks for that name as a required box, from Initialize Package to Delete Credential, and the vault stores it in its own form. So when a later step looks up or updates the same credential, map the name from the same source you used to create it rather than retyping it, and check at the test that Get Credential finds what you expect.
06What if the operation you need is not on the list?
Start with the Mobilerun page on Zapier: it shows the current list of triggers, actions and searches. If the exact operation is missing, try combining what exists in a multi-step Zap, for instance Find Devices, then Wait for Device, then Run Task. The many Get actions also let you pull a task's status, screenshots or trajectory into a later step. Keep in mind that the only trigger is a change of task state, so nothing starts a Zap on a device or credential event.
07Zapier, Make or n8n for Mobilerun?
It comes down to criteria, not to a winner. On Zapier, the one Mobilerun trigger is instant, so how fast a Zap starts does not depend on your plan. Weigh how many steps your flows need, since Wait for Device plus Run Task plus a message is already a paid multi-step Zap; how many runs a month your agents produce, since each successful action is a task; and where your other tools are already connected. Compare those points on each platform before choosing.
Same platform

Other docs you might need on this stack.

Browse all integrations