Salesloft's iPaaS integrations can streamline data from third-party sources, automating workflows and ensuring smooth data transfer across systems. But, like any tool, setting it up correctly is key to getting the most out of the integration. 

Here are some best practices to create custom Plays using the iPaaS integrations: 

1. Start with Your "Why" – What Do You Want to Automate?

Before you dive into setting up an iPaaS integration, take a moment to think about the why. What do you want to achieve with this integration? Identifying your ‘why’ will help you determine which buyer signals to activate. 

Do you want to:

• Engage based on product usage and inventory data
• Connect custom lead scoring and AI models to seller action
• Notify Account owner of high priority tickets
• Follow-up when quotes are created, expiring….etc. 
• Trigger engagement workflows based on service start and completion
• Engage prospects based on marketing campaign enrollment and status

By getting clear on your goals, you can make sure your Salesloft plays are focused on the buyer signals that matter most. 🎯

2.  Ensure Your Data Source Has a Primary Identifier

To make sure that data flows seamlessly between your systems, it's essential to ensure that your data source has a primary identifier that matches with Salesloft. This identifier will allow Salesloft to correctly match and update existing records. The best identifiers to use are:

• CRM_ID: A global identifier that most sales tech stacks support.
• Salesloft ID: Ideal if your data source already contains accounts in Salesloft.
• Account Domain: Some Salesloft templates allow you to perform domain lookups, ensuring the most up-to-date account information is used.

3. Use the Upsert Action When Possible

The Upsert action is a powerful tool that minimizes API requests by either updating existing records or creating new ones if they don’t exist. When setting up your integration, use Upsert to ensure that you’re not making redundant API calls.

• Salesloft Upsert is particularly effective because it reduces the number of API requests made during data syncing, improving the overall efficiency of your integration.
• Things to Note: CRM Upsert currently supports Salesforce, so if you're using Salesforce as your data source, it's the most effective way to ensure smooth integration.

4. Ensure Your Data Source Contains Account Domain (for Account Creation)

If your workflows are aimed at updating accounts in Salesloft, it’s crucial that your data source includes an account domain. This will enable your iPaaS provider to match or create new accounts correctly when syncing data into Salesloft.

Without an account domain, there’s a risk of creating duplicate or mislinked accounts, which can cause issues with data consistency and workflow execution.

5. Test, Test, and Test Again

Testing is crucial! Test your play with dummy data before going live to ensure that everything syncs properly.

• ✅ Run test scenarios to make sure the data flows as expected.
• 🔍 Monitor your iPaaS provider for any issues, especially when making updates.

Remember: It's easier to catch issues early rather than deal with the aftermath!