DatriseAI-first ETL

Newsdata to Redash Integration

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

How Datrise loads Newsdata into Redash

Datrise syncs Newsdata's articles, sources, categories, countries, publication dates, and keywords into Redash as SQL tables Redash queries and visualizes. Flexible or custom fields land in flattened columns for query results, and timestamps such as created, updated, and status changes are typed as temporal columns.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for scheduled queries. Redash caches query results on a schedule, so Datrise keeps tables incrementally fresh so cached dashboards reflect reality.

Ideal for lightweight, query-driven dashboards.

Endpoints

Newsdata: News feed API with topic and country filters.

Redash: Open-source SQL client for queries, visualizations, and dashboards.

How Newsdata entities map to Redash

Newsdata entityRedash objectNotes
articlesnewsdata_articlesid PK · custom fields → flattened columns for query results
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 Redash?

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

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

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

Related pipelines

Early access

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