Salesloft → Metabase
AI-first ETL from Salesloft into Metabase. Governed entities, incremental sync, typed landing tables.
How Datrise loads Salesloft into Metabase
Datrise syncs Salesloft's cadence activity, conversation signals, and revenue workflow execution into Metabase as clean SQL tables Metabase auto-discovers. Flexible or custom fields land in flattened columns for the question builder, and timestamps such as created, updated, and status changes are typed as temporal columns for trends.
Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for large questions. Metabase auto-scans schemas, so Datrise uses readable table and column names so the no-code UI stays self-explanatory.
Ideal for self-serve questions and dashboards for whole teams.
Endpoints
Salesloft: Revenue workflow platform for cadences, conversations, and coaching signals.
Metabase: Open-source analytics with questions, dashboards, and embedded insights.
How Salesloft entities map to Metabase
| Salesloft entity | Metabase object | Notes |
|---|---|---|
| cadence activity | salesloft_cadence_activity | temporal columns for trends 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 Metabase?
Flexible values are stored as flattened columns for the question builder, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Metabase types.
How does the Salesloft to Metabase sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for Salesloft
Early access
Connect Salesloft to Metabase 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.