The Google access file

Google asks every application that reads an account to identify itself with an “OAuth client”. Today you (or your organisation) create that client once; its file stays on your computer and serves Gmail, Calendar and Drive. Allow ten minutes. In an organisation, the administrator does it once for everyone.

Steps

1. Open console.cloud.google.com with your Google account.
2. Create a project (for example “Hidden Tokens”).
3. APIs & Services → Library: enable the APIs you need.
   • Gmail: Gmail API
   • Calendar: Google Calendar API
   • Drive: Google Drive API, Google Docs API, Google Sheets API, Google Slides API
4. APIs & Services → OAuth consent screen:
   • Google Workspace: type Internal.
   • Personal Gmail account: type External, then add your address under Test users.
5. APIs & Services → Credentials → Create credentials → OAuth client ID, application type Desktop app.
6. Download the JSON file.
7. In Hidden Tokens → Connectors → Choose the Google access file…, pick that file.

Good to know

• This file identifies your application to Google; it gives access to no mailbox until you sign in. Keep it to yourself all the same.
• With type External left in testing mode, Google expires the sign-in every 7 days. With Internal (Workspace), it does not.
• Adding Drive later: enable the four APIs of step 3, then Sign in on the Drive row. The file does not change.
• Google may show “Google hasn’t verified this app”: it is your own application; continue through “Advanced”.