News API to Sisense Integration

How Datrise loads News API into Sisense

Datrise syncs News API's articles, sources, headlines, publication dates, categories, and search queries into Sisense as modeled tables for a Sisense ElastiCube (or live connection). Flexible or custom fields land in flattened columns for the cube, and timestamps such as created, updated, and status changes are typed as date/time fields.

Sync is incremental: Datrise uses incremental ElastiCube builds on changed rows, so re-runs update only what changed. Date-partitioned facts to speed cube builds. ElastiCube is an in-memory model, so Datrise lands incremental, build-friendly tables rather than forcing full rebuilds.

Ideal for embedded analytics on an in-memory engine.

Endpoints

News API: Aggregated news headlines across publishers.

Sisense: Analytics platform with elastic data models and embedded analytics.

How News API entities map to Sisense

News API entity	Sisense object	Notes
articles	`news_api_articles`	id PK · custom fields → flattened columns for the cube
sources	`news_api_sources`	id PK · linked to news_api_articles
headlines	`news_api_headlines`	id PK · linked to news_api_articles
publication dates	`news_api_publication_dates`	id PK · linked to news_api_articles

FAQ

How does Datrise handle News API's custom fields in Sisense?

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

How does the News API to Sisense sync stay up to date?

It runs incrementally — Datrise uses incremental ElastiCube builds on changed rows.

Related pipelines

Early access

Connect News API to Sisense 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.