DatriseAI-first ETL

Salesloft Azure Synapse

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

How Datrise loads Salesloft into Azure Synapse

Datrise syncs Salesloft's cadence activity, conversation signals, and revenue workflow execution into Azure Synapse as a typed table per source entity. Flexible or custom fields land in NVARCHAR(MAX) JSON columns, and timestamps such as created, updated, and status changes are typed as datetime2.

Sync is incremental: Datrise uses COPY into staging, then a MERGE on stable id, so re-runs update only what changed. Hash distribution on the join id with date partitioning on facts. Synapse dedicated pools reward good hash-distribution choices, so Datrise distributes on entity ids to avoid data-movement-heavy joins.

Ideal for Azure analytics estates feeding Power BI.

Endpoints

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

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Salesloft entities map to Azure Synapse

Salesloft entityAzure Synapse objectNotes
cadence activitysalesloft_cadence_activitydatetime2 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 Azure Synapse?

Flexible values are stored as NVARCHAR(MAX) JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Azure Synapse types.

How does the Salesloft to Azure Synapse sync stay up to date?

It runs incrementally — Datrise uses COPY into staging, then a MERGE on stable id.

Related pipelines

Early access

Connect Salesloft to Azure Synapse 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.