Skip to main content

Introduction

This guide will provide you with the necessary steps to begin using your IPaaS solution to register object updates as Salesloft Signals. With Salesloft’s no-code framework in Plays, Salesloft users can leverage data from various systems, through IPaaS, to trigger automated workflows and create tasks for their sales team. This will allow you to orchestrate actions and drive outcomes based on real-time data from across your tech stack.

IPaaS Scheme

Important Notes​

  • Most of these steps will happen in your IPaAS solution
  • Salesloft Plays will assign Tasks to sellers based on changes to the data attributes you push into the platform.

Supported Users​

  • Any Salesloft customer with an existing, supported IPaaS solution
  • This article specifically focuses on existing integrations with IPaaS platforms like Tray.ai, Workato, and Zapier, but the solution is not limited to those solutions.

Use Cases​

In the examples following this document, we will primarily focus on data that does not live in your CRM. Data in your CRM can flow into Rhythm without IPaaS if attributes are mapped in Salesloft. The articles in this guide will highlight two sources:

  1. External Databases
  2. Product Adoption/Usage Sources (API data source)

However, you may use any intent, scores, or attributes related to Accounts to drive actions.

High-Level Steps​

  1. Identify a data attribute from the external system you’d want to use as a signal
  2. Create a custom field in Salesloft for that attribute
  3. Use a Salesloft identifier to find the corresponding Salesloft object (e.g., Account)
  4. Update/Upsert that record and include the custom fields, tags, or other corresponding data points.
  5. Set up a Salesloft Play to trigger whenever data changes on that field

Best Practices​

  • Ensure that your data source or data table contains a primary identifier that would exist in Salesloft. The best identifiers are as follows:
    • CRM_ID - Global identifier across most of the sales tech stack
    • Salesloft ID - Great identifier if your source contains accounts that already exist in Salesloft.
    • Account domain - Some templates built by Salesloft contain a domain lookup option that uses the most recently updated account if multiple accounts are returned
  • Ensure that your data source contains an account domain if you want your workflows to Create Accounts in Salesloft.
  • Use Upsert Action when possible. The Salesloft Upsert action reduces the number of API requests in your IPaaS. Today, upserting using CRM is only supported for Salesforce.

Start with a template​

Use one of the provided templates to speed up development in your IPaaS. These templates should provide you with a production-ready framework that only requires your team-specific details.

API Concepts​

  • Upsert - an Upsert API function will update a record if it exists and create a record if it does not. The API request specifies an upsert_key (id, domain, or crm_id) for Accounts, and Salesloft will use this field to find the unique record in your Salesloft instance. The only crm_id supported today is SFDC.
  • Pagination - Some data sources can return multiple pages of data when being queried.
  • Custom Fields - Like most revenue orchestration platforms, Salesloft allows users to create custom fields for objects in-app and in the API. Custom fields are used to store values that don’t natively exist in our platform. The values in these fields will be used as signals. See the structure below
"custom_fields": {
    "Rhythm Adopter": true
}