DatriseAI-first ETL

New York Times to Yellowfin Integration

AI-first ETL from New York Times into Yellowfin. Governed entities, incremental sync, typed landing tables.

How Datrise loads New York Times into Yellowfin

Datrise syncs New York Times's articles, sections, headlines, bylines, publication dates, and keywords 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

New York Times: Article archive and top-stories metadata.

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

How New York Times entities map to Yellowfin

New York Times entityYellowfin objectNotes
articlesnew_york_times_articlesid PK · custom fields → flattened columns
sectionsnew_york_times_sectionsid PK · linked to new_york_times_articles
headlinesnew_york_times_headlinesid PK · linked to new_york_times_articles
bylinesnew_york_times_bylinesid PK · linked to new_york_times_articles

FAQ

How does Datrise handle New York Times'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 New York Times to Yellowfin sync stay up to date?

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

Related pipelines

Early access

Connect New York Times 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.