Google Drive (Meet recordings)

On Google Drive (Meet recordings)'s side

1. In Google Drive, open (or create) the folder your recordings land in. For Google Meet that is usually the "Meet Recordings" folder in the host's My Drive; any folder works.
2. Copy the folder link from the address bar (it contains /folders/) and paste it on your Flows page under "Add a Drive folder".
3. The card then shows an address ending in .iam.gserviceaccount.com. Share the folder with that address as a Viewer — the same Share button you would use for a colleague.
4. That is the whole connection. No Google sign-in is handed to MeetNotes, and Viewer means we can read the files, never change or delete them.

What to paste from your flow card

• The service-account address shown on the source card — into Drive's Share dialog, as a Viewer.
• Your folder link — into MeetNotes when you add the source.

What we never ask for: Your Google password, "Sign in with Google" for the workspace, or Editor access. Viewer on one folder is all we take.

How to test

1. Drop one short audio file into the folder (or record a short Meet call with recording on).
2. Within about 5–10 minutes the recent activity on your Flows page shows it as received → done. The card shows the last check time.
3. If nothing arrives after 15 minutes, open the folder's Share dialog and confirm the service-account address is listed as a Viewer, and that the file was added after the source was created.

When an event shows failed or skipped

The Flows page prints one short reason per event. Here is what each one on this connector means and what to do.

• fetch failed — We could not download the recording from the link the provider sent — the link had expired, it needed a login we do not hold, the file was over 300 MB, it pointed at a private address, or the server did not answer. We retry a few times before giving up. If your recordings need a login, set "If the recording needs a login" on the source.
• audio files only — The file was not audio — a picture, a document, or (except from a Drive folder) a video. Only a Drive folder source accepts video; every other door wants an audio file.
• audio unreadable — The file was named like audio but could not be decoded: empty, cut short, or not the format its name claims. Not retried. Send the recording again from the provider.
• no minutes — Your workspace had no pooled minutes left, so we did not download the recording. Skipped, not retried. Top up the pool and have the provider send the recording again.
• processing failed — The recording came in but something on our side failed after that. We are alerted automatically; if it keeps happening, write to support@getmeetnotes.com with the reference shown on the Flows page.
• file too large — A file in the Drive folder is over 2 GB — almost always a video nobody meant to transcribe. Skipped. Export the audio track, or trim the video, and drop the smaller file in.

The full list, across every connector, is on the setup index.