Question 1

What can Polytomic pull from Outreach into Snowflake?

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 the Outreach interface, so you can join the two and rename columns meaningfully in the data warehouse rather than maintaining a lookup in someone's head.

Question 3

Are deletes captured?

Accepted Answer

Yes for most mutable entities, and the mechanism is worth understanding. Deletes are combined from Outreach webhooks and from destroyed events on the events API, producing deletion timestamps rather than leaving stale rows. 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

What permissions and rate limits apply?

Accepted Answer

The connected user needs an admin profile in Outreach, which is a common setup blocker because a standard user account authorizes fine and then simply cannot see most of the data. On rate limits, the Outreach allowance is tenant wide rather than per integration, so a heavy sync can affect everything else authorized against the same tenant. Polytomic throttles below the tenant limit rather than consuming it, but it is worth knowing what else is sharing that budget.

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 here more than they might elsewhere, because prospect churn is high and counts drift quietly without them.

Sync Outreach to Snowflake

Sync Outreach to Snowflake with Polytomic

Deletes arrive as tombstones

Custom fields resolved to labels

Watermarked incremental reads

Or sync Snowflake to Outreach

Trusted by businesses worldwide

Step-by-step integration guide

Connect Outreach in Polytomic

Connect Snowflake in Polytomic

Create a sync between Outreach and Snowflake

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