Weld
Start free

Intercom to Microsoft SQL Server integration

Connect Intercom to Microsoft SQL Server and automatically sync your customer support data. Weld extracts Contacts, Conversations, Companies, and Tags from Intercom, loads them into Microsoft SQL Server, and lets you transform the data using SQL or dbt, no custom scripts required.

Start for freeView setup guide
4.8 on G2
IntercomSource
WeldWeld
Microsoft SQL ServerWarehouse
Weld · New sync
IntercomSourceIntercomConnected
Tables to sync
  • call19 cols
  • conversation59 cols
  • contact43 cols
  • admin5 cols
  • tag3 cols
  • company14 cols
  • Extract
  • Load
  • Keep in sync
Microsoft SQL ServerDestinationMicrosoft SQL ServerReady
intercom schema
  • 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

  • Flatpay
  • Holafly
  • eComplete
  • Dishoom
  • Danish Endurance
  • Female Invest
  • Son of a Tailor
  • Onomondo
  • Medik8
  • Pas Normal Studios
How it works

How to set up Intercom to Microsoft SQL Server in Weld.
In the app, with the API or an agent.

Setup guideAPI guideMCP docs
Weld · New Intercom sync
IntercomNew connectionIntercomAuthorised
Connection nameintercom
AuthorizeOpens Intercom to grant read access
Use cases

Why sync Intercom to Microsoft SQL Server?
Ready for analysis.

Centralizing your Intercom data in Microsoft SQL Server 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 Microsoft SQL Server using SQL or your preferred BI tool.

  • Support metrics and SLA tracking

    Monitor ticket volume, resolution times, and satisfaction scores from Intercom in Microsoft SQL Server. Correlate support data with product and customer data.

  • Centralized data warehouse

    Bring Intercom data into Microsoft SQL Server 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 Microsoft SQL Server. Connect BI tools like Looker, Metabase, or Power BI.

Schema

What data can you sync?
Every Intercom table, keys intact.

Weld syncs the following data objects from Intercom into Microsoft SQL Server. The exact tables and fields depend on your Intercom configuration and the permissions granted during setup.

Open the schema explorer
All 17 tables
  • 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
Weld MCP server

Ask your agent.
It queries Microsoft SQL Server 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 Microsoft SQL Server.

Set up the MCP serverClaudeCursorChatGPTGemini
Claude CodeOpus 5
>

How many call rows do we have per conversation? Use our Intercom data in Microsoft SQL Server.

Reading the Intercom context first, so the query uses the right tables and keys.

●weld·search_available_references
⎿raw.intercom.call
raw.intercom.conversation
+ 15 more Intercom tables
●weld·get_reference_schema
⎿call · 19 columns
joins conversation on conversation_id
●weld·run_query
⎿select j.id, count(*) from {{raw.intercom.call}} c
join {{raw.intercom.conversation}} j on c.conversation_id = j.id
group by 1
submitted
●weld·get_query_status
⎿DONE
●weld·get_query_result
⎿rows returned
✓Answered from Intercom data in Microsoft SQL Server
>Ask about your Intercom data
Under the hood

Technical considerations.
What to expect.

Reverse ETL

ELT vs. reverse ETL: Intercom and Microsoft SQL Server

ELT (Extract, Load, Transform) moves data from Intercom into Microsoft SQL Server 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 Microsoft SQL Server 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 Microsoft SQL Server.

Microsoft SQL Server 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 Microsoft SQL Server 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.
Resources

Keep reading.
Guides, docs and schema.

Documentation

Intercom setup guide

How to connect Intercom to Weld, step by step.

Documentation

Microsoft SQL Server setup guide

How to connect Microsoft SQL Server to Weld, step by step.

Schema

Intercom schema explorer

Browse all 17 tables and 220 fields.

Connector

Intercom connector

Everything Weld does with Intercom.

FAQ

Common questions.
About Intercom to Microsoft SQL Server.

Start syncing Intercom to Microsoft SQL Server.

Set up your Intercom data pipeline in minutes. No credit card required. Free for 14 days.

IntercomSource
WeldWeld
Microsoft SQL ServerWarehouse
Start for freeTalk to us
Related

Related integrations.
More with Intercom and Microsoft SQL Server.

View all