All integrations
Google Sheets push
OUT — POST /api/sheets/export
Spreadsheets are where document data goes to be used, and Google Sheets is where most small teams already keep their books and ledgers. Dynamite Docs connects to your Google account once, then pushes any extraction into a spreadsheet: a fresh tab per push, a Document Fields tab for metadata, and never an overwrite of the work you have already done.
Try it free or read the API & webhooks docs.
The gap between a table and a spreadsheet is real work
- An extracted table is not in your spreadsheet until someone formats it and copies it over, manual work that quietly eats the value of the extraction.
- Re-pushing the same document (after a correction, say) usually means overwriting or duplicating rows by hand.
- The document name and extraction id get dropped in the copy, so the sheet cannot be traced back to its source.
- Every spreadsheet-bound team has its own favorite way to paste, and none of them survive contact with a formatted table.
How the Sheets push works
01 — Connect Google Sheets once
The OAuth connection is the same one that powers Drive import, with one consent, offline access, and tokens encrypted with the BYOK encryption standard.
02 — Open the export menu
From any completed extraction, choose the Sheets push. Dynamite Docs reuses the last-used spreadsheet if you want, or picks a new one.
03 — Get a fresh tab
The extraction is written to a new tab in the spreadsheet. A Document Fields tab carries the metadata (document name, dates, extraction id, confidence). Earlier pushes are never overwritten.
04 — Keep working in Sheets
The tab is a normal sheet: filter, pivot, mail-merge, or feed it into the formulas you already run. The data stays linked to the source document in your workspace.
What the Sheets push writes
A push lands two things in your spreadsheet:
- Fresh tab per push — your earlier tabs are never touched
- Document Fields tab — document name, dates, extraction id, confidence
- Last-used spreadsheet — reused by default for continuity
- Offline OAuth consent — refresh tokens, encrypted at rest
- Combined scopes — one connection also covers Drive import
- Revocable — disconnect from the workspace anytime
A realistic example
A bookkeeper pushing a vendor invoice run to their working spreadsheet:
| Push | Tab created | Contents |
|---|
| Invoice batch 2026-08 | INV-2026-08 | Vendor, date, number, line items, tax, total |
| Bank statement Jul | BS-JUL | Date, description, debit/credit, amount, balance |
| Both pushes | Document Fields | Source document names + extraction ids + confidence |
A push is a link between the workspace and the sheet
The one-click Sheets push exists because the step after extraction, getting the data somewhere it can be used, is where most workflows stall. A fresh tab per push means the spreadsheet becomes an append-only ledger of your extractions. Every push is a new, clearly named tab, so a corrected re-push adds the updated tab instead of destroying the last one. Teams that reconcile against these sheets trust the history, because nothing gets silently overwritten.
The Document Fields tab is the detail most tools skip, and it is the one that makes the sheet auditable. Document name, extraction id, dates, and confidence ride alongside the data, so a row in your spreadsheet can be traced back to the exact source document and extraction. For a finance team that later has to prove where a number came from, that link is the whole point.
Reusing the last-used spreadsheet keeps the workflow sticky without forcing a picker dialog every time; the push simply appends a tab to the spreadsheet you already work in. If you prefer a fresh target, the choice is there. Because the OAuth connection is shared with Drive import, one consent covers both, and tokens stay encrypted with the same AES-GCM standard applied to provider keys.
The connection is deliberately scoped and revocable. Offline consent means the server can push to the sheet after you close the browser, which is what makes the push work from anywhere, and disconnecting from the workspace revokes the whole thing in one action.
What the Sheets push does and does not
Does
- Pushes a completed extraction to Google Sheets as a fresh tab, with a Document Fields tab for metadata.
- Reuses the last-used spreadsheet by default and never overwrites your earlier tabs.
- Encrypts the OAuth token and uses one revocable connection shared with Drive import.
Does not
- Does not modify or format cells in your other tabs. Each push is its own new tab.
- Does not write back cell edits you make in Sheets (no two-way sync).
- Does not store OAuth tokens in plaintext or push without your connection.
Why Sheets is the default destination
Most small finance teams already live in Sheets; a one-click push removes the copy-paste that separates an extraction from a working ledger.
Append-only tabs keep your spreadsheet history trustworthy. Re-pushes add, never destroy.
One encrypted, revocable OAuth connection covers Sheets and Drive, so the Google surface stays coherent and under your control.
Questions, answered
Do I need a separate Google connection for Sheets?
No. Sheets push and Drive import share one OAuth connection with combined scopes. If yours predates the Drive scopes, a one-time reconnect enables both.
Will a push overwrite my existing data?
No. Each push creates a fresh tab. Your earlier tabs are left exactly as they are.
What is in the Document Fields tab?
Metadata about the push: the source document name, extraction id, dates, and confidence, so rows in the sheet can be traced back to their source.
How do I revoke access?
Disconnect from the workspace. One action revokes the shared connection for both Sheets and Drive.
Document workflows it feeds
Open app, no payment details.