Skip to main content

Sailthru 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 Sailthru location.
sailthru_cred_api.png

Sailthru

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

  2. Select the Sailthru connector from the list of available destination connectors. Then, select the credential that will be used to connect to the Sailthru account, and click Next; or, create a new Sailthru credential for use in this flow.

  3. Sailthru destinations can be manually configured to send data to any valid Sailthru API endpoint. Common use cases include creating or updating user profiles, managing list subscriptions, triggering transactional email sends, and updating user purchase or event data. You can also configure Nexla to automatically send the response received from the Sailthru API after each call to a new Nexla webhook data source.

    First, select the API method that will be used for calls to the Sailthru API from the Method pulldown menu. Common methods for Sailthru write operations include:

    • POST: For creating new records or updating existing ones (the primary method for most Sailthru write operations, including user profile updates, list subscriptions, and event tracking)
    • DELETE: For removing records, such as unsubscribing a user from a list or deleting a user profile

Data Format​

  1. Select the format in which the Nexset data will be sent to the Sailthru API from the Content Format pulldown menu. Nexla will automatically convert the data to the selected format for each API call. Sailthru's API accepts data in JSON format for most endpoints.

API Endpoint URL​

  1. Enter the URL of the Sailthru API endpoint to which you want to send the Nexset data in the URL field. This should be the complete URL, including the protocol (https://) and the endpoint path. Common Sailthru API endpoints for destination operations include:

    • https://api.sailthru.com/user — Create or update user profiles, including custom variables, purchase history, and list subscriptions. This endpoint supports POST requests for upserting user data based on email address or external ID.
    • https://api.sailthru.com/list — Add or remove users from subscriber lists. Use this endpoint to manage list subscriptions and segmentation.
    • https://api.sailthru.com/send — Trigger transactional email sends to individual users using a predefined template.
    • https://api.sailthru.com/purchase — Record purchase events for a user, which can be used to power personalized recommendations and behavioral targeting.
    • https://api.sailthru.com/event — Track custom events for users, such as product views, add-to-cart actions, or other behavioral signals.

    For complete details on all available Sailthru API endpoints, required parameters, and supported request formats, refer to the Sailthru API Documentation. Pay close attention to required fields for each endpoint, as Sailthru's API may return errors for missing or incorrectly formatted parameters.

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 authentication headers in this field. Sailthru's API key, secret, and request signature are handled automatically by Nexla using your Sailthru credential configuration.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this Sailthru destination, select the attributes from the Exclude Attributes pulldown menu. This is useful when your Nexset contains internal fields or metadata that should not be forwarded to the Sailthru API.

  • 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. Batching can improve throughput when sending large volumes of user profile updates or event data to Sailthru.

  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.

Response Webhook​

Optional

Nexla can automatically send the response received from the Sailthru API after each call to a new Nexla webhook data source. This option allows you to track the status of each API call and capture any additional information returned by Sailthru—such as user profile update confirmations, error messages, or job IDs for asynchronous operations.

  • 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 Sailthru 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​

After all endpoint settings have been configured, Nexla can send a test payload to the Sailthru 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 Sailthru 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 send the data to the configured Sailthru endpoint, open the destination resource menu, and select Activate.

    The Nexset data will not be sent to the Sailthru API until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.