Sections10
Reading time8 min
EvidenceWorking integration

/api/drive/*

Google Drive document extraction should not begin with a download folder full of renamed copies. Connect the Google account once, choose the files in Google Picker and review the extracted rows beside each source. When the data is ready, write a new XLSX, CSV or JSON file back to Drive. The original stays where it was.

Google Drive account and file access

  • Manual Drive workflows create two extra transfers for every document: download before extraction and upload after export.
  • Local copies lose the shared folder context, which makes the right source and the latest result harder to trace.
  • A finished workbook belongs back in the team Drive, not in one person's Downloads folder or an email attachment.
  • The connection should request a clear Google scope and remain easy to revoke.

How the Drive connection works

Dynamite Docs logoDynamite Docs
The handoff
Document library: Google DriveConnect Google once. Browse and import. Extract and review. Export back to Drive. Illustrative example, not extracted customer data.A REVIEWED DOCUMENT, CONNECTED TO YOUR WORKSOURCE DOCUMENTDocument libraryDrive importPDFs, images, Sheets,…Drive exportfinished extractions…Dynamite DocsGoogle…Import sourceReview before delivery
  1. 01Connect Google once
  2. 02Browse and import
  3. 03Extract and review
  4. 04Export back to Drive
Import a file. Return reviewed data. Illustrative example.
01

Connect Google once

One OAuth connection can grant the exact scope used by each feature: drive.file for Google Sheets push, Drive exports, and Drive imports via Google Picker. The connection is per account, encrypted, and revocable from the workspace.

02

Browse and import

The standard Google Picker lets you securely browse, search, and select one or multiple files directly from your Drive. Selected files stream to the client for the normal upload pipeline, so R2 persistence and browser-only storage work exactly as they do for a drag-and-drop.

03

Extract and review

The imported document uses the normal extraction pipeline with confidence-scored rows, saved correction patterns, hosted page caps, and the same file limits as other uploads.

04

Export back to Drive

Push a finished extraction to your Drive as an XLSX workbook, CSV file, or JSON file. The endpoint uses the same format builders as direct downloads, then creates a new Drive file.

What the Drive connection moves

Dynamite Docs logoDynamite Docs
Inside the output
Document library: Google DriveDrive import: PDFs, images, Sheets, Docs, and more via Google Picker. Drive export: finished extractions as XLSX, CSV, or JSON files. Google Picker: secure multi-file selection with standard Drive UI. Illustrative example, not extracted customer data.Extracted fieldsDOCUMENT SCHEMAdrive_importPDFs, images, Sheets, Docs, and…drive_exportfinished extractions as XLSX,…google_pickersecure multi-file selection with…Google DriveDESTINATION FIELDSDrive importMap to your destination schemaDrive exportMap to your destination schemaGoogle PickerMap to your destination schemaIllustrative mapping. Confirm the field names accepted by your destination.
Drive import
PDFs, images, Sheets, Docs, and more via Google Picker
Drive export
finished extractions as XLSX, CSV, or JSON files
Google Picker
secure multi-file selection with standard Drive UI
Import a file. Return reviewed data. Illustrative example.

One shared OAuth connection powers both directions, with tokens encrypted using the same BYOK encryption that protects your API keys:

Drive importPDFs, images, Sheets, Docs, and more via Google Picker
Drive exportfinished extractions as XLSX, CSV, or JSON files
Google Pickersecure multi-file selection with standard Drive UI
Importable filternon-importable MIME types hidden by default
Shared OAuth connectionreuses the Sheets connection; revocable
Token securityAES-GCM encrypted, never stored plaintext

A realistic example

A typical audit-adjacent loop with Drive:

StepWhere it happensOutcome
Client drops a trial balance PDF into a shared Drive folderGoogle DriveDocument waits, no download needed
You import it from the Drive panel in Dynamite DocsDynamite Docs workspaceFile streams into the normal pipeline, parsed as rows
Review low-confidence balances and exportDynamite Docs Data StudioClean .xlsx written back to your Drive

What the Drive connection does and does not

Does

  • Opens Google Picker for user-controlled browsing and multi-file selection.
  • Streams selected files to the client so the standard upload pipeline decides storage and extraction.
  • Exports finished extractions back to your Drive as new XLSX, CSV, or JSON files.

Does not

  • Does not scan or index your entire Drive. Only the files you select are fetched.
  • Does not overwrite files in your Drive; exports are written as new workbooks.
  • Does not keep your OAuth token unencrypted. Tokens are AES-GCM encrypted like every other secret.

Why Drive is more than a file picker

Import reuses the upload pipeline, so Drive-sourced files get identical storage, extraction, and review behavior, no second-class path to maintain.

Export closes the loop your team already has. The results go back to the Drive where the source documents and the shared spreadsheets already live.

One scoped, revocable OAuth connection with encrypted tokens keeps the integration useful without a broad, unexaminable scope grant.

Setup and delivery questions

Extraction guides

Related integrations

Document workflows it feeds

From the blog

Pull documents from Drive and send results back.

Connect Google once from the workspace, import a PDF straight from your Drive, and export the finished extraction back as an .xlsx, no downloads in between.

Can we save optional cookies?

Essential cookies keep you signed in. With your permission, optional analytics cookies and masked session replays help us understand usage and diagnose errors. Privacy policy. Change your choice anytime in Cookie settings.