DatriseAI-first ETL

Freshcaller to Holistics Integration

AI-first ETL from Freshcaller into Holistics. Governed entities, incremental sync, typed landing tables.

How Datrise loads Freshcaller into Holistics

Datrise syncs Freshcaller's calls, agents, queues, phone numbers, call metrics, and recordings into Holistics as warehouse tables modeled in Holistics. Flexible or custom fields land in flattened columns for the modeling layer, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the modeled tables, so re-runs update only what changed. Date-partitioned facts for fast aggregates. Holistics models data as code on top of SQL, so Datrise lands stable column names to keep your models from drifting.

Ideal for as-code BI modeling on a warehouse.

Endpoints

Freshcaller: Cloud call center for support and sales.

Holistics: Self-service BI with modeling layers and scheduled report delivery.

How Freshcaller entities map to Holistics

Freshcaller entityHolistics objectNotes
callsfreshcaller_callsid PK · custom fields → flattened columns for the modeling layer
agentsfreshcaller_agentsid PK · linked to freshcaller_calls
queuesfreshcaller_queuesid PK · linked to freshcaller_calls
phone numbersfreshcaller_phone_numbersid PK · linked to freshcaller_calls

FAQ

How does Datrise handle Freshcaller's custom fields in Holistics?

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

How does the Freshcaller to Holistics sync stay up to date?

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

Related pipelines

Early access

Connect Freshcaller to Holistics 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.