Weld
Start free

Gong to Microsoft SQL Server integration

Connect Gong to Microsoft SQL Server and automatically sync your CRM data. Weld extracts data from Gong, loads it into Microsoft SQL Server, and lets you transform the data using SQL or dbt, no custom scripts required.

Start for free
4.8 on G2
GongSource
WeldWeld
Microsoft SQL ServerWarehouse
Weld · New sync
GongSourceGongConnected
Tables to sync
  • user20 cols
  • workspace4 cols
  • call29 cols
  • library_folder7 cols
  • answered_scorecard10 cols
  • call_in_folder10 cols
  • Extract
  • Load
  • Keep in sync
Microsoft SQL ServerDestinationMicrosoft SQL ServerReady
gong schema
  • gong.userSynced
  • gong.workspaceSyncing
  • gong.callSynced
  • gong.library_folderSynced
  • gong.answered_scorecardSynced
  • gong.call_in_folderSynced
Gong tables
63
fields, typed
481
relationships kept
35
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 Gong to Microsoft SQL Server in Weld.
In the app, with the API or an agent.

API guideMCP docs
Weld · New Gong sync
GongNew connectionGongAuthorised
Connection namegong
AuthorizeOpens Gong to grant read access
Use cases

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

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

Combine Gong data with other customer touchpoints to build a unified customer view across sales, marketing, and support.

  • Sales pipeline analytics

    Analyze your full sales funnel in Microsoft SQL Server. Join CRM data with marketing and product data for complete attribution.

  • Centralized data warehouse

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

Schema

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

Weld syncs the objects the Gong connector exposes into Microsoft SQL Server, and you choose which tables and fields to include. The connector's docs list what is available.

Open the schema explorer
All 63 tables
  • user
  • workspace
  • call
  • library_folder
  • answered_scorecard
  • call_in_folder
  • scorecard
  • manual_call_integration
  • manual_call
  • permission_profile
  • tracker
  • call_participant
  • call_context_integration
  • call_outline
  • call_outline_item
  • call_highlight_item_start_time
  • transcript_sentence
  • call_speaker
  • call_highlight_item
  • call_highlight
  • call_key_point
  • transcript
  • user_setting_history
  • permission_call_access
  • permission_coaching_access
  • permission_deal_access
  • permission_email_access
  • permission_forecast_access
  • permission_forecast_edit_submission_access
  • permission_forecast_edit_target_access
  • and 33 more
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 Gong 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 workspace? Use our Gong data in Microsoft SQL Server.

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

●weld·search_available_references
⎿raw.gong.call
raw.gong.workspace
+ 61 more Gong tables
●weld·get_reference_schema
⎿call · 29 columns
joins workspace on workspace_id
●weld·run_query
⎿select w.id, count(*) from {{raw.gong.call}} c
join {{raw.gong.workspace}} w on c.workspace_id = w.id
group by 1
submitted
●weld·get_query_status
⎿DONE
●weld·get_query_result
⎿rows returned
✓Answered from Gong data in Microsoft SQL Server
>Ask about your Gong data
Under the hood

Technical considerations.
What to expect.

Incremental syncing
Weld uses incremental syncing where supported by the Gong API, loading only new and updated records to minimize data transfer and warehouse costs.
Schema handling
Weld automatically manages schema changes. If Gong 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

Microsoft SQL Server setup guide

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

Schema

Gong schema explorer

Browse all 63 tables and 481 fields.

Connector

Gong connector

Everything Weld does with Gong.

Connector

Microsoft SQL Server connector

Everything Weld does with Microsoft SQL Server.

FAQ

Common questions.
About Gong to Microsoft SQL Server.

Start syncing Gong to Microsoft SQL Server.

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

GongSource
WeldWeld
Microsoft SQL ServerWarehouse
Start for freeTalk to us
Related

Related integrations.
More with Gong and Microsoft SQL Server.

View all