Question 1

Which Outreach objects can a Redshift 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 warehouse for analysis but not written back. That narrow surface covers the jobs teams actually want: keep account and prospect fields current, and decide who gets worked.

Question 2

Can I enrol prospects in an Outreach sequence from Redshift?

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 there is no need to run a separate seeding sync beforehand. That makes it workable to model a list of accounts showing buying signals and let enrolment follow automatically as they qualify.

Question 3

How do I stop the Outreach sync scanning my whole table?

Accepted Answer

Set a tracking column and design the table around it. Polytomic records the current maximum value, then reads only rows past the previous mark and up to that new high water mark. The gain depends on Redshift being able to filter that column efficiently, so the tracking column is a good candidate for the sort key on the underlying table. Without one the model still syncs differentially, but the query itself still has to scan.

Question 4

What happens to rows that Outreach rejects?

Accepted Answer

They are set aside rather than stopping the run. Each rejected record is isolated and logged while the rest carry on, and it shows up in Sync History with the identity value and the error message, usually downloadable so you can work through them in bulk. Transient failures retry on their own. For anything needing a real fix, retry from History once corrected, or switch on automatic retry so they clear themselves on the next run.

Question 5

When is reverse ETL better than exporting a prospect list?

Accepted Answer

Once the list needs to change more often than someone is willing to rebuild it. A quarterly export is fine if your targeting is stable, but signals like a usage jump or a support pattern suggesting expansion move weekly, and by the time a spreadsheet reaches a rep it is describing last month. Reverse ETL keeps enrolment tied to the model, so the working list moves when the underlying facts do.

Sync Redshift to Outreach

Sync Redshift to Outreach with Polytomic

Enrol straight into sequences

Accounts, prospects, sequences

Reads forward, not everything

Or sync Outreach to Redshift

Trusted by businesses worldwide

Step-by-step integration guide

Connect Redshift in Polytomic

Connect Outreach in Polytomic

Create a sync between Redshift 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 Redshift with Outreach?