Google Sheets + Go Fig
Sync Google Sheets with Go Fig for governed spreadsheet ingest and live updates.
Google Sheets is where most finance teams actually build: driver models, commission schedules, regional forecasts, ad-hoc what-ifs, and the approved budget often lives as a shared workbook. Go Fig connects to Google Sheets through a service account, ingests named ranges at the cell grain, and brings that data into the Financial Intelligence Graph with the same governance as any API-sourced connector. Schemas are declared once and validated on every sync, so an inserted row or a renamed column surfaces as a schema-change event instead of breaking a dashboard. Version history is retained, uploader identity is tracked, and Celeste can query the sheet directly alongside GL, CRM, and operational data. The design goal is to let finance keep building in spreadsheets where that is the right tool, while the downstream graph treats the data as governed rather than as a one-off paste.
Key facts
- Auth
- Google service account + IAM
- Grain
- Named range, cell-level
- Schema tracking
- Column-name anchored, drift alerts
- Two-way
- Read by default, write-back supported
- Sync cadence
- 15-minute default, on-demand supported
What you can do with Google Sheets data in Go Fig
Budget and forecast ingest
Pull the approved budget workbook and join it to GL actuals for automatic variance analysis, without converting to a planning tool.
Driver and commission models
Ingest operational driver sheets (unit volumes, commission rates, territory assignments) so revenue projections stay tied to the source of truth.
Governed handoff from ad-hoc sheets
Move a working spreadsheet into the governed graph with schema tracking and versioning, without losing the flexibility of Sheets.
Data available from Google Sheets
Go Fig extracts and normalizes the following data from your Google Sheets account:
How to connect Google Sheets
Provision the Go Fig service account
Go Fig issues a Google service account email specific to your workspace. Your Google Workspace admin approves it in IAM. The service account is scoped to read-only on Google Sheets by default; write-back requires a separate scope approval.
Share the target sheets with the service account
For each sheet you want ingested, share it with the service account email (Viewer, or Editor for write-back). This is the same share pattern used for any Google collaborator, so it fits existing admin habits. Go Fig lists every sheet the service account has access to, so access is always visible.
Declare the schema (range, headers, types)
For each sheet, pick the named range or A1 range that contains the data (not the whole tab, which often includes formatting rows). Confirm the header row and declare types per column. Go Fig validates every sync against this schema, so a column-rename or an inserted total row is caught at ingest.
Set sync cadence and join downstream
Default sync is every 15 minutes. Sheets that change rarely (annual budget) can be set to daily; sheets that drive live dashboards can be set to on-demand via webhook or Celeste trigger. Once ingested, the data is queryable alongside any other connected source.
Authentication: Google service account authenticated via domain-wide delegation or direct share. The service account email is shared on each sheet with Viewer permission (or Editor if write-back is enabled). Access is managed through Google Workspace IAM so your admin sees exactly what Go Fig can read.
Common Questions About Google Sheets Integration
How does Go Fig handle sheets where people insert rows or rename columns?
Schema is declared once with the column header as the stable anchor. Inserted rows are fine as long as they land inside the declared range. Renamed columns trigger a schema-change event, the sync is held in staging, and an admin is notified. This is the same governance pattern used for API-sourced connectors, adapted for the reality that humans edit spreadsheets.
Are formulas evaluated, or does Go Fig read the formula text?
Values only. Go Fig reads the evaluated value of every cell (what a user sees), not the formula text. This means complex formula logic runs inside Sheets where it was authored, and Go Fig ingests the result. If you need the formula logic itself exposed for audit, that can be captured as a separate schema event.
What about pivot tables, filter views, and charts?
Pivot-table output cells are ingested like any other cell range (declare the range, declare the types). Filter views are respected if you point the sync at a filter view rather than the underlying range. Charts are metadata-only, Go Fig records that a chart exists but does not render it, because the underlying data is already in the graph and can be visualized natively.
Can Go Fig write data back to Google Sheets?
Yes, with Editor permission on the target sheet. The most common write-back pattern is pushing a computed metric (variance, forecast, reconciled number) back into a summary tab so non-finance users can see it in Sheets without logging into Go Fig. Write-back is always to a dedicated range, so user-edited cells are never overwritten.
How does access control work with a service account?
The service account is a Google Workspace identity managed by your admin. Every sheet it has access to is visible in Google Admin and in the service account's Drive view. Revoking access to any specific sheet is a one-click unshare. For org-wide audits, Go Fig also reports which sheets are currently being read and by which user of the Go Fig workspace triggered the original connection.
Related Operations integrations
Other systems Go Fig connects into the Financial Intelligence Graph, often alongside Google Sheets.
Industries running Google Sheets with Go Fig
Strategic CFOs in these industries typically stitch Google Sheets into their Financial Intelligence Graph alongside their ERP and operational systems.
Ready to connect Google Sheets?
See how your Google Sheets data looks in Go Fig with a personalized demo.
Book a Demo