Question 1

What can Polytomic pull from Outreach into Redshift?

Accepted Answer

Prospects and accounts, sequences with their states, steps and templates, mailings, calls, events and activity, tasks, opportunities, users, teams, mailboxes, personas, stages, templates, audit logs and the supporting reference entities. For most teams the interesting join is mailings and calls against opportunities, because that is what connects outbound effort to pipeline created.

Question 2

How do Outreach custom fields arrive?

Accepted Answer

Accounts and prospects expose up to 150 custom field slots, and in the raw API those are named positionally as custom1 through custom150, which is unhelpful on its own. A separate custom fields entity maps each slot to the label your team sees in Outreach, so you can join the two and rename columns meaningfully in the data warehouse rather than keeping a lookup in someone's head.

Question 3

Are deletes captured?

Accepted Answer

Yes for most mutable entities. Deletes are combined from Outreach webhooks and from destroyed events on the events API, producing deletion timestamps rather than leaving stale rows, which Redshift records as soft deletes by default. Two caveats. Delete capture is deliberately skipped on the first full run and begins once a checkpoint exists, so the very first load is a snapshot. And not every entity supports delete events, with events themselves, audit logs, custom field definitions and several reference datasets excluded. For those, a periodic full ETL read is how you reconcile.

Question 4

Does it matter whether we use provisioned Redshift or Redshift Serverless?

Accepted Answer

Not for how the data lands. Write behaviour, merge logic, deletion handling and staging are the same on both. What differs is connection setup. Provisioned clusters use normal database credentials with direct connectivity, optionally through an SSH tunnel, and can stage with either an access key pair or an IAM role. Serverless requires IAM role authentication, with a role that Polytomic can assume, that can reach S3, and that Redshift can also assume to run the COPY.

Question 5

Why replicate Outreach into a data warehouse?

Accepted Answer

Because sales engagement data only answers useful questions when it meets pipeline data, and the two live in different systems. ETL into a data warehouse lets you attribute opportunities to sequences, measure which touches precede a meeting, and compare rep activity to outcomes rather than to other activity. The delete tombstones matter more here than elsewhere, because prospect churn is high and counts drift quietly without them.

Sync Outreach to Redshift

Sync Outreach to Redshift with Polytomic

Deletes arrive as tombstones

Custom fields resolved to labels

Watermarked incremental reads

Or sync Redshift to Outreach

Trusted by businesses worldwide

Step-by-step integration guide

Connect Outreach in Polytomic

Connect Redshift in Polytomic

Create a sync between Outreach and Redshift

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