Google Drive

Productivity

Ready to use

Google Drive data, published as Google Drive publishes it. Ingest delivers this data to a data warehouse you own as 6 tables, and updates it on the schedule you choose. There is no code to write and nothing to install.

What you get

TableEach row is
document_text
document_text
The full text of each Google Doc, as Markdown: one row per document, with `text` and `document_bytes`. `_ingest_parent_key` is the document's `id` in `files`, which has its name, folder, owners and dates. A meeting's notes and transcript that Google Meet saves to Drive are Google Docs and land here. A document is read once, and again only when it changes (a new `modified_time`). A blank document has a null `text` and an `unread_reason` saying it is empty. One the account may not download is not read. A document deleted from Drive keeps its row here, so join to `files` for the current list.
files
files
One row per file and folder in the folders you chose, however deep, or per file and folder the account can see (in My Drive, shared with it, or in a shared drive) when you chose everything: its `name`, `mime_type` (a Google Doc is application/vnd.google-apps.document, a folder application/vnd.google-apps.folder), `created_time`, `modified_time`, `web_view_link`, the folder it is in (`parents`), its owners and who last changed it. A file in the trash is listed with `trashed` true until Google empties it, and its text is not read. Read whole on every run, replacing the table, so a file that is deleted or unshared leaves it.
pdf_text
pdf_text
The text of each PDF stored in Drive: one row per PDF, with `text`, `pages` and `document_bytes`. `_ingest_parent_key` is the file's `id` in `files`. The pages of `text` are separated by a form feed, so page N is the N-th part when it is split on one. Read once, and again only when the file changes. A scanned or password-protected PDF has a null `text` and an `unread_reason` saying why. One the account may not download is not read.
presentation_text
presentation_text
The text of each Google Slides presentation: one row per presentation, with `text` and `document_bytes`. `_ingest_parent_key` is the presentation's `id` in `files`. Read once, and again only when it changes. One the account may not download is not read.
shared_drives
shared_drives
One row per shared drive the account belongs to: its `id`, `name` and `created_time`. A file in a shared drive names it in `files.drive_id`.
text_file_text
text_file_text
The text of each plain text, Markdown and HTML file stored in Drive: one row per file, with `text` and `document_bytes`. `_ingest_parent_key` is the file's `id` in `files`. An HTML file lands as the words on the page. Read once, and again only when the file changes. One the account may not download is not read.

How it works

  1. Choose Google Drive. Connect your Google Drive account once, from Ingest.
  2. Pick where it goes. BigQuery, Snowflake, Databricks, Redshift and 11 more, in an account you own.
  3. Pick a schedule. Daily is the default, and weekly and monthly are there too.
  4. 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 Drive?
Yes. You connect your own Google Drive account once, from Ingest, and the data comes from what that account can see.
Which warehouses can Google Drive 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 row is stored once, by its key: when a run reads a row that is already there, it replaces that copy instead of adding a second one.
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_drive, version 0.1.0, a REST source, status beta, authentication oauth2.

Vendor documentation: https://developers.google.com/workspace/drive/api/reference/rest/v3

Configuration

KeyLabelTypeRequired
folder_idsFoldersstringyes

Resources

ResourceStatusPlanWritePrimary keyOverrides
document_text
The full text of each Google Doc, as Markdown: one row per document, with `text` and `document_bytes`. `_ingest_parent_key` is the document's `id` in `files`, which has its name, folder, owners and dates. A meeting's notes and transcript that Google Meet saves to Drive are Google Docs and land here. A document is read once, and again only when it changes (a new `modified_time`). A blank document has a null `text` and an `unread_reason` saying it is empty. One the account may not download is not read. A document deleted from Drive keeps its row here, so join to `files` for the current list.
betaparent_childmerge_ingest_parent_key-
files
One row per file and folder in the folders you chose, however deep, or per file and folder the account can see (in My Drive, shared with it, or in a shared drive) when you chose everything: its `name`, `mime_type` (a Google Doc is application/vnd.google-apps.document, a folder application/vnd.google-apps.folder), `created_time`, `modified_time`, `web_view_link`, the folder it is in (`parents`), its owners and who last changed it. A file in the trash is listed with `trashed` true until Google empties it, and its text is not read. Read whole on every run, replacing the table, so a file that is deleted or unshared leaves it.
betafullreplaceid-
pdf_text
The text of each PDF stored in Drive: one row per PDF, with `text`, `pages` and `document_bytes`. `_ingest_parent_key` is the file's `id` in `files`. The pages of `text` are separated by a form feed, so page N is the N-th part when it is split on one. Read once, and again only when the file changes. A scanned or password-protected PDF has a null `text` and an `unread_reason` saying why. One the account may not download is not read.
betaparent_childmerge_ingest_parent_key-
presentation_text
The text of each Google Slides presentation: one row per presentation, with `text` and `document_bytes`. `_ingest_parent_key` is the presentation's `id` in `files`. Read once, and again only when it changes. One the account may not download is not read.
betaparent_childmerge_ingest_parent_key-
shared_drives
One row per shared drive the account belongs to: its `id`, `name` and `created_time`. A file in a shared drive names it in `files.drive_id`.
betafullreplaceid-
text_file_text
The text of each plain text, Markdown and HTML file stored in Drive: one row per file, with `text` and `document_bytes`. `_ingest_parent_key` is the file's `id` in `files`. An HTML file lands as the words on the page. Read once, and again only when the file changes. One the account may not download is not read.
betaparent_childmerge_ingest_parent_key-

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 Sheets, Jira, Salesforce.

Get Google Drive data into your warehouse

Last updated .