Gmail Connect normally signs you in through a shared Google app. Google caps
any shared app that reads mail at 100 people, for the lifetime of the app, and shows an
"unverified app" warning until it passes a paid annual security audit.
Making your own key removes both. No cap, no warning about someone else's app, and
nothing shared with any other user — the key belongs to a Google project you own, and only
you ever use it. Gmail Connect then talks to Google directly, with nothing of ours in the
path at all.
You will need a Google account. There is no billing, no card, and no code to write.
Google moved this out of "APIs & Services" into the Google Auth Platform during
2025, so most guides you will find online describe menus that no longer exist. These are the
pages as they are now:
Add or remove scopes → paste https://www.googleapis.com/auth/gmail.modify
into the manual box → Add to table → Update → Save.
Publish it, don't leave it in Testing. A project in Testing hands out keys that Google
expires after 7 days, and your widget would drop out every week. Publishing shows you
an "unverified app" screen the first time you sign in — that is expected for a project only
you use, and you click through it once.