How inbox automation works in each webmail provider, how to warm up and authenticate a sending domain, and the consent rules that keep your mail welcome. Written for people automating their own mailboxes and sending to people who asked to hear from them.
Webmail providers
How inbox automation works inside Gmail, Outlook, Yahoo, AOL and Proton when you are already signed in to your own mailbox in Chrome.
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.
Outlook inbox automation lets a browser tool process unread mail in an Outlook web tab you are already signed in to. Outlook renders its message list as a virtualized list, so the extension scrolls and reads rows as they are drawn rather than loading the whole inbox at once. It works only with your existing session and never asks for your Microsoft password.
Yahoo Mail automation means having a browser tool work through unread messages in a Yahoo Mail tab you are already signed in to. Yahoo loads its inbox with infinite scroll, so the extension scrolls to reveal more messages and processes the ones that match your filters. It uses your existing session and never asks for your Yahoo password.
AOL Mail automation lets the extension work through unread messages in an AOL Mail tab you are already signed in to. AOL's web inbox loads messages with infinite scroll, similar to Yahoo Mail, so the extension scrolls and processes matching rows as they appear. It never asks for your AOL password.
Proton Mail automation is more limited than other providers because Proton decrypts messages locally in your browser. The extension works on the first rendered screen of your inbox after that decryption, processing unread messages it can see there. It uses your existing signed-in session and never asks for your Proton password or keys.
5 min read
Deliverability
Warm-up, authentication, bulk sender rules and the metrics that decide whether your own campaigns reach the inbox.
Email 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.
SPF, 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.
Since 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.
Emails usually go to spam because the receiving provider does not trust the sender enough: authentication is missing or misaligned, the list includes people who did not ask for the mail, recipients complain or ignore it, or the domain is new and sending too much too fast. The durable fix is to address those causes directly, not to disguise the mail.
The deliverability metrics that matter most are bounce rate, spam complaint rate, inbox placement, authentication pass rate and genuine engagement such as replies and clicks. Delivery rate alone only tells you that a server accepted the message, not whether it reached the inbox. Tracking these together shows how mailbox providers see your sending.
6 min read
Setup
Installing the extension, organising Chrome profiles, configuring proxies and connecting your email service provider.
To install an unpacked Chrome extension, extract the ZIP to a folder, open chrome://extensions, turn on Developer mode and click Load unpacked, then select the extracted folder. The extension is distributed this way, rather than through the Chrome Web Store, after you purchase a license. Keep the folder in place afterwards, because Chrome loads the extension from it.
Multiple 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.
A Chrome profile proxy routes that profile's browsing through a chosen proxy server instead of your normal connection. The extension's Proxy Manager offers three modes: direct (no proxy), shared (one proxy for all profiles) and per-account (a separate proxy per profile). Most people should start with direct and only add a proxy for a clear, legitimate reason.
The ESP Connector links your email service provider account to the extension so it can recognise which messages in your own seed inboxes belong to a specific campaign. Instead of filtering by sender alone, you pick a campaign and the extension finds its messages. Brevo is live, MailerLite and Klaviyo are built, SendGrid and Mailchimp are untested, and Mailgun and Amazon SES are coming soon.
5 min read
Compliance
Consent, unsubscribe and legal basics for email marketing under CAN-SPAM, GDPR and PECR, written for senders who want to stay clean.
Compliant email marketing comes down to sending only to people who agreed to hear from you, identifying yourself honestly, and making it easy to stop. In the US, CAN-SPAM sets rules on content and unsubscribes; in the UK and EU, GDPR and PECR generally require prior consent for marketing email to individuals. This checklist summarises the basics and is not legal advice.
Double opt-in means a new subscriber signs up and then confirms by clicking a link in a confirmation email before they receive marketing. It proves the address is real and that its owner wanted to subscribe. That improves list quality, reduces complaints and gives you a stronger consent record.
6 min read
Comparisons
How browser-based inbox automation compares with workflow tools and API integrations, and when each approach makes sense.
Browser 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.
An email API integration talks to the provider's servers directly with credentials or OAuth, while browser automation works inside the webmail page you are already signed in to. APIs are better for scale, server-side jobs and structured data. Browser automation is better when you need to see the inbox as a person would and want to avoid handing mailbox credentials to another service.
See how a subject and preheader truncate on mobile and desktop inboxes.
Open free tool
Email Automate for Chrome
Automate the mailboxes you own, right inside Chrome.
Runs in the Gmail, Outlook, Yahoo, AOL and Proton tabs you are already signed in to. Filter by sender or campaign, set reading times and limits, keep a local activity log. No mailbox passwords, one-time licence.