Automate unread message scanning, custom reading dwell times, campaign link actions, and multi-profile inbox warm-up directly inside your Chrome browser.
Find unread messages inside the signed-in mailbox. ERA walks the inbox and builds an unread queue from what is actually rendered.
Apply campaign, sender, domain, or date rules. The unread queue is reduced to the messages your run actually targets.
Open messages and perform configured actions — dwell for the reading time, open links, or send a reply, with delays between steps.
Record activity and completion status. Every step lands in a local activity history with timestamps and per-message outcomes.
The same run configuration works across five webmail providers. Underneath, ERA adapts to how each inbox actually renders messages.
Unread messages are collected page by page. The extension walks the inbox pagination, then returns to page one before starting the run.
Support behavior varies by provider. Not every automation feature behaves identically across mailboxes.
Connect your ESP to pull active campaigns, apply sender filters, and narrow your unread queue automatically. No manual rule-building.
TEST THE CONNECTION TO VERIFY CREDENTIALS
Configure how browser traffic leaves the machine — per Chrome profile. Switch between direct, shared, and per-account routing without touching run settings.
Each account is assigned its own proxy. Routes stay isolated per Chrome profile.
Proxy configuration is profile-scoped and applies to browser traffic during runs. ERA makes no anonymity or evasion guarantees.
Timing, limits, filters, and behaviors — tuned per run. Change a setting and watch the simulated run respond.
Configure settings, then simulate a run.
An optional loop between two mailboxes you own — messages sent inside a defined window, opened, and replied to with a configurable probability. Dry Run simulates the loop end to end.
Dry Run walks the full loop and renders simulated messages. Nothing is sent.
WarmTalk exchanges messages between mailboxes you own. It does not improve or guarantee deliverability outcomes.
Each scan, open, and action is recorded locally with a timestamp. Runs are auditable — nothing happens silently.
Separate accounts can run at the same time in separate Chrome profiles — storage and proxy configuration are scoped to the profile, so settings never bleed across accounts. Each license covers 2 profiles.
Each license activates on up to 2 devices, and every Chrome profile counts as one device — the 4 profiles shown here would use 2 licenses. To move a license, deactivate the old profile from inside the extension. Beyond that, fleet size is bounded by your machine.
Runs inside Chrome.
The extension executes in the browser profile you launch it from.
Works through signed-in webmail sessions.
No mailbox passwords, tokens, or credentials are requested.
Automation stays local; the license is verified online.
Activation and periodic re-checks send your license email, license key, a random per-profile device ID and the extension version to the Email Automate license server. Configuration and activity history stay in your Chrome profile.
Payments are processed by Razorpay — card details are handled by Razorpay and never touch our servers.
This is an architectural description — not a guarantee of privacy or security outcomes.
Email Automate ships as a ZIP that you load into Chrome as an unpacked extension — it isn't on the Chrome Web Store. Download it right after payment or from your license email, then activate it with your purchase email and license key.
Right after payment, or from the link in your license email.
Open chrome://extensions and switch Developer Mode on.
Select the extracted email-automate folder. Keep it somewhere permanent — updates go into the same folder.
Open the extension and enter your purchase email and license key.
Illustration — file names and version details in your browser will differ.
Enter the email you bought Email Automate with and your license key to get a new download link.
Eight steps to your first run, then two optional extras. Email Automate installs as an unpacked Chrome extension, so the folder you extract it to matters — everything else is a few clicks.
Straight after payment, or from the link in your license email. Those links are short-lived — use Download again above whenever you need a fresh one.
Unzip it into a folder you will not move, rename or clear out — your Documents folder rather than Downloads. Chrome reads the extension from this folder every time it starts.
Don't run it from inside the ZIP, and don't leave it in a temp folder. If the folder goes, the extension goes with it.
Paste chrome://extensions into the address bar. The Developer mode switch sits in the top-right corner of that page.
Pick the extracted email-automate folder itself — the one with manifest.json directly inside it, not the folder holding it.
Click the puzzle-piece icon in Chrome's toolbar, then the pin beside Email Automate. It opens in the side panel, next to whichever mailbox you are on.
Open the extension and fill in the email you bought with, plus the license key from your license email. Click Activate.
One license activates up to 2 Chrome profiles — each Chrome profile counts as one device.
Tick the mailboxes this run should cover — Gmail, Yahoo, AOL, Outlook or Proton. Sign in to each of them in this Chrome profile first; the extension works through your existing sessions and never asks for a mailbox password.
Open the mailbox tab and hit Start. Session stats — opened, runtime, unread — tick over live, and every step is written to the local activity history.
Open ESP Connector, pick your provider and paste its API key — Brevo's lives under SMTP & API → API Keys. Campaign Lookback sets how far back sent campaigns are read. Keys are stored in your Chrome profile and never shown again.
Leave “Only process ESP emails” off and every unread message is processed as normal. Turn it on to narrow a run to mail your own ESPs sent.
Proxy Manager applies a proxy to the Chrome profile before a scan begins. Add a host, port and credentials, then assign it to an account — or leave the whole thing off and traffic goes out directly.
Proxy configuration is profile-scoped and applies to browser traffic during runs. It makes no anonymity guarantee.
That's expected. Email Automate isn't distributed through the Chrome Web Store, so Chrome flags every unpacked extension this way. Dismiss the bar and carry on — just don't click Remove.
Its folder was moved, renamed or deleted. Put the folder back where it was — or extract the ZIP again somewhere permanent — then load it unpacked once more.
Download the current ZIP, extract it over the same folder, then click Reload on the extension's card in chrome://extensions. Loading a fresh copy from a different folder registers as another device instead of an update.
A license covers up to 2 Chrome profiles. Open the extension on a profile you no longer use and choose Deactivate this device — that frees its place for a new one.
Check three things: the provider is ticked in the panel, you're signed in to that mailbox in this Chrome profile, and the mailbox tab is open. If the ESP Connector is on, only mail sent by your connected ESPs will match.
No subscription and no renewals. Download the extension right after payment — your license key and a download link are also emailed to you.
Secure checkout by Razorpay — card details never touch our servers.
How automation works in each webmail provider, how to warm up and authenticate a domain, and the opt-in rules that keep your mail welcome. Plus four free tools that run in your browser.
Gmail inbox automation means letting a tool work through your own unread messages in a Gmail tab you are already signed in to: finding mail from chosen senders, opening it, and optionally replying or opening links. The extension does this inside Chrome, page by page, without ever asking for your Gmail password. It is meant for your own mailboxes, for example to check how your own campaigns land and render.
6 min readEmail warm-up is the practice of increasing sending volume from a new mailbox or domain gradually, so mailbox providers can build a picture of it before it sends larger volumes. Good warm-up relies on real, low-volume, wanted mail and steady growth, not on tricks. The extension's optional WarmTalk feature helps by running a paced conversation loop between two mailboxes you own.
7 min readSPF, DKIM and DMARC are DNS-based standards that let receiving mail servers check that email claiming to come from your domain is authorised. SPF lists which servers may send for you, DKIM adds a cryptographic signature, and DMARC tells receivers what to do when checks fail and where to send reports. Gmail and Yahoo now require authentication from senders, so this is a baseline, not an optional extra.
8 min readSince February 2024, Gmail and Yahoo have required senders to authenticate their mail, and bulk senders must also publish DMARC, support one-click unsubscribe and keep spam complaint rates low. Google describes bulk senders as those sending close to 5,000 or more messages a day to Gmail addresses. Google also advises keeping the reported spam rate below 0.1 percent and never reaching 0.3 percent.
7 min readMultiple Chrome profiles let you keep each mailbox you own in its own isolated browser environment, with separate cookies, sessions, extensions and settings. That makes it the cleanest way to run inbox automation across several accounts. The extension supports multiple Chrome profiles, each with its own configuration and optional proxy.
5 min readBrowser inbox automation and n8n workflows solve different problems. n8n connects services through APIs and triggers, which suits back-office tasks like routing form submissions, syncing contacts or sending transactional notices. Browser automation works inside the webmail interface you are signed in to, which suits tasks that depend on what the inbox actually shows, such as checking placement and rendering of your own campaigns.
6 min readPlan a gradual daily sending ramp for a new mailbox or domain.
Check a subject line and body for spammy phrasing, shouting and link overload.
Build SPF and DMARC DNS TXT records for your sending domain.
See how a subject and preheader truncate on mobile and desktop inboxes.
Built for mailboxes you own and recipients who opted in. Read the email compliance checklist before any campaign.
The operational details — licensing, providers, sessions, proxies, and what happens when webmail interfaces change.
Email Automate is a Chrome extension that operates on the webmail tabs you are already signed in to. It scans the rendered inbox for unread messages, applies your campaign and sender filters, opens matching messages, waits for your configured reading time, performs optional actions such as link opens or replies, and records each step in a local activity log.
Gmail, Yahoo, AOL, Outlook, and Proton. Provider behavior differs: Gmail is processed through pagination, Yahoo and AOL through continuous scrolling, Outlook through a virtualized scrolling list, and Proton on the first rendered screen after local decryption.
No. The extension runs inside your existing signed-in browser sessions. It never asks for, stores, or transmits your mailbox credentials.
The Proxy Manager sets the proxy configuration of the Chrome profile it runs in. You can route traffic directly, share one proxy across accounts, or assign a dedicated proxy per account. Proxy configuration is profile-scoped and applies to browser traffic during runs.
WarmTalk is an optional two-mailbox messaging loop between mailboxes you own. Mailbox A composes a message to Mailbox B within a defined sending window, Mailbox B opens and can reply with a configurable probability, all within daily and weekly caps. A dry-run mode simulates the loop without sending anything.
Yes. Extension storage and proxy configuration are scoped to the Chrome profile, so separate profiles can run separate accounts at the same time without sharing settings. One license activates up to 2 Chrome profiles — each profile counts as one device.
Webmail interfaces change regularly. If a run cannot locate expected elements, it stops safely, records the failure in the activity log, and can retry based on your retry settings. Fixes for interface changes are released as new versions of the extension, which you can download with your license at any time.
Any automated activity in a mailbox may be subject to your provider's terms of service and abuse detection. The extension ships conservative defaults — reading times, delays, limits — but you are responsible for configuring runs that comply with your provider's policies. No outcome can be guaranteed.
A one-time payment for a lifetime license — there is no subscription and nothing renews. The license activates the extension on up to 2 devices, where each Chrome profile counts as one device. Payments are processed by Razorpay: card details go to Razorpay and never reach our servers.
Right after payment you can download the extension as a ZIP, and your license email contains your license key and a download link. Extract the ZIP, open chrome://extensions, turn on Developer mode, click Load unpacked and select the extracted email-automate folder. Then open the extension and enter your purchase email and license key. Keep that folder in a permanent place: to update, copy a new version over it and click reload in chrome://extensions — a copy loaded from a different folder counts as another device. The extension is not listed on the Chrome Web Store.
Yes. Open the extension on the device you no longer use and choose Deactivate this device. That frees its place, and you can activate another Chrome profile with the same email and license key.
Use Download again on this page with your purchase email and license key to get a fresh link to the current version. Download links expire, so request a new one whenever you need it.
Pay once with Razorpay and download right after payment. Your license key is emailed to you.
