Gong Connector

Gong is a revenue intelligence platform that records and analyzes sales calls, emails and meetings to give teams insight into deals and customer conversations.

4.8 on G2
Weld · Data Sources
GongLive
userSynced
workspaceSynced
callSynced
library_folderSyncing
answered_scorecardQueued
Lands insnowflakebigquerydatabricksAgent context over MCP
How it works

Set up in minutes.
No code, no maintenance.

Gong

Gong

Data source

Authenticating...
Ready to connect
Overview

Gong in your warehouse.
Ready for your agents.

Gong is a revenue intelligence platform that records and analyzes sales calls, emails and meetings to give teams insight into deals and customer conversations. Weld's Gong connector is fully managed: it extracts data from Gong, loads it into your warehouse, and keeps it in sync. The data lands in a clean, documented schema with agent context attached, so analysts can query it with SQL or dbt, and agents can query it over the Weld MCP server without guessing at tables or joins.

AgentsQuery over MCPYour warehouse63 tables, with agent contextWeldExtract, load, keep in syncGongSource
Agent context

Gong data schema.
The map your agents read.

Every table, field and relationship Weld syncs from Gong is served to agents as context over MCP, so they pick the right tables and join on the right keys.

tables
63
fields
481
relationships
35
Open the schema explorer
Open the full schema explorer
Weld MCP server

Ask your agent.
It already knows Gong.

Connect Claude, Cursor, ChatGPT or your own agent to Weld over MCP. It reads the Gong context, finds the tables it needs and queries your warehouse.

  • Agent contextGong tables, fields and joins
  • QuerySQL against your warehouse
  • OperateCheck, rerun and refresh syncs
Claude CodeOpus 5
>

How many call rows do we have per workspace? Use our Gong data.

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 your warehouse
>Ask about your Gong data
Weld Connect API

Set it up in code.
One REST API.

Use the Weld Connect REST API to create Gong connections, configure ELT syncs, and manage pipelines entirely through code. Built for embedding, automation, and CI/CD workflows.

POST/elt_syncs
▌
FAQ

Common questions.
About connectors.

Something not covered here? A data engineer can walk through your setup with you.

Talk to us

Put your Gong data to work.

Connect Gong, pick a warehouse, and your agents can query it today. Free for 14 days, no credit card.

GongSource
WeldWeld
MCPAgents