DatriseAI-first ETL

Salesloft Holistics

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

How Datrise loads Salesloft into Holistics

Datrise syncs Salesloft's cadence activity, conversation signals, and revenue workflow execution 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

Salesloft: Revenue workflow platform for cadences, conversations, and coaching signals.

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

How Salesloft entities map to Holistics

Salesloft entityHolistics objectNotes
cadence activitysalesloft_cadence_activitydate/time dimensions events
conversation signalssalesloft_conversation_signalsid PK · linked to salesloft_cadence_activity
revenue workflow executionsalesloft_revenue_workflow_executionid PK · linked to salesloft_cadence_activity

FAQ

How does Datrise handle Salesloft'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 Salesloft to Holistics sync stay up to date?

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

Related pipelines

Early access

Connect Salesloft 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.