Source connector

Google Drive connector

Google Drive integration for databases, warehouses and BI tools

Cloud file storage often used for operational exports. Datrise captures Google Drive entities such as files, folders, permissions, and revision metadata, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Google Drive API v3 authenticates with OAuth 2.0, service account, incremental runs key on changes.list startPageToken, and Google Drive caps calls at 1,000,000 quota units per minute per project and 325,000 quota units per minute per user (files.list costs 100 units, files.get costs 5, media downloads cost 200).

Of the 4 objects, 4 sync as upserts keyed on the primary key and 0 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `google_drive_files`) with a schema derived from the Google Drive API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Google Drive pipeline page, and join the waitlist to get the Google Drive connector (Files) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Google Drive data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
files	google_drive_files	Upsert by primary key, incremental on updated-at
folders	google_drive_folders	Upsert by primary key, incremental on updated-at
permissions	google_drive_permissions	Upsert by primary key, incremental on updated-at
revision metadata	google_drive_revision_metadata	Upsert by primary key, incremental on updated-at

Google Drive API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Google Drive API v3
Authentication	OAuth 2.0, service account — OAuth 2.0 user consent or a service account (optionally with domain-wide delegation); read-only sync needs only the drive.readonly scope.
Pagination	token — files.list and changes.list return an opaque nextPageToken; there is no fixed page size, only a response-size ceiling.
Rate limit	1,000,000 quota units per minute per project and 325,000 quota units per minute per user (files.list costs 100 units, files.get costs 5, media downloads cost 200)
Incremental cursor	changes.list startPageToken — changes.getStartPageToken plus changes.list is the vendor-recommended diff mechanism; modifiedTime alone misses folder moves and permission-only changes.
Webhooks	Yes — Push notifications via files.watch / changes.watch channels
Bulk export	Yes — files.export (Google Docs Editors native formats only)
Deletes detectable	Yes — changes.list?includeRemoved=true flags removed items; trashed=true on files.list surfaces soft-deleted files still in the trash

Official API reference

What bites when replicating Google Drive

Drive API v3 quota is 1,000,000 quota units per minute per project and 325,000 per minute per user; a single `files.list` call already costs 100 units, so paginated list-heavy syncs exhaust the per-user quota quickly.
Incremental sync should start from `changes.getStartPageToken`, since the `modifiedTime` field alone does not reflect file moves between folders or permission-only changes.
`files.export` for native Google Docs/Sheets/Slides content caps exported output at 10 MB, so large native documents must be split or exported into a smaller format.
Shared drive items are silently excluded from `files.list` and `changes.list` unless `supportsAllDrives=true` and `includeItemsFromAllDrives=true` are both set on the request.

Compare this against every other documented API

Popular destinations for Google Drive

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Google Drive connector FAQ

What Google Drive data does the connector extract?: 4 objects: files, folders, permissions and revision metadata. Each lands in its own table with types preserved; history-style objects (0) load as append-only streams.
Is the Google Drive integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Google Drive data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Google Drive → destination pair has its own page with the object-to-table mapping.

Early access

Launch your Google Drive pipeline with guided onboarding

Join the waitlist to get priority access for Google Drive integrations with guided setup, schema-aware mapping, and production-grade incremental sync.