Question 1

Which Salesloft objects can I write to from Databricks?

Accepted Answer

Accounts, people and cadences, where writing to a cadence means adding people to it. The rest of Salesloft is source only, so activity data can be read into the lakehouse for reporting but not written back. Those three cover what teams want from this direction: accurate account and person records, and control over who gets worked and when.

Question 2

Does this work if our Databricks workspace runs on GCP?

Accepted Answer

For reading, yes. Source access works through the server hostname and HTTP path regardless of which cloud the workspace runs on, and authentication is cloud neutral too. The limitation is on the other side: destination staging is implemented for AWS and Azure only, so a GCP workspace can feed reverse ETL but cannot currently be a target for loading data in. Worth knowing if you were planning both directions.

Question 3

Can I add people to a cadence from a model?

Accepted Answer

Yes, and missing people are created for you. If someone selected for a cadence is not in Salesloft yet, they are created and then added, so there is no separate seeding step. That makes it practical to model a qualified list in the lakehouse and let enrolment happen as people meet the criteria rather than when somebody remembers to upload a file.

Question 4

Should the lakehouse create people in Salesloft?

Accepted Answer

It depends who owns the record, and it deserves a deliberate choice rather than a default. Update or create lets the model introduce people, update only enriches those already there and skips the rest, and create only adds new ones without touching matches. If Salesloft is populated from your CRM, update only keeps ownership clear. If the model is where qualified people get identified, letting it create them is the point.

Question 5

What does this change day to day?

Accepted Answer

It moves the decision about who to contact from a periodic exercise to a continuous one. Signals that matter, like a usage jump or a renewal approaching, change weekly, while a manually built cadence list changes whenever someone finds time. Tying enrolment to a model means the working list keeps up with the underlying data without anyone maintaining it.

Sync Databricks to Salesloft

Sync Databricks to Salesloft with Polytomic

Add people to cadences

Works on any cloud

Accounts, people, cadences

Or sync Salesloft to Databricks

Trusted by businesses worldwide

Step-by-step integration guide

Connect Databricks in Polytomic

Connect Salesloft in Polytomic

Create a sync between Databricks and Salesloft

Map fields and enable the sync

Frequently asked questions

The sync and ETL platform that does it all

Powerful data sync

Advanced analytics

Enterprise security

Easy setup

Ready to connect Databricks with Salesloft?