GOOGLE SHEETS → SNOWFLAKE
Sync each non-empty worksheet from Google Sheets into its own Snowflake table on a schedule, using file-level change detection.
Supaflow scans the configured Drive folder and its subfolders, treats row 1 as the header, and infers a schema for each worksheet. When a spreadsheet's Drive modification time changes, selected worksheets are re-read in full; this is not cell-level change capture. Every connector is included on every Supaflow plan — you pay only for the compute your pipelines consume.
For RevOps, finance, and operations teams bringing shared spreadsheets into Snowflake — with no per-row fees.
Compare managed connectors, manual loads, and custom pipelines by spreadsheet scope, update behavior, deployment model, and billing unit.
Compare Google Sheets and Google Drive ETL options→Verified connector behavior and known limits for this source.
| Feature | How it works | Limit / caveat |
|---|---|---|
| Worksheet as table | Each non-empty worksheet becomes its own table, named from the source file and worksheet. Supaflow scans the configured Drive folder recursively. | A worksheet must have a header row and at least one data row to appear during schema discovery. |
| Worksheet identity validation | Supaflow reads the selected file and worksheet by their saved identities, then validates the saved file name, worksheet name, and folder path. | Renaming or moving a selected spreadsheet, or renaming its worksheet, makes that saved object stale. Refresh the source schema and explicitly select the object at its new identity. |
| Authentication | Choose a Supaflow-managed service account, user OAuth, or a service-account key that you provide. | For either service-account option, share the Drive folder with the service-account email. |
| File-level incremental reads | After the initial run, the connector uses each spreadsheet’s Drive modification time to select work in the next sync window. | Each selected worksheet is re-read in full. The connector does not emit cell-level changes or source-side delete events. |
| Schema discovery | Row 1 is treated as the header row, and column types are inferred from sampled data rows independently for each worksheet. | There is no header-row offset or schema union across separate worksheets. |
| Formula values | Supaflow reads the cached numeric or string result stored with each formula cell in the exported workbook. | Supaflow does not recalculate formulas. A formula without a readable cached result lands as null. |
| Rate limiting | The connector retries Google rate-limit responses and transient server failures with exponential backoff and jitter. | A persistent error is reported after the retry limit is reached. |
| File-level error handling | During sync reads, choose whether a file error stops the sync or skips that file and continues. | The default is FAIL. SKIP leaves the affected worksheet out of the current run. This setting does not apply to schema discovery or stale-object identity errors. |
| Audit metadata | Connector-added spreadsheet name and file ID metadata support source lineage in Snowflake. | — |
| Destination | Discovered worksheets map to Snowflake tables through the pipeline. | Append, merge, reset, and schema-evolution behavior are pipeline and destination settings, not source-side change capture. |
Every Supaflow connector is included on every plan at no extra cost. You pay only for compute consumed, measured in Supaflow Credits (1 credit = 1 billable job hour on an S (Small) Agent node). No per-row fees.
Supaflow discovers each worksheet separately, validates its saved source identity at read time, and reads the cached values in the exported workbook. Changes are detected at the spreadsheet-file level.
File names, worksheet names, and folder paths are part of source object identity. A rename or move does not silently redirect an existing mapping; refresh the source schema and explicitly select the newly named object.
These source-specific cases affect discovery, parsing, or incremental reads. The notes below explain the failure mode and connector behavior.
Failure mode: Google can refuse the .xlsx export request because of access or export constraints, including file size.
Evidence: Schema discovery must export the workbook before it can inspect worksheet fields, and sync reads export it before parsing rows.
Fix: Discovery stops and identifies the spreadsheet. During a sync, FAIL stops on the error and SKIP omits the affected worksheet read. Check access and export constraints, then split the spreadsheet if Google reports its export-size limit.
Failure mode: A selected worksheet was renamed after schema discovery, so the saved source object is stale.
Evidence: Google keeps the numeric worksheet ID, but Supaflow also treats the worksheet name as part of the source object identity and rejects the mismatch.
Fix: Refresh the source schema and explicitly select the worksheet under its new name. Existing mappings do not follow the rename automatically.
Failure mode: A formula cell may not include a readable cached result in the exported workbook.
Evidence: Supaflow reads cached numeric and string results rather than recalculating formulas.
Fix: When neither cached value is available, that cell lands as null and the worksheet read continues.
Failure mode: Title blocks, banner notes, or merged cells above the real header row produce the wrong field names.
Evidence: Schema discovery always uses row 1 as the header and infers each worksheet independently.
Fix: Move the header row to row 1 before connecting the spreadsheet. Separate worksheets do not share or union schema.
Choose a Supaflow-managed service account, user OAuth, or your own service-account key. Set Source File Type to Google Sheets.
Google Drive source docs→Select the folder containing the spreadsheets you want to sync. Supaflow walks subfolders recursively and discovers each non-empty worksheet as a table.
Connect your Snowflake warehouse and review the worksheet tables and fields before creating the pipeline.
Snowflake destination docs→Pick a cron or interval. After the initial run, spreadsheet modification times determine which worksheets are read again.
Schedules docs→Supaflow authenticates with a managed service account, user OAuth, or a service-account key. It scans the configured Drive folder recursively and discovers each non-empty worksheet as a table. Row 1 is the header. When a spreadsheet changes, each selected worksheet is re-read in full.
The existing source object becomes stale because the worksheet name is part of its identity. Refresh the source schema and explicitly select the worksheet under its new name; the existing mapping does not follow the rename automatically.
The export failure stops schema discovery. During a sync, the default Error Handling: FAIL setting stops on the error; Error Handling: SKIP omits the affected worksheet read and continues. Check access and export constraints, then split the spreadsheet if Google reports its export-size limit.
Fivetran measures connector usage in Monthly Active Rows, while Hevo counts a changed Google Sheet's full re-ingestion toward its Events quota. Every Supaflow connector is included on every plan at no extra cost. You pay only for compute consumed, measured in Supaflow Credits (1 credit = 1 billable job hour on an S (Small) Agent node). No per-row fees. Review current vendor pricing against how often your spreadsheets change.
Supaflow reads the cached numeric or string result stored with a formula in the exported workbook. It does not recalculate formulas. If neither cached result is readable, the cell lands as null and the worksheet read continues.
The connector is folder-based. To isolate one spreadsheet, place it in its own Drive folder and point the source at that folder.
Yes. Supaflow's sync agent can run in your own VPC so spreadsheet content and destination traffic use your data plane. The control plane remains managed.
The Google Sheets source and Snowflake destination, plus other Supaflow connectors you can pair into a Snowflake pipeline.
Source connector overview — Sheets, CSV, TSV, and Excel (.xlsx) use the same connector.
Bulk file-drop use case: CSV, TSV, and Excel (.xlsx) from Drive into Snowflake.
Destination connector overview and capabilities.
Pair with Sheets when Salesforce reports are exported for collaboration.
Pair with Sheets for marketing reporting that mixes CRM and manual data.
Browse the full catalog of sources and destinations.
Setup for managed service accounts, OAuth, service-account keys, Google Sheets selection, and troubleshooting.
Connect your Snowflake warehouse, role requirements, type mapping, and sync semantics.
Compare managed connectors, manual loads, and custom pipelines, then follow the Supaflow setup walkthrough.
Every connector is included on every plan. Pay only for compute consumed (Supaflow Credits).
Every connector is included on every Supaflow plan — you pay only for the compute your pipelines consume. Schedule file-level incremental reads and review worksheet mappings before they load.