Question 1

What can I write from BigQuery into Salesloft?

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 your data warehouse for reporting but not written back. That writable set covers what teams normally want from reverse ETL here: keep account and person records accurate, and decide who gets worked and when.

Question 2

Can I add people to a Salesloft cadence from BigQuery?

Accepted Answer

Yes, and people who do not exist yet are handled for you. If someone selected for a cadence is not in Salesloft, they are created first and then added, so there is no need for a separate seeding sync beforehand. That makes it realistic to model a qualified list in BigQuery and let enrolment happen on its own as people meet the criteria.

Question 3

Should my BigQuery model create new people in Salesloft?

Accepted Answer

That is what the sync mode decides, and it is worth a deliberate choice. Update or create adds people who are not there, update only enriches existing records and skips the rest, and create only adds new ones without touching matches. If another system already owns who exists in Salesloft, update only avoids duplicate records appearing from rows that never went through your normal process. If the warehouse is the source of qualified people, update or create is the point of the exercise.

Question 4

What happens when a record fails to write to Salesloft?

Accepted Answer

The run keeps going. A record level failure is isolated and logged rather than stopping the sync, and it appears in Sync History with the identity value and the error message, usually downloadable. Transient problems retry automatically. Anything needing a fix can be retried by hand from History, or picked up on its own if you enable retrying failed records on the next run.

Question 5

What problem does this solve for a sales team?

Accepted Answer

It removes the gap between the list that is correct and the list reps actually work. Qualification usually depends on usage signals, renewal timing and support history that live in the data warehouse, and the traditional fix is somebody exporting a spreadsheet once a quarter. Reverse ETL keeps cadence membership and account fields tied to the model, so the list changes when the underlying facts change rather than when someone remembers to refresh it.

Sync BigQuery to Salesloft

Sync BigQuery to Salesloft with Polytomic

Add people to cadences

Accounts, people, cadences

Failed rows can retry

Or sync Salesloft to BigQuery

Trusted by businesses worldwide

Step-by-step integration guide

Connect BigQuery in Polytomic

Connect Salesloft in Polytomic

Create a sync between BigQuery 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 BigQuery with Salesloft?