Plaid → DuckDB
AI-first ETL from Plaid into DuckDB. Governed entities, incremental sync, typed landing tables.
How Datrise loads Plaid into DuckDB
Datrise syncs Plaid'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
Plaid: SaaS or API data source for analytics and warehouse sync.
DuckDB: In-process analytics database for fast local OLAP.
How Plaid entities map to DuckDB
| Plaid entity | DuckDB object | Notes |
|---|---|---|
| records | plaid_records | id PK · custom fields → JSON or STRUCT columns |
| events | plaid_events | TIMESTAMP WITH TIME ZONE events |
| configuration objects | plaid_configuration_objects | id PK · linked to plaid_records |
FAQ
How does Datrise handle Plaid'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 Plaid 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 Plaid
Early access
Connect Plaid 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.