Salesloft → Neon
AI-first ETL from Salesloft into Neon. Governed entities, incremental sync, typed landing tables.
How Datrise loads Salesloft into Neon
Datrise syncs Salesloft's cadence activity, conversation signals, and revenue workflow execution into Neon as a typed table per source entity. Flexible or custom fields land in jsonb columns, and timestamps such as created, updated, and status changes are typed as timestamptz.
Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE, so re-runs update only what changed. Optional declarative partitioning by load date. Neon separates compute from storage, so Datrise batches writes to keep autoscaling compute from cold-starting on every small change.
Ideal for serverless Postgres workloads that scale to zero between syncs.
Endpoints
Salesloft: Revenue workflow platform for cadences, conversations, and coaching signals.
Neon: Serverless Postgres destination with branching and autoscaling.
How Salesloft entities map to Neon
| Salesloft entity | Neon object | Notes |
|---|---|---|
| cadence activity | salesloft_cadence_activity | timestamptz events |
| conversation signals | salesloft_conversation_signals | id PK · linked to salesloft_cadence_activity |
| revenue workflow execution | salesloft_revenue_workflow_execution | id PK · linked to salesloft_cadence_activity |
FAQ
How does Datrise handle Salesloft's custom fields in Neon?
Flexible values are stored as jsonb columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Neon types.
How does the Salesloft to Neon sync stay up to date?
It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE.
Related pipelines
More destinations for Salesloft
Early access
Connect Salesloft to Neon 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.