Question 1

Which Outreach objects can a Databricks model write to?

Accepted Answer

Accounts, prospects and sequences, where writing to a sequence means adding prospects to it. Everything else is source only, so mailings, calls and tasks can be pulled into the lakehouse for analysis but not written back. That narrow surface still covers the jobs teams want: keep account and prospect fields current, and decide who gets worked.

Question 2

Can I enrol prospects in a sequence from a model?

Accepted Answer

Yes, and the missing person case is handled. If a prospect selected for a sequence does not exist in Outreach yet, it is created first and then enrolled, so no separate seeding sync is needed beforehand. That makes it realistic to model a scored list of accounts and let enrolment follow automatically as people cross whatever threshold you set.

Question 3

What can a tracking column miss?

Accepted Answer

Two things worth knowing before you rely on it. An update that does not move the tracking value will not be picked up, so a column like an updated timestamp has to actually change whenever the row changes. And hard deletes cannot be discovered this way at all, since a row that disappears simply stops being returned. If either matters, plan a periodic full read alongside the incremental schedule rather than assuming the watermark covers everything.

Question 4

Does one bad record stop the whole run?

Accepted Answer

No. A rejected record is isolated and logged while everything else continues, then appears in Sync History with its identity value and the error message, usually downloadable so a batch can be worked through at once. Transient failures retry on their own. Anything needing a genuine fix can be retried from History once corrected, or picked up automatically if you enable retrying failed records on the next run.

Question 5

When does this beat handing reps a list?

Accepted Answer

As soon as the list depends on something that moves. A scored account list is only useful while the score is current, and a spreadsheet stops being current the moment it is sent. Reverse ETL writes the model output into Outreach so enrolment tracks the model, meaning a rep working their sequence is working the latest version rather than whatever was true at the last export.

Sync Databricks to Outreach

Sync Databricks to Outreach with Polytomic

Enrol straight into sequences

Accounts, prospects, sequences

Reads forward, not everything

Or sync Outreach to Databricks

Trusted by businesses worldwide

Step-by-step integration guide

Connect Databricks in Polytomic

Connect Outreach in Polytomic

Create a sync between Databricks and Outreach

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 Outreach?