DatriseAI-first ETL

Google Drive GoodData

AI-first ETL from Google Drive into GoodData. Governed entities, incremental sync, typed landing tables.

How Datrise loads Google Drive into GoodData

Datrise syncs Google Drive's files, folders, permissions, and revision metadata into GoodData as warehouse tables GoodData maps into its logical data model. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date dimensions.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. GoodData's LDM maps datasets by keys, so Datrise lands stable primary and foreign id columns to keep the model valid.

Ideal for embedded, multi-tenant analytics.

Endpoints

Google Drive: Cloud file storage often used for operational exports.

GoodData: Composable analytics platform with headless BI and embedded dashboards.

How Google Drive entities map to GoodData

Google Drive entityGoodData objectNotes
filesgoogle_drive_filesid PK · custom fields → flattened columns
foldersgoogle_drive_foldersid PK · linked to google_drive_files
permissionsgoogle_drive_permissionsid PK · linked to google_drive_files
revision metadatagoogle_drive_revision_metadataid PK · linked to google_drive_files

FAQ

How does Datrise handle Google Drive's custom fields in GoodData?

Flexible values are stored as flattened columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native GoodData types.

How does the Google Drive to GoodData sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the connected tables.

Related pipelines

Early access

Connect Google Drive to GoodData the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.