Google Sheets
Productivity
Google Sheets data, published as Google Sheets publishes it. Ingest delivers this data to a data warehouse you own as one table, and updates it on the schedule you choose. There is no code to write and nothing to install.
What you get
| Table | Each row is |
|---|---|
spreadsheet_tabsspreadsheet_tabs | Every tab of each picked spreadsheet, each landing as its own table named after the spreadsheet and the tab (a tab called Q3 in a spreadsheet called Budget lands as budget_q3; a name that starts with a digit, like 2024 Plan, takes tab_ in front). Each table holds every row of its tab below the header, read whole on each run and replacing the table. A tab's first row is its header: each of its cells names a column, and a row with a value under a blank header fails that tab rather than land it unnamed. Google leaves out the empty cells at the end of a row, and those land as nulls. Values are the cells' underlying values, not their display format (a number formatted as currency lands as the number); dates, times and durations land as the text the sheet shows for them. A formula lands as its result. A tab added later lands on the next run; a renamed tab starts a new table, and a deleted or renamed tab's old table stays as last loaded. Chart sheets are skipped. |
How it works
- Choose Google Sheets. Connect your Google Sheets account once, from Ingest.
- Pick where it goes. BigQuery, Snowflake, Databricks, Redshift and 11 more, in an account you own.
- Pick a schedule. Daily is the default, and weekly and monthly are there too.
- Ingest runs it from then on. If a run fails, your dashboard shows which table and why.
Questions
- Do I need an account with Google Sheets?
- Yes. You connect your own Google Sheets account once, from Ingest, and the data comes from what that account can see.
- Which warehouses can Google Sheets data go to?
- Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, ObsessionDB, MySQL / generic SQL and Snowflake, in an account you own.
- How fresh is the data?
- As fresh as your schedule: daily by default, or weekly or monthly. Schedules as often as every 20 minutes are on the Enterprise plan.
- Will running it again create duplicate rows?
- No. Each run replaces the table, so it never holds two copies of the same row.
- Do I need to write code?
- No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.
For your data team: technical reference
Connector google_sheets, version 0.1.0, a REST source, status beta, authentication oauth2.
Vendor documentation: https://developers.google.com/workspace/sheets/api/reference/rest/v4/spreadsheets.values/batchGetByDataFilter
Configuration
| Key | Label | Type | Required |
|---|---|---|---|
spreadsheet_ids | Spreadsheets | string | yes |
Resources
| Resource | Status | Plan | Write | Primary key | Overrides |
|---|---|---|---|---|---|
spreadsheet_tabsEvery tab of each picked spreadsheet, each landing as its own table named after the spreadsheet and the tab (a tab called Q3 in a spreadsheet called Budget lands as budget_q3; a name that starts with a digit, like 2024 Plan, takes tab_ in front). Each table holds every row of its tab below the header, read whole on each run and replacing the table. A tab's first row is its header: each of its cells names a column, and a row with a value under a blank header fails that tab rather than land it unnamed. Google leaves out the empty cells at the end of a row, and those land as nulls. Values are the cells' underlying values, not their display format (a number formatted as currency lands as the number); dates, times and durations land as the text the sheet shows for them. A formula lands as its result. A tab added later lands on the next run; a renamed tab starts a new table, and a deleted or renamed tab's old table stays as last loaded. Chart sheets are skipped. | beta | full | replace | - | - |
Where this lands, and what else connects
Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, ObsessionDB, MySQL / generic SQL, Snowflake.
Other sources Ingest connects for SaaS teams: Asana, OpenAI (ChatGPT Enterprise), Clockify, Google Drive, Jira, Salesforce.
- How Ingest reads a REST source
- Ingest for SaaS teams
- The tables Ingest creates
- Every source Ingest connects
Get Google Sheets data into your warehouse
Last updated .