SalesLoft is a sales-engagement platform built around cadences and the calls and emails reps run through them. Connecting it as a data source through the Connectors library syncs that activity into your Alta workspace, where it becomes training data for Alta and a foundation for your metrics, dashboards, and Luna analysis. Once it's flowing, you can measure cadence performance, call connect rates, and rep activity — and ask Luna questions in plain English. SalesLoft connects with credentials.

Who this is for: Sales and RevOps teams who run cadences in SalesLoft and want that activity measured across Alta.

Before you start

Have your SalesLoft credentials ready, with access to the people and cadence data you want to sync.
Connect a source only once per workspace. If SalesLoft already shows Connected, edit the existing connection.

Connect SalesLoft

Open Connectors from the sidebar.
Find SalesLoft via the category tabs or the Search data sources box.
Click the SalesLoft card to open the Create connector screen.
Fill in the connection fields shown, then click Create.
Alta runs a connect test. If it fails you'll see The connect test has failed with SalesLoft's error — fix the field and retry.
The card then shows Connected and Data is syncing until the first sync finishes.

Choose which tables sync

Open the connection. SalesLoft brings in tables like people, cadences, and activities.
Use the Synced toggle in the SalesLoft tables section to control what's pulled in.
Turn off Show only synced tables to see everything available.

Key tables and fields synced

people — prospects: id, email_address, title, person_company_name, cadence_id, owner
cadences — sequences: id, name, created_at, step counts
emails — sends and engagement: id, status, sent_at, opened, clicked, replied
calls — dials and outcomes: id, sentiment, disposition, duration, created_at
users — reps: id, email, name

What you can ask this data

Once it's syncing, build it into metrics and dashboards or just ask Luna / Ask AI. For example:

"Which cadences have the highest reply rate?" — aggregates emails.replied grouped by cadences.name.
"How many people are in each cadence?" — counts people by cadence_id.
"What's call connect rate by rep?" — uses calls.disposition grouped by user.
"How many emails were sent last week?" — counts emails by sent_at.
"Which reps generate the most positive call sentiment?" — groups calls.sentiment by user.

Example use cases

Cadence scorecard. Reply and open rates per cadence to find what's working.
Activity dashboard. Calls and emails per rep per week, with connect rate.
Call-outcome analysis. Disposition and sentiment trends over time.
Engagement-to-pipeline. Combine with CRM data to connect cadence activity to created pipeline.

Keep it in sync

Sync status shows Last sync (Succeeded/Failed) and the Sync frequency.
Click Sync now to refresh immediately; it's disabled while a sync runs.
Use the overflow menu (⋯) to Disable, Enable, or Delete.

Tips and common pitfalls

Emails and calls hold the metrics. Sync those tables, not just people/cadences, to measure performance.
Sync only what you need to keep syncs fast.
A failed connect test is usually credentials. Re-check the field flagged by the inline error.
Deleting is permanent. Disable instead to pause.