Skip to main content

Salesloft Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow data flow that sends data to a Salesloft location.
salesloft_api.png

Salesloft

Create a Salesloft Destination​

  1. Click the + icon on the Nexset that will be sent to the Salesloft destination, and select the Send to Destination option from the menu.

  2. 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.

  3. In Nexla, Salesloft destinations can be created using pre-built endpoint templates, which expedite destination setup for common Salesloft endpoints. Each template is designed specifically for the corresponding Salesloft API endpoint, making destination configuration easy and efficient.
    • To configure this destination using a template, follow the instructions in Configure Using a Template.

    Salesloft destinations can also be configured manually, allowing you to send data to Salesloft endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template​

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.

  • To configure this destination using a template, 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.

Configure Manually​

Salesloft destinations can 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.

API Method​

  1. To manually configure this destination, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the Salesloft API from the Method pulldown menu. Common HTTP methods for Salesloft destinations include:

    • POST: For creating new records (accounts, people, activities, bulk jobs, cadence memberships)
    • PUT: For fully updating existing records (accounts, people)
    • PATCH: For partially updating existing records
    • DELETE: For removing records (accounts, people)

Data Format​

  1. Select the format in which the Nexset data will be sent to the Salesloft API from the Content Format pulldown menu. The Salesloft API accepts JSON format for all write operations. Nexla will automatically convert the data to the selected format for each API call.

API Endpoint URL​

  1. Enter the URL of the Salesloft API endpoint to which you want to send the Nexset data in the URL field. All Salesloft API v2 endpoints use the base URL https://api.salesloft.com/v2/, followed by the resource path.

    For update, upsert, or delete operations, include the record ID at the end of the URL. For example:

    • Creating a person: https://api.salesloft.com/v2/people
    • Updating a specific account: https://api.salesloft.com/v2/accounts/12345
    • Deleting a specific person: https://api.salesloft.com/v2/people/67890

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this destination, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2).

    You do not need to include the Authorization header or Content-Type header, as these are handled automatically by the Salesloft credential and Nexla's data format configuration.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this Salesloft destination, select the attributes from the Exclude Attributes pulldown menu.

  • Any number of attributes can be selected for exclusion, and all excluded attributes will be shown in the field. To remove an attribute from the list, click the X icon next to the attribute name.

Record Batching​

Optional

  1. If records should be sent to this destination in batched API calls, check the box next to Would you like to batch your records together? to enable record batching.

  2. Enter the maximum number of records that should be batched together in a single API call in the Batch Size field. By default, this value is set to 100.

  3. Select the algorithm that will be used to group records into batches from the Grouping Algorithm pulldown menu. The sample request shown in the panel on the right will be updated to reflect the current batching settings.

Batching is particularly useful when using the Salesloft bulk job data endpoint, which accepts multiple records per request. For standard create and update endpoints that accept a single record per request, batching should remain disabled.

Response Webhook​

Optional

Nexla can automatically send the response received from the Salesloft API after each call to a new Nexla webhook data source. This option allows you to keep track of the status of each API call and any additional information returned after each call, such as created record IDs or validation errors.

  • To enable this option, check the box next to Would you like to process the API response as a Nexla Webhook source?.

Sample Request Payload​

Sample request payloads containing a portion of the Nexset data that will be sent to the Salesloft API endpoint based on the current settings are shown in the Sample Payload panel on the right. These samples can be referenced to ensure that the destination and request settings are correctly configured.

  • Click on a sample request payload to expand it and view the complete payload content.
  • Sample payloads are automatically updated with each setting change, making it easy to verify that changes achieve the desired effect.

Endpoint Testing (Manual Configuration)​

After all endpoint settings have been configured, Nexla can send a test payload to the Salesloft API to ensure that the destination is configured correctly.

  1. To send a test payload, select the Test button at the top of the Sample Payload panel, and click on a listed sample payload to expand it.

  2. If any modifications to the sample payload are needed, make the necessary changes directly within the sample window.

  3. Click the Send Test Data button at the top of a sample payload to send the test payload to the Salesloft API using the current settings.

Save & Activate the Destination​

  • 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 begin sending 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.