Newmobilerun VA is now in beta, a hosted 24/7 agent for mobile automation
● Apps · Gmail

Automate Gmail
on a real phone.

Your agent signs in to your own Gmail on a real Android or iOS phone with real device identity. It triages, sends, follows up, catches OTP codes, and runs e-sign flows.

Gmail outreach workflow · demo

All demos on YouTube ↗

Used by teams backed by a16z and Y CombinatorBacked by Merantix · SIXTY · DEGREE · TKM · May Ventures
01 · Use cases

What agents do in Gmail.

01

Triage the inbox

Point your agent at your own Gmail to read, label, archive, and flag what needs a human, fast and cheap across your threads.

02

Send and follow up

Draft, send, and chase replies from your authorized account. Agent writes, waits for the reply, and follows up on schedule.

03

Receive codes and sign

Get your own OTP and 2FA codes on the device, then carry them into the flow that needs them. Run e-sign flows end to end.

02 · Why a real phone

Why a real phone.

Gmail was built for phones, not scripts. Your agent runs on a real Android or iOS device, with real device and agent identity: it passes the checks real apps run. That legitimacy is why your mail sends, codes arrive, and sessions hold.

  • Authentic device identity. A real phone, with a number when you add one, reads like an ordinary user's device, so your authorized mail stays deliverable.
  • Any model, any stack. Drive Gmail from the model you already use over API, SDK, or MCP, or hand it to a chat VA.
  • Cheaper by default. Your agent reads the accessibility tree, up to 90% cheaper than vision-only, and the real phone uses device minutes only while it is on.
● Try these

Real tasks, ready to run.

  • Log into my Gmail, search for the receipt sender, mark it important, archive the reply
  • QA the Gmail login screen, enter credentials, assert the inbox loads
  • Open Gmail, compose a test email, attach a photo from the gallery, send it
  • Monitor my Gmail inbox for new order alerts and return each as JSON
03 · FAQ

Gmail automation, answered.

Can I automate Gmail with an AI agent?
Yes. mobilerun runs your own Gmail on a real phone, and your AI agent drives it over API, SDK, or MCP. It can triage, send, follow up, and complete e-sign flows.
Will my mail stay deliverable?
Yes. Your account runs on a real phone that passes the checks real apps run. That's why your authorized, first-party mail sends and sessions stay trusted.
Can it receive OTP codes, and is this the same as Agent Mail?
Yes, it receives codes. Gmail gets email codes, and for SMS codes you add a receive-only number (from $60 a month) or bring your own eSIM. Agent Mail is separate: a mobilerun API inbox that receives email and extracts OTPs without a Gmail account, and Developer includes 10 mailboxes. Gmail automation drives your own account in the real app, including sending and replying. About Agent Mail →
● Infrastructure

Mobile execution, as infrastructure.

What a headless browser is to web agents, mobilerun is to mobile agents. You build the product. We run the phones behind it, and we never compete with what you build on top.

The device layer

Real phones, network and identity behind one REST API.

Your product on top

Ship assistants, AI workers, data feeds, QA and RPA. Own the UX and the customer.

Rent, do not build

No hardware to buy. Start free, run up to 100 phones at once self-serve, and as many as you need on Enterprise.

Automate Gmail on a real phone.

Point your agent at your own Gmail on a real phone.