Is the Google Drive integration live?

Watch-folder automation is on the roadmap. Today you download the file from Drive, upload to RecordX, then export the transcript and upload it back next to the source.

Does it work with Shared Drives?

Yes - Shared Drives (Team Drives) and My Drive folders both fit the plan. Shared Drive folders are typically the better fit because the team already has access to the transcript siblings.

Which Google plan is needed?

Any Google account with Drive works - personal Gmail, Workspace, or education. RecordX uses the standard Drive API.

What about Google Meet recordings?

Google Meet cloud recordings on Workspace Business plans and above save to a Meet Recordings folder in Drive. Once the watch-folder is live, pointing RecordX at that folder catches every Meet recording automatically.

Where do outputs land?

Sibling files in the same folder: recording.mp4 gets recording.transcript.txt and recording.summary.md next to it. You can also route outputs to a /Transcripts subfolder.

RecordX + Google Drive

Category: storage - Status: roadmap

Start for free → No credit card required.

What it does today

The watch-folder sync isn't shipped. Today the flow is manual: download the audio / video from Drive, upload to RecordX, then export the transcript and upload it back to the same folder. The planned integration will watch a Drive folder or Shared Drive you nominate, transcribe every new audio / video that lands, and write transcript, summary and action-item files back as siblings.

Setup today

Create your RecordX account at recordx.io/register.html.
Right-click the audio / video in Drive and choose Download.
Drop the file into the RecordX web app.
Wait for transcript, summary, action items.
Export (TXT, VTT, SRT, DOCX) and upload back next to the source in Drive.

Setup (once the watch-folder ships)

Open settings in the RecordX web app and click Connect Google Drive.
Sign in and consent to the folder / drive scope requested.
Pick the folder or Shared Drive to watch.
Choose output preferences: sibling files vs /Transcripts subfolder.
Pick formats: TXT, VTT, SRT, DOCX, JSON.
Drop a test recording in the folder; check the sibling transcript appears.

Data sync (planned)

Data	Direction	Notes
Audio / video files	Drive → RecordX	New files in watched folders trigger transcription.
Transcript	RecordX → Drive	Sibling file: `recording.transcript.txt`.
Summary	RecordX → Drive	Sibling Markdown or DOCX file.
Action items	RecordX → Drive	Included in the summary output.
Speaker labels	RecordX → Drive	Embedded in the transcript when detected.
Source media	Not modified	Original file untouched.
Drive comments	Not synced	Kept in Drive; RecordX doesn't read them.

Permissions and scopes

The planned OAuth scope is https://www.googleapis.com/auth/drive.file - the "app-created files and files the user opens with the app" scope. That's the least-privilege scope that lets RecordX read the media files you nominate and write the transcript siblings, without granting access to your whole Drive. No domain-wide delegation is requested.

Pricing and limits

RecordX doesn't charge extra for Drive transcription - files consume your normal monthly minutes. Google Drive API calls are free within Google's per-user quotas (roughly 1,000 requests per 100 seconds per user). Storage is your own Google account quota; the transcript sibling is usually a few KB, so the footprint is small. Very large media files use resumable upload internally.

Common gotchas

Shared Drive vs My Drive: sharing on a Shared Drive is inherited, so make sure the team you want to see the transcript already has access.
Google Meet recordings save to a Meet Recordings folder - point RecordX there once the watch-folder ships.
Docs, Sheets, Slides are Google-native formats and are ignored - only true media files are transcribed.
Change tokens can lag by a few seconds; new-file pickup isn't instant.

Alternatives while you wait

Zapier or Make: Drive "New file in folder" → RecordX "Transcribe file".
Google Meet's own built-in transcript on Workspace - fine if you don't need Hebrew / 50+ languages.
Manual upload from Drive to RecordX, manual download back.
Dropbox - same shape.

FAQ

Is the Google Drive integration live?: Watch-folder automation is on the roadmap. Today you download the file from Drive, upload to RecordX, then export the transcript and upload it back next to the source.
Does it work with Shared Drives?: Yes - Shared Drives (Team Drives) and My Drive folders both fit the plan. Shared Drive folders are typically the better fit because the team already has access to the transcript siblings.
Which Google plan is needed?: Any Google account with Drive works - personal Gmail, Workspace, or education. RecordX uses the standard Drive API.
What about Google Meet recordings?: Google Meet cloud recordings on Workspace Business plans and above save to a Meet Recordings folder in Drive. Once the watch-folder is live, pointing RecordX at that folder catches every Meet recording automatically.
Where do outputs land?: Sibling files in the same folder: recording.mp4 gets recording.transcript.txt and recording.summary.md next to it. You can also route outputs to a /Transcripts subfolder.

Setup checklist

RecordX account created.
Google Drive folder / Shared Drive identified for the watch.
Sharing on that folder covers the team who should see the transcript.
Meet Recordings folder identified if you record Meet calls.
Retention rules aligned.

Related integrations

Dropbox - same shape.
Google Calendar - live meeting side.
Google Meet - the recording source.
Notion - if summaries belong in a doc, not a file.
See all integrations.

Start for free