Sections10
Reading time8 min
EvidenceWorking integration

POST /api/sheets/export

Export extracted data to Google Sheets without copying rows or rebuilding headers. Connect Google once, choose a reviewed extraction and push it to a fresh tab. Document metadata goes to a separate Document Fields tab, and an earlier push is never overwritten.

How Google Sheets receives rows and fields

  • 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

Dynamite Docs logoDynamite Docs
The handoff
Supplier invoice: A new Google Sheets tabConnect Google Sheets once. Open the export menu. Get a fresh tab. Keep working in Sheets. Illustrative example, not extracted customer data.A REVIEWED DOCUMENT, CONNECTED TO YOUR WORKSOURCE DOCUMENTSupplier invoiceFresh tab per pushyour earlier tabs are…Document Fields tabdocument name, dates,…Dynamite DocsGoogle…DestinationReview before delivery
  1. 01Connect Google Sheets once
  2. 02Open the export menu
  3. 03Get a fresh tab
  4. 04Keep working in Sheets
Reviewed rows, ready for your sheet. Illustrative example.
01

Connect Google Sheets once

The OAuth connection requests the drive.file scope for Sheets push. If you also use Drive import or Drive export, the same encrypted connection covers them without creating a separate account link.

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

Dynamite Docs logoDynamite Docs
Inside the output
Supplier invoice: A new Google Sheets tabFresh 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. Illustrative example, not extracted customer data.Extracted fieldsDOCUMENT SCHEMAfresh_tab_per_pushyour earlier tabs are never…document_fields_tabdocument name, dates, extraction…last_used_spreadsheetreused by default for continuityA new Google Sheets tabDESTINATION FIELDSFresh tab per pushMap to your destination schemaDocument Fields tabMap to your destination schemaLast-used spreadsheetMap to your destination schemaIllustrative mapping. Confirm the field names accepted by your destination.
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
Reviewed rows, ready for your sheet. Illustrative example.

A push lands two things in your spreadsheet:

Fresh tab per pushyour earlier tabs are never touched
Document Fields tabdocument name, dates, extraction id, confidence
Last-used spreadsheetreused by default for continuity
Offline OAuth consentrefresh tokens, encrypted at rest
Exact scope trackingspreadsheets for push; Drive scopes only for Drive
Revocabledisconnect from the workspace anytime

A realistic example

A bookkeeper pushing a vendor invoice run to their working spreadsheet:

PushTab createdContents
Invoice batch 2026-08INV-2026-08Vendor, date, number, line items, tax, total
Bank statement JulBS-JULDate, description, debit/credit, amount, balance
Both pushesDocument FieldsSource document names + extraction ids + confidence

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 records the exact granted scopes for Sheets and Drive features.

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 optional Drive features, so you can review and remove the Google connection in one place.

Setup and delivery questions

Extraction guides

Related integrations

Document workflows it feeds

From the blog

Push your next extraction to Sheets.

Connect Google once, then push any extraction with one click. Fresh tab, metadata included, nothing overwritten.

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.