Conversations and tickets
Both come across, with their parts as separate tables.
Replicate Intercom into PostgreSQL with Polytomic so support conversations are queryable next to product and account data. Contacts, conversations and tickets refresh incrementally on updated at, and ETL keeps conversation parts attached to the conversations they belong to.
Both come across, with their parts as separate tables.
Contacts, conversations and tickets resume rather than rescan.
Admins, teams and tags are small enough to scan each run.
Polytomic is bi-directional by default, so you can move data the other way just as easily.
PostgreSQL to Intercom
Jonathan Krangel
VP Global Head of Revenue Operations
“Polytomic handles so many ETL and sync jobs at Cursor. They are a true partner to us.”
Follow these simple steps to connect Intercom with PostgreSQL in minutes
Connect Intercom
Connect PostgreSQL
Create sync
Enable sync
Connect Intercom to Polytomic by authorizing the app against your workspace.
Connect PostgreSQL to Polytomic with host, port, database, and credentials.
Sync data in either direction between Intercom and PostgreSQL. Choose the source data and destination objects for the direction you need.
Map the fields, choose the sync schedule and behavior, then save and enable the sync.
Get answers to common questions about the integration process
Sync data in either direction between Intercom and PostgreSQL.
Use both integrations' source and destination capabilities in one managed sync workflow.
Enterprise encryption and security protocols ensure your data remains protected.
Get up and running in minutes with our step-by-step integration guide.