Salesloft

Read and write Salesloft people, accounts, notes and tasks, manage cadence memberships and read call and email activity.

Keep sales engagement data aligned with the CRM and product signals, and enrol qualified people into cadences from flows.

Build a flow with Salesloft Provider API documentation

Source actions

Destination actions

Data types

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

accounts

Create account
Destination
Not retried automatically
Creates an account. The domain must be unique on the team.
Get account
Source
One account by Salesloft ID.
List accounts
Source
Incremental
Accounts with stage, tier, owner and custom fields; filter by update time or domain.
Update account
Destination
Duplicate protected
Updates the mapped account fields; set archived to archive or restore.
Upsert account
Destination
Duplicate protected
Creates or updates an account matched on domain, crm_id or Salesloft ID.

cadence memberships

Add person to cadence
Destination
Not retried automatically
Adds one person to a cadence. Cadence steps (including automated emails) start for that person, so enable this only for explicit enrolment flows.
List cadence memberships
Source
Incremental
Which people are (or were) on which cadences.

cadences

List cadences
Source
Incremental
Cadences, optionally only those people can be added to.

calls

List calls
Source
Incremental
Logged calls with disposition, sentiment and duration.

custom fields

List custom fields
Source
Custom field definitions for people, companies and opportunities with value types.

emails

List emails
Source
Incremental
Sent and scheduled emails with tracking counts.

Get authenticated user
Source
The user that owns the API key.

notes

Create note
Destination
Not retried automatically
Adds a note to a person or account; it syncs to the CRM unless skipCrmSync is set.
List notes
Source
Incremental
Notes on people and accounts.
Update note
Destination
Duplicate protected
Updates note content. Changes are not synced to the CRM.

people

Create person
Destination
Not retried automatically
Creates a person. An email address, or a phone and last name, is required and must be unique on the team.
Get person
Source
One person by Salesloft ID.
List people
Source
Incremental
People with engagement counts and custom fields; filter by update time, email, account or cadence.
Update person
Destination
Duplicate protected
Updates the mapped person fields, including custom fields.

tasks

Create task
Destination
Duplicate protected
Creates a call, email or general task for a person. Uses Salesloft's idempotency_key.
List tasks
Source
Incremental
Call, email and general tasks; cadence step tasks are not included.
Update task
Destination
Duplicate protected
Updates a task, or completes it by setting currentState to completed.

users

List users
Source
Users visible to the key owner.

Authentication

Salesloft API key

Plans and access

Salesloft customers with API access; API keys are created per user. Requests act as the key owner and are limited to the scopes chosen for the key.

Test environment

Salesloft provides sandbox teams to partners and customers on request.

Rate limits

600 cost points per minute per team; high page numbers cost more; HTTP 429 with Retry-After.

Provider events

Salesloft webhook subscriptions for people, cadence membership, call, email and task events. Nexra event triggers are not yet available; flows run on demand or on a schedule.

Before you build a flow

Array filters accept one value per operation input in Nexra.
do_not_contact and contact_restrictions are only sent when mapped explicitly.
People, notes and cadence memberships have no idempotency key; uncertain creates are not repeated automatically. Tasks use Salesloft's idempotency_key.
The account create/update reference lists custom_fields as an array while reads return an object keyed by field name; Nexra sends the mapped value unchanged.
Activity reads (calls, emails) may require additional scopes; email subject and body are sensitive fields that need a specific scope.