Question 1

Which Front objects accept writes from ClickHouse?

Accepted Answer

Accounts and contacts. Everything else is source only, including conversations, channels, contact lists, inboxes, tags, teammates, teams and events, so those can be read into the warehouse but not written to. Accounts and contacts are the practical targets anyway, since they hold the context somebody needs the moment a message arrives.

Question 2

What should the model actually contain?

Accepted Answer

A summary, not a history. The temptation with an event store is to send everything, but a shared inbox displays a handful of fields next to a contact and nobody reads a hundred columns mid conversation. Let ClickHouse do the aggregation, which is what it is best at, and write the four or five values that change a reply: plan, spend, last active, renewal date, open issue count.

Question 3

What decides whether a contact updates or duplicates?

Accepted Answer

The identity field you map, together with the sync mode. Map one column from your model, usually an email address, to the identity field on the Front object. Polytomic looks the record up on that pair and treats a match as an existing contact to update. Then update or create makes the missing ones, update only skips them, and create only adds new ones without touching matches. Most duplicate problems trace back to a loose identity mapping rather than the mode.

Question 4

Should every person in the model end up in Front?

Accepted Answer

Almost certainly not. If the model covers everyone who ever triggered an event, update or create will import all of them into a shared inbox where they are noise rather than context. Update only is normally right here, enriching the contacts Front already knows about because somebody actually wrote in, and leaving the rest of the warehouse where it is.

Question 5

What does an agent gain from this?

Accepted Answer

The ability to tell conversations apart before reading them. A shared inbox shows an address and a message, so everything looks equally urgent until somebody investigates. Reverse ETL attaches plan, spend, activity and renewal date to the contact, so the queue can be ordered by what matters and a reply written knowing who is asking, which is different from simply replying fast.

Sync ClickHouse to Front

Sync ClickHouse to Front with Polytomic

Contacts and accounts

Send the summary, not the rows

Matching prevents duplicates

Or sync Front to ClickHouse

Trusted by businesses worldwide

Step-by-step integration guide

Connect ClickHouse in Polytomic

Connect Front in Polytomic

Create a sync between ClickHouse and Front

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