DatriseAI-first ETL

Salesloft Airtable

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

How Datrise loads Salesloft into Airtable

Datrise syncs Salesloft's cadence activity, conversation signals, and revenue workflow execution into Airtable as a table per source entity in your base. Flexible or custom fields land in long-text JSON or linked records for nested data, and timestamps such as created, updated, and status changes are typed as date/dateTime fields.

Sync is incremental: Datrise uses upserts records matched on a stable id field, so re-runs update only what changed. Airtable enforces per-base record and API rate limits, so Datrise batches writes and lands a focused field set.

Ideal for operational workflows and light CRM views in Airtable.

Endpoints

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

Airtable: Relational spreadsheet destination for ops and go-to-market teams.

How Salesloft entities map to Airtable

Salesloft entityAirtable objectNotes
cadence activitysalesloft_cadence_activitydate/dateTime fields 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 Airtable?

Flexible values are stored as long-text JSON or linked records for nested data, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Airtable types.

How does the Salesloft to Airtable sync stay up to date?

It runs incrementally — Datrise uses upserts records matched on a stable id field.

Related pipelines

Early access

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