Question 1

Which Outreach objects can a ClickHouse 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 still covers what teams want here, which is keeping account and prospect fields current and controlling who gets worked.

Question 2

Can I enrol prospects straight 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. That makes it realistic to model a behavioural trigger, say accounts that crossed a usage threshold this week, and let enrolment follow automatically as people qualify.

Question 3

When should this sync run?

Accepted Answer

Away from whatever else is hammering the cluster, particularly for the first run. A model reading across a large event table is a genuine ClickHouse query competing for the same memory and threads as everything else, and Polytomic does not set its own quota or priority. Once a tracking column is in place ongoing runs read a bounded window and become much cheaper, so the usual shape is a heavy first load off peak followed by a light frequent schedule.

Question 4

What happens to rows Outreach rejects?

Accepted Answer

They are set aside rather than stopping the run. Each rejected record is isolated and logged while the rest continue, appearing 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, and anything needing a real fix can be retried from History or picked up automatically on the next run.

Question 5

When does this beat handing reps a list?

Accepted Answer

As soon as the trigger is behavioural. A list of accounts that looked interesting last month is stale by the time it is worked, whereas usage crossing a threshold is a fact that just happened. Reverse ETL turns that query result into enrolled prospects on a schedule, so outreach follows the behaviour rather than following whenever somebody last exported a spreadsheet.

Sync ClickHouse to Outreach

Sync ClickHouse to Outreach with Polytomic

Enrol straight into sequences

Accounts, prospects, sequences

Schedule around the cluster

Or sync Outreach to ClickHouse

Trusted by businesses worldwide

Step-by-step integration guide

Connect ClickHouse in Polytomic

Connect Outreach in Polytomic

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