Google Webfonts → DuckDB
AI-first ETL from Google Webfonts into DuckDB. Governed entities, incremental sync, typed landing tables.
How Datrise loads Google Webfonts into DuckDB
Datrise syncs Google Webfonts's records, events, and configuration objects into DuckDB as a typed table per source entity in a DuckDB file. Flexible or custom fields land in JSON or STRUCT columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP WITH TIME ZONE.
Sync is incremental: Datrise uses rewrites changed entities into the local database (or Parquet) on each run, so re-runs update only what changed. Hive-partitioned Parquet by load date when exporting. DuckDB is single-writer and embedded, so Datrise produces a consistent file snapshot rather than concurrent streaming writes.
Ideal for local and notebook analytics without standing up a server.
Endpoints
Google Webfonts: SaaS or API data source for analytics and warehouse sync.
DuckDB: In-process analytics database for fast local OLAP.
How Google Webfonts entities map to DuckDB
| Google Webfonts entity | DuckDB object | Notes |
|---|---|---|
| records | google_webfonts_records | id PK · custom fields → JSON or STRUCT columns |
| events | google_webfonts_events | TIMESTAMP WITH TIME ZONE events |
| configuration objects | google_webfonts_configuration_objects | id PK · linked to google_webfonts_records |
FAQ
How does Datrise handle Google Webfonts's custom fields in DuckDB?
Flexible values are stored as JSON or STRUCT columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native DuckDB types.
How does the Google Webfonts to DuckDB sync stay up to date?
It runs incrementally — Datrise uses rewrites changed entities into the local database (or Parquet) on each run.
Related pipelines
More destinations for Google Webfonts
- Google Webfonts → Amazon Athena
- Google Webfonts → Amazon S3 Data Lake
- Google Webfonts → Azure Data Lake Storage
- Google Webfonts → Azure Synapse
- Google Webfonts → Spreadsheets
- Google Webfonts → Airtable
- Google Webfonts → CSV Files
- Google Webfonts → MongoDB
- Google Webfonts → Supabase
- Google Webfonts → Neon
- Google Webfonts → PlanetScale
- Google Webfonts → Amazon DynamoDB
Early access
Connect Google Webfonts to DuckDB 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.