DatriseAI-first ETL

Google Drive Yellowfin

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

How Datrise loads Google Drive into Yellowfin

Datrise syncs Google Drive's files, folders, permissions, and revision metadata into Yellowfin as warehouse tables Yellowfin builds views on. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. Yellowfin views reference columns by name, so Datrise lands stable, well-typed columns to keep reports valid.

Ideal for dashboards with automated data storytelling.

Endpoints

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

Yellowfin: BI suite with dashboards, automated insights, and data storytelling.

How Google Drive entities map to Yellowfin

Google Drive entityYellowfin 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 Yellowfin?

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 Yellowfin types.

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

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

Related pipelines

Early access

Connect Google Drive to Yellowfin 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.