DatriseAI-first ETL

Newsdata to Birst Integration

AI-first ETL from Newsdata into Birst. Governed entities, incremental sync, typed landing tables.

How Datrise loads Newsdata into Birst

Datrise syncs Newsdata's articles, sources, categories, countries, publication dates, and keywords into Birst as warehouse tables for Birst's automated star schema. 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 source tables Birst ingests, so re-runs update only what changed. Date-partitioned facts. Birst builds its own semantic layer, so Datrise lands conformed, well-keyed tables it can automate against.

Ideal for networked, governed enterprise BI.

Endpoints

Newsdata: News feed API with topic and country filters.

Birst: Cloud BI with networked analytics and enterprise semantic layers.

How Newsdata entities map to Birst

Newsdata entityBirst objectNotes
articlesnewsdata_articlesid PK · custom fields → flattened columns
sourcesnewsdata_sourcesid PK · linked to newsdata_articles
categoriesnewsdata_categoriesid PK · linked to newsdata_articles
countriesnewsdata_countriesid PK · linked to newsdata_articles

FAQ

How does Datrise handle Newsdata's custom fields in Birst?

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

How does the Newsdata to Birst sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the source tables Birst ingests.

Related pipelines

Early access

Connect Newsdata to Birst 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.