Salesloft is a leading revenue and sales engagement platform that helps sales teams manage the full customer engagement lifecycle. It provides multi-step cadences (automated outreach), account and contact management, call and email tracking, and performance analytics. Its API exposes accounts, people, cadences, activities, opportunities, and bulk operations for integrating sales data with other systems.
Power end-to-end data operations for your Salesloft API with Nexla. Our bi-directional Salesloft connector is purpose-built for Salesloft, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Salesloft or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Salesloft workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
To connect Nexla to Salesloft, you must first create an OAuth application in your Salesloft account. Salesloft uses OAuth 2.0 (3-legged authorization code flow) to grant Nexla access to your data on behalf of your users.
Navigate to your account settings by clicking your profile icon in the top-right corner, then select Settings.
In the left sidebar, locate the Integrations section and click API or navigate to Your Applications > OAuth Applications.
Click Create New to begin creating a new OAuth application.
Fill in the application details:
Application Name: Enter a descriptive name for the integration, such as Nexla Integration.
Redirect URI: Enter https://app.nexla.io/oauth/callback as the redirect URI. This is the URL Salesloft will redirect users to after they authorize access.
Scopes: Select the scopes (permissions) appropriate for your use case. Common scopes include:
After the application is created, you will be shown your Application ID (Client ID) and Secret (Client Secret). Copy both values immediately and store them securely, as the secret may not be displayed again.
For more information about available OAuth scopes and application configuration, see the Salesloft OAuth documentation.
The Salesloft REST API base URL is https://api.salesloft.com/v2. This is the default value used when configuring Nexla credentials and generally does not need to be changed.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Salesloft uses a 3-legged OAuth 2.0 flow, where users authorize Nexla to access Salesloft data by logging in to Salesloft and granting permission. Nexla then exchanges the authorization code for an access token automatically. Enter the Client ID obtained from your Salesloft OAuth application in the Client ID field. This is the unique public identifier assigned to your Salesloft OAuth application.
Enter the Client Secret from your Salesloft OAuth application in the Client Secret field. This private key authenticates Nexla's requests to Salesloft when exchanging authorization codes for access tokens.
Important
The Client Secret should be kept confidential and never shared. It authenticates your application with Salesloft during the token exchange process.
In the Access Scope field, enter a space-separated list of OAuth scopes that match the permissions your application requires. For example: accounts:read accounts:write people:read cadences:read activities:read. The scopes you enter must match or be a subset of the scopes configured in your Salesloft OAuth application.
Salesloft uses scopes to control access to specific data and actions. Request only the scopes necessary for your integration. For a full list of available scopes, see the Salesloft Scopes documentation.
The API Base URL field defaults to https://api.salesloft.com/v2, which is the standard Salesloft REST API base URL. This value should remain unchanged for most integrations.
After entering the required settings, click the Authorize button to begin the OAuth authorization flow. You will be redirected to the Salesloft login page.
Sign in to Salesloft with your account credentials and review the requested permissions. Click Authorize to grant Nexla access to your Salesloft account.
After authorization is complete, you will be redirected back to Nexla and the credential will be populated with an access token automatically.
Salesloft access tokens expire periodically. Nexla automatically handles token refresh using the refresh token obtained during the initial authorization, so you do not need to manually re-authorize the credential under normal circumstances.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Salesloft connector tile, then select the credential that will be used to connect to your Salesloft instance, and click Next; or, create a new Salesloft credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Salesloft endpoints. Each template is designed specifically for the corresponding Salesloft API endpoint, making data source setup easy and efficient. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.
Get Current Team
Retrieves information about the current Salesloft team, including team settings, configuration, and membership details. Use this endpoint when you need an overview of your Salesloft team's structure and settings.
No additional configuration parameters are required for this endpoint. Once the template is selected, Nexla will automatically retrieve the current team information for the authenticated account.
The response includes top-level team metadata such as the team name, settings, and associated configuration. This data is returned as a single record rather than a paginated list.
This endpoint returns data for the team associated with the authenticated credential. Ensure that the selected credential belongs to the team whose data you wish to retrieve. For more details, see the Salesloft API documentation.
List Account Stages
Retrieves all account stages configured in your Salesloft instance. Account stages define the lifecycle status of accounts (e.g., Prospect, Qualified, Customer) and are used to categorize and track accounts through your sales process.
No additional configuration parameters are required for this endpoint. Nexla will automatically retrieve all account stages available in the authenticated Salesloft instance.
The results are returned as an array of account stage objects, each containing the stage name, ID, and associated metadata.
Account stages are managed in Salesloft under Settings > CRM > Account Stages. This endpoint is useful for building reports or enriching account data with stage information.
List Account Tiers
Retrieves all account tiers configured in your Salesloft instance. Account tiers allow you to segment and prioritize accounts by their strategic importance or revenue potential (e.g., Tier 1, Tier 2, Tier 3).
No additional configuration parameters are required. Nexla will automatically retrieve all account tiers available in the authenticated Salesloft instance.
Each account tier record includes the tier name, ID, and associated configuration details.
Account tiers are a useful segmentation tool in account-based sales strategies. Use this endpoint to enrich account data or build dashboards that reflect account prioritization.
List Accounts
Retrieves a paginated list of all accounts in your Salesloft instance. Accounts represent companies or organizations being tracked in your sales process, including their contact information, stage, owner, and activity history.
No additional configuration parameters are required. Nexla will automatically paginate through all available accounts and retrieve the full list.
This endpoint uses offset-based pagination with up to 100 records per page. Nexla handles pagination automatically, so all accounts will be retrieved in a single data flow run.
Each account record includes fields such as account name, domain, industry, owner, stage, tier, CRM ID, and timestamps for creation and last modification.
The Salesloft API applies rate limits on a team level. If your account list is very large, consider scheduling ingestion during off-peak hours to minimize the impact on other integrations sharing the same rate limit. For more information, see the Salesloft API Basics documentation.
Fetch an Account
Retrieves detailed information for a single Salesloft account identified by its unique Account ID. Use this endpoint when you need to fetch complete details for a specific account rather than listing all accounts.
Enter the unique identifier of the account you want to retrieve in the Account ID field. This is a required parameter.
The Account ID can be found by first using the List Accounts endpoint to retrieve all accounts and identify the ID of the desired account.
Alternatively, the Account ID can be obtained from your Salesloft UI by navigating to the account record and noting the ID in the URL (e.g., https://app.salesloft.com/accounts/{account_id}).
The response includes a single account object with all associated fields, including CRM data, contact counts, and engagement metrics.
Account IDs in Salesloft are integer values. Ensure the ID entered is valid and belongs to an account accessible by the authenticated credential.
List Actions
Retrieves a paginated list of all actions in your Salesloft instance. Actions represent tasks assigned to sales representatives as part of cadence steps, such as sending an email, making a phone call, or completing a LinkedIn outreach.
No additional configuration parameters are required. Nexla will automatically paginate through all available actions and retrieve the full list.
This endpoint uses offset-based pagination with up to 100 records per page. Nexla handles pagination automatically.
Each action record includes the action type, associated person, cadence step, due date, status, and assigned owner.
Actions are tied to cadence steps and represent the work items that sales reps must complete. Use this endpoint to track team productivity, cadence adherence, and task completion rates.
Get Action
Retrieves detailed information for a specific action identified by its unique Action ID. Use this endpoint when you need complete details about a particular task or cadence step action.
Enter the unique identifier of the action you want to retrieve in the Action ID field. This is a required parameter.
Action IDs can be obtained by first using the List Actions endpoint to retrieve all actions and identify the relevant ID.
The response includes a single action object with all associated fields, including type, status, person association, cadence step details, and timestamps.
List Past Activities
Retrieves a paginated list of historical activity records from your Salesloft account. Activity histories represent completed sales activities such as sent emails, completed calls, LinkedIn touchpoints, and other engagement events.
No additional configuration parameters are required. Nexla will automatically paginate through all activity history records and retrieve the full list.
This endpoint uses offset-based pagination with up to 100 records per page, and Nexla handles pagination automatically.
Each record includes the activity type, associated person, account, cadence, outcome, timestamp, and owner information.
Activity history data is valuable for sales analytics, coaching, and reporting. Use this endpoint to build dashboards that track engagement metrics, call outcomes, email reply rates, and rep productivity over time.
List Bulk Jobs
Retrieves a paginated list of bulk jobs in your Salesloft instance. Bulk jobs are used for large-scale import, update, or delete operations on people, accounts, or other records. Use this endpoint to monitor job status and track results.
No additional configuration parameters are required. Nexla will automatically paginate through all bulk jobs and retrieve the full list.
This endpoint uses offset-based pagination with up to 100 records per page.
Each bulk job record includes the job type, state (pending, processing, complete, failed), record counts, and timestamps.
Bulk jobs can be filtered by state (e.g., completed, failed) using query parameters when configuring a manual source. Use the List Bulk Job Results endpoint to retrieve the outcomes of a completed bulk job.
List Job Data for Bulk Job
Retrieves the job data records associated with a specific bulk job. Job data represents the individual records submitted for processing as part of a bulk import, update, or delete operation.
Enter the unique identifier of the bulk job whose data you want to retrieve in the Bulk Job ID field. This is a required parameter.
Bulk Job IDs can be obtained from the List Bulk Jobs endpoint.
This endpoint uses offset-based pagination with up to 100 records per page, and Nexla handles pagination automatically.
Each record includes the submitted data payload and any associated metadata for that job data entry.
List Bulk Job Results
Retrieves the results for a completed bulk job, including the outcome (success or failure) for each individual record submitted in the job. Use this endpoint to audit bulk operations and identify records that failed to process.
Enter the unique identifier of the completed bulk job in the Bulk Job ID field. This is a required parameter.
Bulk Job IDs can be obtained from the List Bulk Jobs endpoint. Ensure the job has reached a completed state before retrieving results.
This endpoint uses offset-based pagination with up to 100 records per page, and Nexla handles pagination automatically.
Each result record includes the record ID, processing status, any error messages, and associated metadata.
This endpoint is particularly useful for validating bulk import or update operations. Failed records will include error messages that can help diagnose data quality issues.
List Cadence Memberships
Retrieves a paginated list of all cadence memberships in your Salesloft instance. A cadence membership represents the enrollment of a person (contact) in a specific cadence (outreach sequence), and tracks their progress through the cadence steps.
No additional configuration parameters are required. Nexla will automatically paginate through all cadence memberships and retrieve the full list.
This endpoint uses offset-based pagination with up to 100 records per page.
Each membership record includes the associated person, cadence, current step, status (active, finished, removed), and timestamps.
Cadence membership data is valuable for tracking the engagement status of contacts across your outreach sequences. Use this data to build reports on cadence performance, contact engagement rates, and outreach effectiveness.
List Cadences
Retrieves a paginated list of all cadences in your Salesloft account. Cadences are multi-step outreach sequences that automate and guide sales representatives through a defined series of touchpoints—such as emails, calls, and social touches—to engage prospects effectively.
No additional configuration parameters are required. Nexla will automatically paginate through all available cadences and retrieve the full list.
This endpoint uses offset-based pagination with up to 100 records per page.
Each cadence record includes the cadence name, owner, team visibility, step count, active/archived status, and creation and modification timestamps.
Salesloft cadences are the core of sales engagement automation. Use this endpoint to analyze cadence usage, track which cadences are most active, and audit the cadence library across your team.
Fetch a Cadence
Retrieves detailed information for a specific cadence identified by its unique Cadence ID. Use this endpoint when you need complete details about a particular outreach sequence, including its steps and configuration.
Enter the unique identifier of the cadence you want to retrieve in the Cadence ID field. This is a required parameter.
Cadence IDs can be obtained from the List Cadences endpoint.
Alternatively, the Cadence ID appears in the URL when viewing a cadence in the Salesloft UI (e.g., https://app.salesloft.com/cadences/{cadence_id}).
The response includes the full cadence object with all steps, settings, and associated metadata.
List Calendar Events
Retrieves a paginated list of calendar events from your Salesloft account. Calendar events include meetings, calls, and other scheduled activities that have been synced with Salesloft's calendar integration.
No additional configuration parameters are required. Nexla will automatically paginate through all available calendar events and retrieve the full list.
This endpoint uses offset-based pagination with up to 100 records per page.
Each calendar event record includes the event title, start and end times, attendees, associated person and account, and event status.
Calendar events in Salesloft are synchronized from connected calendar providers (e.g., Google Calendar, Microsoft Outlook). Use this endpoint to track meeting activity, analyze meeting-to-opportunity conversion rates, or build scheduling reports.
List Call Data Records
Retrieves a paginated list of call data records from your Salesloft account. Call data records contain detailed telephony information for calls made through Salesloft Dialer, including call duration, recording URLs, disposition, and sentiment data.
No additional configuration parameters are required. Nexla will automatically paginate through all available call data records and retrieve the full list.
This endpoint uses offset-based pagination with up to 100 records per page.
Each record includes the caller, recipient, call duration, recording URL (if available), call disposition, call sentiment, associated person and account, and timestamps.
Call data records are valuable for sales coaching, performance analysis, and compliance auditing. If call recording is enabled in your Salesloft account, recording URLs will be included in the response. Access to recordings may require additional permissions.
Fetch a Call Data Record
Retrieves detailed information for a specific call data record identified by its unique ID. Use this endpoint when you need complete telephony details for a single call.
Enter the unique identifier of the call data record you want to retrieve in the Call Data Record ID field. This is a required parameter.
Call Data Record IDs can be obtained from the List Call Data Records endpoint.
The response includes a single call data record object with all telephony details, including duration, disposition, sentiment, recording URL, and associated person and account information.
List Opportunities
Retrieves a paginated list of all opportunities in your Salesloft account. Opportunities represent potential revenue-generating deals and can be managed directly within Salesloft or synchronized from a connected CRM system such as Salesforce.
No additional configuration parameters are required. Nexla will automatically paginate through all available opportunities and retrieve the full list.
This endpoint uses offset-based pagination with up to 100 records per page.
Each opportunity record includes the opportunity name, amount, stage, associated account and people, close date, owner, and CRM synchronization status.
Salesloft supports managing opportunities via API for teams without a configured CRM. For teams with a CRM integration (e.g., Salesforce), opportunity data is typically synchronized from the CRM. For more details, see the Salesloft Opportunity API guide.
Fetch an Opportunity
Retrieves detailed information for a specific opportunity identified by its unique Opportunity ID. Use this endpoint when you need complete details about a single deal, including its current stage, associated contacts, and revenue information.
Enter the unique identifier of the opportunity you want to retrieve in the Opportunity ID field. This is a required parameter.
Opportunity IDs can be obtained from the List Opportunities endpoint.
The response includes the full opportunity object with all associated fields including deal value, pipeline stage, close date, account association, and owner details.
List Pending Emails
Retrieves a paginated list of pending emails in your Salesloft account. Pending emails are scheduled outreach emails that have been queued for sending as part of a cadence step but have not yet been delivered.
No additional configuration parameters are required. Nexla will automatically paginate through all pending emails and retrieve the full list.
This endpoint uses offset-based pagination with up to 100 records per page.
Each pending email record includes the recipient, sender, email subject, scheduled send time, associated cadence step, and status.
Use this endpoint to audit the email queue, identify bottlenecks in email delivery, or build monitoring workflows that alert when emails remain pending beyond a defined threshold.
List People
Retrieves a paginated list of all people (contacts) in your Salesloft account. People represent individual contacts that your sales team is engaging with, and each person record contains their contact details, associated account, cadence memberships, and engagement history.
No additional configuration parameters are required. Nexla will automatically paginate through all people records and retrieve the full list.
This endpoint uses offset-based pagination with up to 100 records per page.
Each person record includes fields such as first and last name, email address, phone number, title, associated account, owner, CRM ID, and engagement timestamps.
The People endpoint is one of the most frequently used in Salesloft integrations. It provides the foundation for contact synchronization workflows, engagement reporting, and CRM enrichment pipelines. For large contact databases, consider scheduling regular incremental syncs to keep your downstream systems current.
List Users
Retrieves a paginated list of all users in your Salesloft account. Users represent the members of your sales team who have access to the Salesloft platform, including their roles, permissions, and profile information.
No additional configuration parameters are required. Nexla will automatically paginate through all users and retrieve the full list.
This endpoint uses offset-based pagination with up to 100 records per page.
Each user record includes the user's name, email address, role, team membership, active status, and associated settings.
This endpoint is useful for user management reporting, access auditing, and enriching activity or account data with sales rep information. Only users with appropriate Salesloft permissions will be visible via the authenticated credential's access scope.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Salesloft data sources can also be manually configured to ingest data from any valid Salesloft REST API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom query parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
All Salesloft API v2 endpoints use the base URL https://api.salesloft.com/v2/, followed by the resource path (e.g., https://api.salesloft.com/v2/people, https://api.salesloft.com/v2/accounts, https://api.salesloft.com/v2/cadences). Salesloft list responses wrap records in a top-level data array—set the path to data to $.data[*] for list endpoints, or $ for single-object endpoints such as /team. Pagination and record-count metadata is available at $.metadata. The Salesloft API enforces rate limits at the team level, shared across all integrations and users on the team, so schedule high-volume flows during off-peak hours. You do not need to include the Authorization header, as it is handled automatically by the Salesloft credential. For more details, see the Salesloft API Basics documentation.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Salesloft data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the Salesloft destination, and select the Send to Destination option from the menu. Select the Salesloft connector from the list of available destination connectors, then select the credential that will be used to connect to your Salesloft organization, and click Next; or, create a new Salesloft credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Salesloft endpoints. Each template is designed specifically for the corresponding Salesloft API endpoint, making destination setup easy and efficient. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Upsert an Account
Creates or updates a Salesloft account based on a provided identifier and account details. This endpoint uses Salesloft's upsert logic to either insert a new account or update an existing one if a matching record is found, preventing duplicate account creation.
No additional template-level configuration parameters are required for this endpoint. The account data to be upserted should be provided as a JSON object in the Nexset, and Nexla will send each record as a POST request to the Salesloft account upserts API.
The request body should include the fields you want to create or update. Common fields include:
name (required) — The name of the account (company name).
domain — The company's website domain (e.g., example.com), used by Salesloft to match and deduplicate accounts.
crm_id — The CRM record ID for this account (e.g., Salesforce Account ID), used to link the account to its CRM record.
owner_id — The Salesloft user ID of the account owner.
industry — The industry classification for the account.
Salesloft matches accounts for upsert using the domain field. If an account with the same domain already exists, its fields will be updated with the values provided in the request. If no match is found, a new account will be created.
For a complete list of supported account fields and their formats, see the Salesloft API documentation. Ensure that the Nexset schema maps field names to the correct Salesloft account field names before sending data to this endpoint.
Submit Account and People Redaction Request
Submits a data redaction request for a Salesloft account and its associated people records. Redaction permanently removes personally identifiable information (PII) from Salesloft in compliance with data privacy regulations such as GDPR and CCPA.
No additional template-level configuration parameters are required. Each Nexset record should contain the account identifier and any additional fields required by the Salesloft redaction API.
The request body should include the identifier of the account to be redacted. Salesloft will remove the account's PII and the PII of all associated people records upon processing the request.
:::warning Important
Redaction requests are irreversible. Once submitted, the PII associated with the specified account and people will be permanently removed from Salesloft. Ensure that all redaction requests are reviewed and authorized before sending data to this endpoint.
:::
Use this endpoint as part of a GDPR or CCPA compliance workflow to process data deletion requests received from customers. For more information about Salesloft's data privacy controls, refer to the Salesloft API documentation.
Create an Account
Creates a new account in Salesloft with the provided name and domain. Use this endpoint when you want to add new company records to Salesloft from an external data source, such as a CRM export, marketing database, or enrichment tool.
No additional template-level configuration parameters are required. Each Nexset record should contain the fields for the account to be created.
Required and commonly used fields include:
name (required) — The company name for the new account.
domain — The company's website domain. Salesloft uses the domain to identify and deduplicate accounts.
owner_id — The Salesloft user ID of the account owner.
industry — Industry classification for the account.
account_stage_id — The ID of the account stage to assign to the new account.
account_tier_id — The ID of the account tier to assign.
If an account with the same domain already exists in Salesloft, the API will return an error. Use the Upsert an Account endpoint instead if you need to handle both create and update scenarios.
Before sending records to this endpoint, verify that account names and domains are correctly formatted. Duplicate domain values may cause API errors. Consider using the Upsert an Account template instead for workflows that may encounter existing accounts.
Update an Existing Account
Updates the details of an existing Salesloft account identified by its Account ID. Use this endpoint to synchronize account data from an external system (such as a CRM) into Salesloft, updating fields like account name, domain, stage, tier, or owner.
Enter the unique identifier of the account to update in the Account ID field. This is a required parameter that identifies which Salesloft account record will be modified.
Account IDs can be obtained from the List Accounts data source endpoint or from the account URL in the Salesloft UI.
The Account ID can also be passed dynamically as a field in the Nexset data by mapping the appropriate column to the Account ID parameter.
The request body should contain only the fields you wish to update. Fields not included in the request will retain their existing values in Salesloft.
This endpoint uses HTTP PUT, which replaces the specified fields with the values provided. Ensure that all required fields are included in the request payload to avoid unintentionally clearing field values.
Delete an Account
Deletes a Salesloft account identified by its Account ID. Use this endpoint to remove accounts that are no longer needed or to process bulk account deletion as part of a data lifecycle management workflow.
Enter the unique identifier of the account to delete in the Account ID field. This is a required parameter.
Account IDs can be obtained from the List Accounts data source endpoint.
The Account ID can also be passed dynamically as a field in the Nexset by mapping the appropriate column to the Account ID parameter.
:::warning Important
Account deletion in Salesloft is permanent and cannot be undone. Deleting an account will also remove associated data such as cadence memberships and activity history linked to that account. Verify that the correct Account IDs are being sent before activating this destination.
:::
Create Activity
Creates a new activity record in Salesloft representing a sales interaction such as a call, email, or other engagement event. Use this endpoint to log activities from external systems (e.g., phone systems, email platforms) into Salesloft, keeping your engagement records centralized and accurate.
No additional template-level configuration parameters are required. Each Nexset record should contain the fields for the activity to be created.
Commonly used fields include:
activity_type — The type of activity (e.g., call, email, other).
person_id — The Salesloft person (contact) ID associated with the activity.
account_id — The Salesloft account ID associated with the activity.
user_id — The Salesloft user ID of the rep who performed the activity.
occurred_at — The timestamp of when the activity occurred (ISO 8601 format).
note — An optional note or description of the activity.
Activities logged via the API will appear in the Salesloft activity feed and contribute to engagement reporting. Ensure that person and account IDs are valid Salesloft identifiers before sending records to this endpoint.
Create Bulk Job
Creates a bulk job in Salesloft for processing large numbers of records in a single operation. Bulk jobs support import, update, and delete operations on people, accounts, and other Salesloft objects. Use this endpoint to initiate large-scale data operations without making individual API calls for each record.
No additional template-level configuration parameters are required. Each Nexset record should contain the bulk job definition, including the job type and target resource.
The request body should include:
type — The type of bulk operation (e.g., import, update, delete).
target_type — The resource type to process (e.g., person, account).
After creating the bulk job, use the Create Job Data for Bulk Job endpoint to add records to the job, and then monitor its progress using the List Bulk Jobs source endpoint.
Bulk jobs are processed asynchronously by Salesloft. After creating a job and submitting job data, allow time for processing to complete before querying results using the List Bulk Job Results source endpoint.
Create Job Data for Bulk Job
Adds individual data records to an existing bulk job for processing. This endpoint is used after creating a bulk job with the Create Bulk Job endpoint to populate the job with the records to be imported, updated, or deleted.
Enter the unique identifier of the bulk job to which data will be added in the Bulk Job ID field. This is a required parameter.
The Bulk Job ID is returned in the response when creating a bulk job using the Create Bulk Job endpoint.
Existing Bulk Job IDs can also be retrieved using the List Bulk Jobs data source endpoint.
Each Nexset record represents a single job data entry to be submitted to the bulk job. The record structure should match the expected format for the bulk job's target resource type (e.g., person or account fields).
Salesloft imposes limits on the size of individual API requests for bulk job data. For very large datasets, consider splitting records across multiple Nexla flow runs or batching records appropriately using the Record Batching configuration option in the manual destination settings.
Create a Cadence Membership
Enrolls a person (contact) in a Salesloft cadence, creating a new cadence membership. Cadence memberships trigger the cadence outreach sequence for the enrolled person, initiating the series of steps (emails, calls, tasks) defined in the cadence. Use this endpoint to automate prospect enrollment in cadences based on data from external sources.
No additional template-level configuration parameters are required. Each Nexset record should contain the fields needed to create the cadence membership.
Required fields include:
person_id (required) — The Salesloft person ID of the contact to enroll in the cadence.
cadence_id (required) — The Salesloft cadence ID of the cadence in which the person will be enrolled.
user_id — The Salesloft user ID of the sales rep who will own this cadence membership (defaults to the authenticated user if not specified).
Once enrolled, the person will begin receiving the cadence outreach steps according to the cadence schedule. The cadence membership status will be set to active.
Enrolling a person who is already an active member of the specified cadence will result in an API error. Use the List Cadence Memberships source endpoint to verify existing memberships before enrolling new records. Person and cadence IDs must be valid Salesloft identifiers.
Once the selected endpoint template has been configured, select the Test button at the top of the Sample Payload panel, and click on a listed sample payload to expand it and send a test payload to the Salesloft API to verify that the destination is configured correctly before saving.
Salesloft destinations can also be manually configured to send data to any valid Salesloft REST API endpoint. Using manual configuration, you can also configure Nexla to automatically send the response received from the Salesloft API after each call to a new Nexla webhook data source. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
All Salesloft API v2 endpoints use the base URL https://api.salesloft.com/v2/, followed by the resource path, and accept JSON format for all write operations. For update, upsert, or delete operations, include the record ID at the end of the URL—for example, https://api.salesloft.com/v2/accounts/12345. You do not need to include the Authorization or Content-Type headers, as these are handled automatically by the Salesloft credential and Nexla's data format configuration.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Salesloft endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to Salesloft until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
