All integrations
Google Drive import & export
IN + OUT — /api/drive/*
Most teams keep their documents in Drive before they ever get extracted. Dynamite Docs connects to your Google account once, then you can import a document straight from your Drive and push finished extractions back out as Excel files, without downloading a thing in between.
Try it free or read the API & webhooks docs.
Drive is where the documents sit, and where the exports should go
- Documents live in Drive, extraction happens in a tool, and the two never talk, so every file is downloaded and re-uploaded by hand.
- Finding the right file means re-navigating a shared Drive folder in a second app with a different search.
- Finished spreadsheets end up scattered across email threads and local downloads instead of back in the shared Drive where the team expects them.
- Connecting a tool to Google usually means a broad, unexplained scope grant, not a scoped connection you can review and revoke.
How the Drive connection works
01 — Connect Google once
One OAuth connection with combined scopes, spreadsheets plus read access to Drive. The connection is per account, encrypted, and revocable from the workspace.
02 — Browse and import
The Drive panel lists your documents with name search and pagination, filtered to importable file types by default. Pick one and its bytes 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 extracts on the same queue as everything else: confidence-scored rows, remembered corrections, same page caps.
04 — Export back to Drive
Push a finished extraction to your Drive as an .xlsx workbook. The export rides the same builder as downloads, just written to your Drive instead of your downloads folder.
What the Drive connection moves
One shared OAuth connection powers both directions, with tokens encrypted using the same BYOK encryption that protects your API keys:
- Drive import — PDFs, images, Sheets, Docs, and more
- Drive export — finished extractions as .xlsx
- Name search — paginated file listing inside the workspace
- Importable filter — non-importable MIME types hidden by default
- Shared OAuth connection — reuses the Sheets connection; revocable
- Token security — AES-GCM encrypted, never stored plaintext
A realistic example
A typical audit-adjacent loop with Drive:
| Step | Where it happens | Outcome |
|---|
| Client drops a trial balance PDF into a shared Drive folder | Google Drive | Document waits, no download needed |
| You import it from the Drive panel in Dynamite Docs | Dynamite Docs workspace | File streams into the normal pipeline, parsed as rows |
| Review low-confidence balances and export | Dynamite Docs Data Studio | Clean .xlsx written back to your Drive |
Drive import is the same pipeline with a different front door
The interesting design decision is that Drive import does not invent a second extraction path. The file bytes are proxied to the client, and the existing upload pipeline decides what happens next: R2-backed cloud storage on PRO and ULTRA, or browser-only storage on FREE and HOBBY. That means a document from Drive behaves identically to a document you dragged in, same folders, same confidence review, same exports. There is no second class of Drive-sourced files to learn or debug.
Export is the mirror. Instead of downloading a workbook and re-uploading it to Drive by hand, the finished extraction is written to your Drive as an .xlsx using the same workbook builder as regular exports. For a team that keeps its shared spreadsheets in Drive, that closes the loop. The source documents and the extracted results live in the same place your team already works.
Scope is the part most tools get wrong, and it is the part worth checking. The connection is one OAuth grant with combined scopes: spreadsheets, read-only Drive, and Drive file scope. Existing connections that predate the Drive scopes are flagged and need a one-time reconnect before Drive import is available. Because the connection is shared with Google Sheets push, one consent covers both directions, and revoking it is a single action from the workspace.
Token storage follows the same standard as everything else sensitive. OAuth tokens are encrypted with AES-GCM using the BYOK encryption key, the same protection applied to your AI provider keys, so the credential that can read your Drive is never sitting in a database as plaintext.
What the Drive connection does and does not
Does
- Lists your Drive files with name search and pagination, filtered to importable types by default.
- Streams a selected file to the client so the standard upload pipeline decides storage and extraction.
- Exports finished extractions back to your Drive as .xlsx workbooks.
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.
Questions, answered
Do I need a separate connection for Drive and Sheets?
No. Both use the same OAuth connection with combined scopes. If your connection predates the Drive scopes, you will be prompted to reconnect once to enable Drive import.
What file types can I import?
The panel lists importable files by default, PDFs, images, Sheets, Docs, and other formats the extraction pipeline understands. Non-importable types are filtered out of the list.
Where do imported files get stored?
Exactly where an upload would: R2-backed cloud storage on PRO and ULTRA, browser-only storage on FREE and HOBBY. The import simply feeds the existing pipeline.
How do I revoke access?
Disconnect from the workspace. One action revokes the shared connection for both Drive and Sheets.
Document workflows it feeds
Open app, no payment details.