Gong captures every sales call, surfaces deal-warning signals, and scores rep performance — the conversation-intelligence layer most large sales orgs run. Connecting Gong to clariBI brings transcripts, scorecards, and deal-risk signals into your AI analyses.
Why connect Gong
Sales-call insights ("what objections did prospects raise this week about pricing?") usually mean reviewing dozens of recordings by hand.
With Gong connected, you can ask "Top 5 objections by deal value last quarter", "Which reps had the most positive engagement scores last week?", or "Surface deals tagged with a risk warning in Q4" and the AI engine pulls the answer.
How the connection works
clariBI talks to Gong through its hosted MCP server at https://mcp.gong.io/mcp. Authentication uses an OAuth flow against an OAuth app you register in the vendor's developer console. Tokens stay encrypted server-side and never leave clariBI in clear form.
sequenceDiagram
actor U as You
participant C as clariBI
participant V as Gong
U->>C: Click Authorize with Gong
C->>V: Open OAuth authorization
V-->>U: Grant read access?
U->>V: Approve
V-->>C: Authorization code
C->>V: Exchange code for tokens
V-->>C: Access + refresh tokens
C->>C: Encrypt and store credentials
C-->>U: Connection ready
Available tools
clariBI exposes the read-only Gong tools that the vendor's MCP server publishes at connection time. Write operations (create, update, delete, send, refund) are filtered out by a name-pattern blocklist before any tool reaches the analysis engine, so connecting Gong cannot modify data on the vendor side.
The exact tool inventory depends on the Gong features your account has access to. After connecting, try a few natural-language questions to see what Gong data clariBI can pull.
Data flow during analysis
When you ask a question that maps to Gong, the AI engine routes to the right tool, reads the result, and pairs the answer with a chart you can pin to a dashboard.
sequenceDiagram
actor U as You
participant C as clariBI
participant AI as AI engine
participant V as Gong
U->>C: Ask a question about sales conversation intelligence
C->>AI: Plan the analysis
AI->>V: Call the right tool
V-->>AI: Tool result
AI->>AI: Summarize and chart
C-->>U: Answer plus visual
Setting up the connection
- Open Data Sources in the clariBI sidebar.
- Click Add data source.
- Open the MCP Servers tab.
- Click the Gong card.
- In Gong, open Settings → API → OAuth apps and create a new OAuth app with a redirect URI pointing to clariBI (shown on the connect screen).
- Copy the Client ID and Client Secret from Gong and paste them into clariBI.
- Click Connect, authorize on Gong's consent screen, and give your data source a name.
Permissions and data access
Gong does not support Dynamic Client Registration, so you create the OAuth app in Gong and paste the credentials. clariBI uses them only for the connect handshake; refresh-token rotation happens server-side. Revoke from Gong Settings → API at any time.
Troubleshooting
| Error | Cause | Fix |
|---|---|---|
| "Redirect URI mismatch" | The redirect URI registered in Gong does not match the one clariBI generated for your org. | Copy the redirect URI shown in the connect modal into your Gong OAuth app settings and try again. |
| "Insufficient scope" | The OAuth app did not request enough scopes on the Gong consent screen. | Re-create the app with broader scopes and reconnect. |