Add documentation for native Gong OAuth integration (TSP-1226)

[claude]

Summary

• New page: integrations/popular-integrations/gong.mdx — dedicated Gong integration page covering OAuth setup, all 5 native tool steps (Generic Gong API Call, List Calls, Get Extensive Call Data, Retrieve Call Transcripts, Add New Calls), example use cases, and a migration note for users coming from the previous Pipedream-based Gong actions.
• Updated: get-started/chat/super-gtm/integrations.mdx — Gong accordion updated from API key connection instructions to OAuth, with a link to the new dedicated page.
• Updated: docs.json — Gong added to the CRM & Sales group in the Popular Integrations navigation.

Related

• Implements native Gong OAuth integration documented in PR #14449
• Linear issue: https://linear.app/relevance/issue/TSP-1226/

Test plan

• Verify new Gong page renders correctly in Mintlify preview
• Confirm Gong appears under CRM & Sales in the sidebar navigation
• Confirm links in Super GTM integrations page resolve to the new Gong page
• Check all headings are sentence case and no banned words are present

🤖 Generated with Claude Code

[linear]

TSP-1226

[github-actions]

🎯 Vibe check

Reviewed: 3 files (1 with issues, 2 clean)

Scores

	Dimension	Score	What's holding it back
🟡	Consistency	8/10	gong.mdx Card titles use title case; CLAUDE.md requires sentence case for all title="..." props on Card components. Five instances.
🟢	Technical clarity	9/10	No issues found. Setup steps are specific, prerequisites (Technical Admin permissions) are clearly called out, and the real-time limitation and rate limit notes are appropriately placed.
🟢	Non-technical clarity	9/10	No issues found. Gong is defined before instructions begin, use cases are concrete and domain-specific.
🟡	Structure	8/10	gong.mdx uses a <CardGroup cols={1}> with a single card for the Advanced section — one card is not a group, and this markup adds no value over a short paragraph.

Score key: 🟢 9–10, 🟡 6–8, 🔴 1–5.

✨ Overall vibe: Solid integration docs — well-scoped, accurate, and consistent between the two pages (the Gong accordion in integrations.mdx matches the standalone page). The main thing holding it back is a handful of Card titles that should be in sentence case, and one awkward single-card CardGroup that should just be prose.

🔧 Issues (5)

• integrations/popular-integrations/gong.mdx:36 — Card title "List Calls" → sentence case: "List calls"
• integrations/popular-integrations/gong.mdx:39 — Card title "Get Extensive Call Data" → sentence case: "Get extensive call data"
• integrations/popular-integrations/gong.mdx:42 — Card title "Retrieve Call Transcripts" → sentence case: "Retrieve call transcripts"
• integrations/popular-integrations/gong.mdx:45 — Card title "Add New Calls" → sentence case: "Add new calls"
• integrations/popular-integrations/gong.mdx:53 — Card title "Generic Gong API Call" → sentence case: "Generic Gong API call"

🧩 Component suggestions (1)

• integrations/popular-integrations/gong.mdx:52–56 — <CardGroup cols={1}> wraps a single card for "Generic Gong API Call". A CardGroup with one card adds visual chrome without benefit. Replace with a short paragraph under the ### Advanced heading, e.g.: "Use the Generic Gong API Call tool step to make any request to the Gong REST API when you need functionality beyond the pre-built steps."

✅ Clean files (2)

get-started/chat/super-gtm/integrations.mdx (Gong accordion addition — no issues), docs.json (navigation entry placed correctly under CRM & Sales)

🔋 Credit usage

Item	Count
Files reviewed	3
Context pages read	2
Total lines processed	~750

Files read: integrations/popular-integrations/gong.mdx (109 lines), get-started/chat/super-gtm/integrations.mdx (529 lines), integrations/popular-integrations/hubspot.mdx (60 lines, partial), integrations/popular-integrations/fireflies.mdx (205 lines)