I subscribe to a small number of newsletters that consistently break industry news first. Instead of opening every one by hand, I connect my inbox to an AI tool with read-only access, scoped so it can only view and summarize, never send, delete, or change anything. It scans just those subscriptions and tells me what changed in my industry and my clients' industries.
Every video in my "30 Hacks From Dahlia" series ends with the same line: I help small teams do big things. A lot of that is automating the parts of the day that don't need me personally. This is the hack people ask about most, because it means connecting an AI tool to your actual email inbox, and everyone hesitates over that.
Watch: Hack 31, the tool that reads my newsletters for me
Why I built this in the first place
Staying on top of trends in my industry is part of the job. I don't chase all of it. I subscribe to the handful of newsletters I already trust, the ones that bring the news first instead of recycling it. That part hasn't changed in years.
What changed is what happens after I subscribe. I used to open each one, skim for anything that mattered, and half the time forget I'd read it by the following week. Now a tool goes through my email, finds those specific subscriptions, reads them and summarizes what's in them. I find out what changed in my industry, or my clients' industries, without opening a single one.
Connecting your email safely
Every time I mention this, someone asks, "wait, you gave an AI access to your email?" Not exactly. I gave it read-only access, a narrower permission than the one people picture. That difference is why I'm comfortable running this unattended.
On Gmail
Gmail's API has separate, named permission scopes. The one I use is gmail.readonly. It lets a connected tool view and read messages, and nothing else: no sending, no deleting, no changing labels or folders. When you authorize a connector, Google's OAuth screen shows in plain language what you're granting, something like "Read all resources and their metadata," not "Send email as you," unless you separately approve that broader permission.
On Outlook or Microsoft 365
Microsoft's equivalent is in the Graph API permission model. The scope is Mail.Read, kept apart from Mail.ReadWrite and Mail.Send. A tool that only requests Mail.Read cannot send or modify a message, the same way a read-only database credential cannot run a delete statement.
I'm not relying on the tool to behave. A connector authorized only for gmail.readonly or Mail.Read cannot send or delete an email, whatever it's told to do. That's what makes it safe to leave running in the background.
A read-only permission can't send or delete, no matter what the tool is told.
What the digest actually looks like
There's no dashboard. The tool connects through MCP, the open protocol I use to link most of the AI systems I run, scoped to only the newsletter senders I've chosen. It reads what came in, pulls out what's new or changed, and hands me a plain summary for my industry and my clients' industries. If nothing meaningful changed that week, there's nothing to read.
Before you connect anything to your inbox
Hack 31 of 30
This is hack 31 in the series, which ran past thirty. The full step-by-step guide and the rest of the series are linked in my bio. If you run more than one inbox for your business or your clients, the pattern is the same: connect only what you need, at the access level the job requires.
Frequently Asked Questions
Read-only access means the connection is scoped so the tool can only view and read your inbox. It cannot send, delete, forward, or modify anything. On Gmail this is the gmail.readonly OAuth scope; on Microsoft 365 it is the Mail.Read Graph API permission. Both are separate, narrower permissions than the ones needed to send or manage mail, and neither one grants that access.
It is safe when the connection is explicitly scoped to read-only and limited to what you actually need it to see. The safety comes from the permission itself, not a promise: a tool authorized only for gmail.readonly or Mail.Read is structurally incapable of sending or deleting anything, regardless of what it is instructed to do. Always check the exact scope you are granting before authorizing any connector.
Check the OAuth consent screen when you authorize the connection. Google and Microsoft both display exactly which permission is being granted in plain language, such as "Read all resources and events on your calendar" versus "Send email as you." If the consent screen only mentions reading or viewing, the send and delete actions are not available to the tool no matter what it is asked to do.
Start small. Pick the three to five newsletters you already trust to break industry news first, the ones you would actually stop and read if you saw them. A tool that summarizes a handful of high-signal sources is more useful than one drowning in every subscription you have ever signed up for.
Sources
