Connecting Google Drive, your calendar and your mail: how that really works

What a connection actually is

Almost every serious service — Google Drive, your calendar, your accounting package — has a second entrance next to the regular website: an API. Think of it as an official service desk for software. Where you click and drag, a program can do exactly the same through that desk: store files, schedule appointments, prepare emails.

A connection is nothing more than one program knocking on another program's desk on your behalf. The only question that matters is — with which key?

The consent screen: you're not giving a password, you're giving a key

You know that screen — "This app wants access to your Google account. Allow?" That is the most important, and most misunderstood, part of this story.

When you click Allow, you are not giving your password. Google creates a separate key for that one app, with exactly the permissions listed on the screen — say, reading files yes, sending mail no. You can revoke that key at any time through your Google account, without changing your password.

This system is called OAuth, and it's why connecting is much safer than it feels: scoped permissions, per app, always revocable.

Building a connection yourself

If you want to hook your own software to Google Drive, these are roughly the steps:

1. Create a free developer project in the Google Cloud Console.
2. Enable the Drive API (or Calendar, Gmail API) for that project.
3. Configure the consent screen: name, logo and which permissions (scopes) you request.
4. Build the sign-in flow: the user clicks Allow, your program receives the key.
5. Store that key safely — and build the logic to refresh it automatically, because it expires.

Steps 1 to 4 are an afternoon of puzzling. Step 5 is where hobby projects strand: expired keys, error handling, and Google's verification process once your app requests more permissions. Doable — but it's precision work, and every service does it slightly differently.

How Mia does it

With Mia, the connection is one sentence: "connect my Google Drive." You get Google's official consent screen, click Allow once — done. Storing and refreshing keys happens inside your own isolated environment, and you can always revoke access through your Google account.

The real point: the connection isn't the goal, it's the starting point. After that, every next step is one message:

• "Automatically file every quote I send into the right client folder"
• "Put requests from my inbox straight into the planning"
• "Every Monday, make an overview of last week's invoices"

That's the difference between having a connection and getting something out of it.