Skip to content
Storage

Mavio + Google Drive.

Choose the Drive folder Mavio writes meeting documents into. Mavio uses the per-file Drive scope, so it can only see files it created — never the rest of your Drive.

AvailableOAuth · one-click setupFree plan included
Setup time
< 60s
OAuth · no engineering
Features
3
In production
Modes
1
Standard
Compliance
Secure
AES-256 · GDPR ready
What you get

Built for the way Google Drive actually works.

You Choose The Folder

Nominate the Drive folder meeting documents should land in, per workspace or per meeting skill, so the written record files itself where your team already looks.

Only Files Mavio Created

Mavio holds the per-file Drive permission. It can see the documents it wrote and the folder you pointed it at. The rest of your Drive is not visible to it, by design and by Google's enforcement.

Temporary Files Clean Themselves Up

Charts that need to be embedded into a document are uploaded, embedded, and then deleted. Mavio does not leave working files behind in your Drive.

Setup

Live in a minute, not a meeting.

01

Connect Google Drive

In Mavio, open Settings > Integrations and choose Google Drive, or connect it alongside Google Docs. Sign in with Google and grant per-file access.

02

Pick A Destination Folder

Choose the folder new meeting documents should be created in. You can use one folder for everything, or a different folder per meeting skill.

Capabilities

What works on day one.

Create files in the folder you choose
List the destination folder
Delete its own temporary uploads
Browse your Drive
Read or download your existing files
Delete files Mavio did not create
Deep dive

Google Drive + Mavio in detail.

Google Drive + Mavio

The Drive integration is deliberately small. Its whole job is to decide where the documents Mavio writes should live, and to let Mavio put them there.

What it is for

When Mavio creates a Google Doc from a meeting, that document has to go somewhere. Connecting Drive lets you nominate the folder — a shared team drive for client calls, a private folder for interviews, a different one per meeting skill.

It also covers the mechanics of embedding: a chart produced by a meeting skill has to be uploaded before it can be placed inside a document. Mavio uploads it, embeds it, and deletes the upload.

The scope, and why it is the narrow one

Mavio requests drive.file, not full Drive access. drive.file is Google's per-file scope: an application holding it can only see files it created itself, or files you explicitly opened with that application. Google classifies it as non-sensitive precisely because it cannot reach the rest of your Drive.

The practical consequence is worth stating plainly, because "we connect to your Drive" usually means something much larger:

  • Mavio cannot list, open, search, or download the files already in your Drive.
  • Mavio cannot delete anything it did not create.
  • Mavio can create files in the folder you chose, and manage the ones it created.

Privacy

Google user data from this integration is used only to place and manage the documents you asked Mavio to write. It is never sold, never used for advertising, and never used to train models. The full disclosure is at mavioapp.com/google-data.

Questions

Frequently asked.

Connect in a minute

Start capturing Google Drive meetings today.

Free plan, no credit card. One-click OAuth, no engineering required.