Configure Salesloft as a data pipeline source ​

Set up Salesloft as a data pipeline source to extract and sync sales engagement records, such as people, accounts, cadences, and call and email activity, into your destination.

Use this guide to generate Salesloft credentials, set up a connection, configure your pipeline, add objects, review sync behavior, and understand known limitations.

Features supported ​

The following features are supported when you use Salesloft as a pipeline source:

• Cloud connectivity: Connect to Salesloft over HTTPS through a single global endpoint, https://api.salesloft.com. On-prem agents aren't required.
• Two authentication methods: Connect with an API key or an OAuth 2.0 (authorization code grant) connection. Refer to Supported connection types for more information.
• Full sync and incremental sync: Most objects sync incrementally using each record's updated_at timestamp. Objects that don't expose a filterable timestamp sync in full by default. Refer to Sync modes for more information.
• Object-level selection: Select Salesloft objects to sync as separate tables in your destination. Refer to Supported objects for the full list.
• Derived join key columns: For fields that reference another record, such as an Opportunities record's owner, the pipeline adds a scalar <field>_id column alongside the original JSON reference so you can join tables without parsing JSON. Refer to Primary keys and relationships for more information.
• GDPR-aware compliance fields: The People object's eu_resident and do_not_contact fields always sync unmasked so you can apply compliance-driven handling downstream. Refer to Sensitive data handling for more information.
• Schema drift detection and handling: Detect and apply schema changes automatically with Auto-sync new fields, or keep the schema fixed with Block new fields.
• Field-level data protection: Hash or replicate sensitive fields as is before the data reaches your destination.
• Configurable sync frequency: Schedule syncs on a time-based interval or with a cron expression. The minimum supported interval is 15 minutes.

Prerequisites ​

Connecting Salesloft as a data pipeline source requires:

• A Salesloft account
• Credentials for your chosen authentication method:
  • API key: A personal API key generated from your Salesloft account settings. Refer to Generate a Salesloft API key for setup steps.
  • OAuth 2.0 (authorization code grant): A Salesloft OAuth application registered with the Authorization Code grant type, and a Salesloft user account with permission to authorize the application. Refer to Register a Salesloft OAuth application for setup steps.

Register a Salesloft OAuth application ​

You must register an OAuth application in Salesloft and create a Workato custom OAuth profile before you create a connection to Salesloft using OAuth 2.0 (authorization code grant). Skip this section if you connect with an API key.

Generate a Salesloft API key ​

You must generate an API key in Salesloft before you create the connection in Workato. Skip this section if you connect with an OAuth 2.0 (authorization code grant) connection.

Recommended scopes ​

Grant the following scopes when you register your OAuth application or generate your API key. The scopes are identical for both methods.

Supported connection types ​

Salesloft data pipelines support two authentication methods:

• API key: Provide a personal API key generated from your Salesloft account. Refer to Generate a Salesloft API key for setup steps.
• OAuth 2.0 (authorization code grant): Authorize Workato using a custom OAuth profile built from a Salesloft OAuth application that you create. Salesloft data pipelines don't support a default Workato-managed app, so you must register your own OAuth application and create a custom OAuth profile before you connect. Refer to Register a Salesloft OAuth application for setup steps.

Salesloft doesn't support Basic authentication or SCIM tokens for data pipelines.

Connect to Salesloft ​

Complete the following steps to connect to Salesloft:

Configure the pipeline ​

Complete the following steps to configure Salesloft as your data pipeline source:

[minute] [hour] [day of month] [month] [day of week]

0 8 * * *

Supported objects ​

Salesloft data pipelines sync data from Salesloft REST API v2 resources. The following tables list the supported objects, grouped by category. Each object syncs as a separate table in your destination.

People and accounts ​

Opportunities ​

Cadences and sequencing ​

Sales activities ​

Call and email reference data ​

Users and teams ​

CRM sync ​

Workspace configuration ​

Sync modes ​

Salesloft data pipelines support full sync and incremental sync. The pipeline defaults each object to a sync mode, which you can change unless the object has no usable timestamp. Refer to Configure the pipeline for the per-object Sync mode setting.

Full sync ​

Full sync extracts all available records for an object on every run and updates your destination table to match. If a previously synced record no longer appears in a run, Workato flags it as deleted rather than removing it. Refer to Delete tracking for more information.

The first run of every object performs a full sync, starting from the date you set in the When first started, this pipeline should pick up records from field for objects that support it. The pipeline extracts all available records if you leave the field blank.

Objects whose Salesloft endpoint doesn't support filtering by an update timestamp always sync in full. Refer to the Supported objects tables to see the sync mode for each object.

Incremental sync ​

After the first sync completes, the pipeline extracts only records created or updated since the last successful run, using each record's updated_at timestamp as the cursor.

Refer to the Supported objects tables to see the sync mode for each object.

Delete tracking ​

For objects that sync in full, Workato compares each run against the destination table and flags a record with _workato_is_deleted = true if it no longer appears in Salesloft, rather than removing the row. For objects that sync incrementally, Workato can't detect deletions, because Salesloft doesn't expose deleted records to a read client. A deleted record remains in your destination with its last-synced values.

Meetings is the only object with a source-driven delete signal. Salesloft's API directly reports cancelled and deleted meetings, so the pipeline sets _workato_is_deleted from that signal instead of inferring it from a missing row. Refer to Synthetic columns for more information.

Accounts, Cadences, and EmailTemplates treat archival as a status change rather than a delete, so an archived record stays in your destination. Refer to the Supported objects tables to see delete tracking by object.

Schema and data type handling ​

The following considerations apply to schema and data types when you sync data from Salesloft:

Primary keys and relationships ​

Each destination table uses the Salesloft record id as its primary key, except OpportunityTag. Salesloft doesn't have a dedicated endpoint for OpportunityTag, so the pipeline derives one row per tag from the tags array embedded in each Opportunities record, using a composite key of opportunity_id and tag_name.

Relationships to other records sync as embedded JSON reference columns, such as account on People. The pipeline also adds a scalar <field>_id column derived from the same response alongside most of these reference columns, such as account_id on People. Both columns sync independently, so you can select only the scalar ID column to use as a join key and deselect the full JSON reference to reduce storage, or keep both.

Custom fields ​

Salesloft lets customers define custom fields on People, Accounts, and Opportunities. These sync as a single custom_fields JSON string column rather than as individual columns, because the set of custom fields varies by Salesloft workspace. Refer to the CustomFields object for the custom field definitions in your workspace.

Tags ​

The tags field on People and Accounts returns a plain JSON array of tag name strings. These values can't be joined to the Tags object by a foreign key, because Salesloft doesn't return a tag ID reference on People or Accounts.

Timestamps ​

Salesloft timestamps sync as timestamp with time zone values and preserve the source's ISO 8601 UTC format.

Nested fields ​

Fields that contain nested objects, such as an Emails record's engagement counts, sync as JSON strings in a single column.

Call recordings ​

Each entry in the recordings array on Calls includes a url field that points to a time-limited, presigned URL for the call recording audio. The pipeline syncs this URL as metadata only and doesn't fetch or store the audio content.

Synthetic columns ​

Workato adds the following synthetic column to the destination table of every object that syncs in full:

Sensitive data handling ​

Salesloft objects can contain significant personally identifiable information (PII). The following objects commonly contain sensitive fields:

Use the Hash option in field-level data protection during pipeline configuration to protect PII before it reaches your destination. Refer to the Configure the pipeline steps for more information.

Limitations ​

The following limitations apply when you use Salesloft as a data pipeline source:

Deleted records on incremental objects ​

The pipeline can't detect deletions for objects that sync incrementally, because Salesloft doesn't expose deleted records to a read client. A record deleted in Salesloft remains in your destination with its last-synced values until you run a full sync of that object. Refer to Delete tracking for the objects this affects.

Meetings availability depends on your Salesloft plan ​

The Meetings object isn't available on every Salesloft plan. If your plan doesn't include Meetings API access, the pipeline reports a permission error for Meetings but continues syncing your other selected objects.

Email content requires additional permissions ​

Syncing the subject, body, and error_message fields on Emails requires both the email_contents and email_bodies scopes, whether you connect with an OAuth application or an API key. A connection missing either scope fails to sync the entire Emails object rather than omitting those fields silently.

Minimum sync frequency ​

The minimum supported sync interval is 15 minutes. You can't trigger syncs more frequently than this.