● Apps · Gmail

Automate Gmail
on a real phone.

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

Start for free Book a call

Gmail outreach workflow · demo 1:24

Native demo · muted loop All demos on YouTube ↗

Used by teams backed by a16z and Y Combinator Backed by Merantix · SIXTY · DEGREE · TKM · May Ventures

01 · Use cases

What agents do in Gmail.

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.

Send and follow up

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

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 on real hardware, 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 real number 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 is pay as you go, stateful on request.

● 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 and 2FA codes?

Yes. Gmail can receive email codes, while the phone's eSIM receives SMS codes. The agent can read either in the same run. For an API-native inbound address without a Gmail account, use mobilerun Agent Mail.

Is Gmail automation the same as Agent Mail?

No. Gmail automation drives your authorized Gmail account in the real mobile app, including sending and replying. Agent Mail is a separate mobilerun API inbox for receiving email, retrieving messages, and extracting OTPs.

● 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.

The device layer

Real phones, network and identity behind one REST API.

Your product on top

Ship lead-gen tools, assistants, RPA. Own the UX and the customer.

Rent, do not build

No hardware to buy. 1 to 10,000 devices, billed by usage.

● More apps

Automate Messenger · Automate Discord · Automate Telegram · Automate WhatsApp · all apps