Skip to main content
Telara

Integrations / Salesloft

Salesloft logo

Salesloft

Salesloft sales engagement for people, accounts, cadences, cadence memberships, calls, tasks, and sales activity.

OAuth 2.0
Indexes
Actions
Events

What Telara does

Capability matrix

Before you connect

Prerequisites

A Salesloft team you can administer.
Team admin (or a role that can approve connected apps). Members cannot finish this setup.

Vendor setup

Get the credential

1
Click Connect in Telara
Settings → Integrations → Salesloft. Telara sends you to Salesloft. You do not register a Salesloft OAuth app.
2
Approve access
Sign in as the team admin. On the consent screen, allow Telara to read the people, cadences, and activities this page lists. Click Allow.
3
Return to Telara
Salesloft redirects you back. Finish Connect under Settings → Integrations if it is not already marked connected.

In Telara

Connect in Telara

OAuth 2.0

Salesloft OAuth connector. Endpoint access depends on connector permissions and team visibility.

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

Knowledge

What gets indexed

ResourceCoverage
PersonPartial — not every record the vendor holds is synced
CadencePartial — not every record the vendor holds is synced

Sync

Freshness & sync

ResourceLagDeletions
PersonUp to 1 dayRemoved records disappear on the next full sync
CadenceUp to 1 dayRemoved records disappear on the next full sync

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

Excluded from semantic search: Person, Cadence.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

Team visibility in Salesloft is the usual reason a cadence list looks empty — the authorizing user cannot see those cadences.
Connecting a personal sandbox does not cover the production team.