Salesloft → Redash
AI-first ETL from Salesloft into Redash. Governed entities, incremental sync, typed landing tables.
How Datrise loads Salesloft into Redash
Datrise syncs Salesloft's cadence activity, conversation signals, and revenue workflow execution into Redash as SQL tables Redash queries and visualizes. Flexible or custom fields land in flattened columns for query results, and timestamps such as created, updated, and status changes are typed as temporal columns.
Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for scheduled queries. Redash caches query results on a schedule, so Datrise keeps tables incrementally fresh so cached dashboards reflect reality.
Ideal for lightweight, query-driven dashboards.
Endpoints
Salesloft: Revenue workflow platform for cadences, conversations, and coaching signals.
Redash: Open-source SQL client for queries, visualizations, and dashboards.
How Salesloft entities map to Redash
| Salesloft entity | Redash object | Notes |
|---|---|---|
| cadence activity | salesloft_cadence_activity | temporal columns 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 Redash?
Flexible values are stored as flattened columns for query results, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Redash types.
How does the Salesloft to Redash 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 Redash 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.