Intercom to PostgreSQL integration
Connect Intercom to PostgreSQL and automatically sync your customer support data. Weld extracts Contacts, Conversations, Companies, and Tags from Intercom, loads them into PostgreSQL, and lets you transform the data using SQL or dbt, no custom scripts required.
Source
WarehouseSourceIntercomConnected- call19 cols
- conversation59 cols
- contact43 cols
- admin5 cols
- tag3 cols
- company14 cols
- Extract
- Load
- Keep in sync
DestinationPostgreSQLReady- intercom.callSynced
- intercom.conversationSyncing
- intercom.contactSynced
- intercom.adminSynced
- intercom.tagSynced
- intercom.companySynced
- Intercom tables
- 17
- fields, typed
- 220
- relationships kept
- 10
- agent context included
- MCP
Trusted by data and AI teams
How to set up Intercom to PostgreSQL in Weld.
In the app, with the API or an agent.
New connectionIntercomAuthorisedWhy sync Intercom to PostgreSQL?
Ready for analysis.
Centralizing your Intercom data in PostgreSQL lets you join it with other data sources for cross-platform analytics and deeper insights.
Build reliable dashboards and reports by querying Intercom data directly in PostgreSQL using SQL or your preferred BI tool.
Support metrics and SLA tracking
Monitor ticket volume, resolution times, and satisfaction scores from Intercom in PostgreSQL. Correlate support data with product and customer data.
Centralized data warehouse
Bring Intercom data into PostgreSQL alongside other sources to create a single source of truth for your organization.
Automated reporting
Replace manual exports and spreadsheet-based reporting with automated pipelines from Intercom to PostgreSQL. Connect BI tools like Looker, Metabase, or Power BI.
What data can you sync?
Every Intercom table, keys intact.
Weld syncs the following data objects from Intercom into PostgreSQL. The exact tables and fields depend on your Intercom configuration and the permissions granted during setup.
- call
- conversation
- contact
- admin
- tag
- company
- conversation_part
- contact_company
- contact_tag
- conversation_admin
- conversation_contact
- conversation_tag
- team_admin
- team
- ticket
- contact_social_profile
- conversation_part_attachment
Ask your agent.
It queries PostgreSQL for you.
Connect Claude, Cursor, ChatGPT or your own agent to Weld over MCP. It reads the Intercom context, finds the tables it needs and runs the query in PostgreSQL.
How many call rows do we have per conversation? Use our Intercom data in PostgreSQL.
Reading the Intercom context first, so the query uses the right tables and keys.
Technical considerations.
What to expect.
ELT vs. reverse ETL: Intercom and PostgreSQL
ELT (Extract, Load, Transform) moves data from Intercom into PostgreSQL for analysis. This is the approach shown on this page, and the one to use for dashboards, reports, and data models.
Reverse ETL works the other direction: it pushes enriched data from PostgreSQL back into Intercom. For example, you could sync computed lead scores or customer segments from your warehouse into Intercom to personalize outreach.
Weld supports both directions, so you can build a complete data loop between Intercom and PostgreSQL.
PostgreSQL to Intercom- Incremental syncing
- Weld uses incremental syncing where supported by the Intercom API, loading only new and updated records to minimize data transfer and warehouse costs.
- Schema handling
- Weld automatically manages schema changes. If Intercom adds new fields, they're detected and added to the corresponding PostgreSQL tables.
- Data freshness
- Sync frequency depends on your Weld plan. Most connectors support schedules from every 5 minutes up to daily intervals.
- Security
- All data is encrypted in transit (TLS) and at rest. Weld is SOC 2 Type II compliant and supports IP whitelisting for database connections.
Keep reading.
Guides, docs and schema.
Common questions.
About Intercom to PostgreSQL.
Start syncing Intercom to PostgreSQL.
Set up your Intercom data pipeline in minutes. No credit card required. Free for 14 days.
SourceWarehouse
