DatriseAI-first ETL

New York Times to Domo Integration

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

How Datrise loads New York Times into Domo

Datrise syncs New York Times's articles, sections, headlines, bylines, publication dates, and keywords into Domo as datasets in Domo's cloud store via connector. Flexible or custom fields land in flattened columns for Magic ETL, and timestamps such as created, updated, and status changes are typed as date/time columns.

Sync is incremental: Datrise uses partitioned dataset updates rather than full replaces, so re-runs update only what changed. Domo dataset partitions keyed on load date. Domo stores its own copy of data, so Datrise sends incremental partitions to avoid re-uploading whole datasets.

Ideal for all-in-one cloud BI with built-in ETL.

Endpoints

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

Domo: Cloud BI platform combining data integration and executive dashboards.

How New York Times entities map to Domo

New York Times entityDomo objectNotes
articlesnew_york_times_articlesid PK · custom fields → flattened columns for Magic ETL
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 Domo?

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

How does the New York Times to Domo sync stay up to date?

It runs incrementally — Datrise uses partitioned dataset updates rather than full replaces.

Related pipelines

Early access

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