How to Automate Gong Call Reviews with AI (3 Methods)
Stop listening to every sales call. Learn how to automate Gong call reviews with Claude Code — from simple exports to fully automated grading pipelines.
Most sales leaders know the problem: your team runs 50+ calls a week, but you can only listen to a handful. The rest? You hope they went well.
What if every call got graded automatically? What if you knew which reps needed coaching before the deal slipped?
This playbook shows you three ways to automate Gong call reviews — pick the level that matches your technical comfort and time investment.
What You’ll Walk Away With
| Level | What You Get | Complexity |
|---|---|---|
| Good | On-demand call analysis when you need it | Low — no technical setup |
| Better | Pull and grade transcripts without touching Gong’s UI | Medium — requires API credentials |
| Best | Every call auto-graded, weekly digest in your inbox | Higher — multiple components to configure |
Good: Manual Export + Claude Analysis
Best for: Sales leaders who want quick insights without any technical setup.
What You’ll Get
- Graded transcripts with coaching notes
- Batch analysis of any calls you choose
- Patterns across a set of calls (objection handling, discovery quality, etc.)
The Process
- Export from Gong: Filter by date, rep, or team → select calls → export as CSV
- Save locally: Drop files in a consistent folder (e.g.,
~/Documents/Gong Transcripts/) - Run analysis: Use Claude Code with a grading skill to analyze the batch
How to Build the Grading Skill
Create a Claude Code skill that:
- Reads transcript files from your local folder
- Scores each call against your criteria (discovery quality, talk ratio, next steps, etc.)
- Outputs a summary with grades and coaching notes
Example grading criteria:
- Discovery quality (1-5): Did the rep uncover pain, timeline, budget, decision process?
- Talk ratio: What percentage did the rep talk vs. the prospect?
- Next steps: Clear commitment or vague “let’s circle back”?
- Objection handling: Addressed directly or glossed over?
What You’ll Need
- Gong account with export permissions
- Local folder for transcripts
- Claude Code skill for grading (see workshop materials for skill creation walkthrough)
The Trade-off
You get insights, but you have to remember to do it. No automation means it’s easy to fall behind when things get busy.
Better: API Integration + On-Demand Pull
Best for: Sales leaders comfortable with API setup who want to skip the Gong UI entirely.
What You’ll Get
- Transcripts pulled directly into Claude Code
- Graded and saved as structured markdown
- No manual exports — just run a command when you want new calls
The Process
- Get API credentials: Gong Admin → Company Settings → API → Generate credentials (requires admin access)
- Build the skill: Create a Claude Code skill that calls the Gong API and grades results
- Run on-demand: When you want to review calls, run the skill — it pulls, grades, and saves everything
How to Build It
Your skill needs to:
- Accept a date range (or default to “since last run”)
- Call
POST /v2/calls/transcriptwith the date filter - Parse the response and save each transcript locally
- Run your grading logic on each one
- Output a summary of all calls with grades
Folder structure recommendation:
~/Documents/Gong Transcripts/
├── 2026-01/
│ ├── call_12345_grades.md
│ ├── call_12346_grades.md
What You’ll Need
- Gong API credentials (admin access required)
- Claude Code skill for API calls + grading
- Familiarity with API basics (or willingness to learn)
The Trade-off
More powerful than manual exports, but you still have to remember to run it. No notifications when new calls are ready.
Best: Fully Automated Pipeline
Best for: Sales leaders who want every call graded automatically with zero ongoing effort.
What You’ll Get
- Every call graded the moment it’s processed
- Transcripts + grades synced to Google Drive
- Weekly digest: “12 calls ready for review” in Slack or email
- One-command review to surface patterns and coaching opportunities
How It Works
New call recorded
↓
Gong processes transcript
↓
Webhook fires → n8n catches it
↓
Pull transcript via API
↓
Claude grades against your criteria
↓
Save locally + sync to Drive
↓
Weekly reminder: "Calls ready"
↓
Run /review-calls for patterns
How to Build It
Step 1: Set up the Gong webhook
- Gong Admin → Integrations → Webhooks
- Create webhook for “Call Processed” event
- Point to your n8n webhook URL
Step 2: Build the n8n workflow for new calls
- Webhook trigger node (receives Gong event)
- HTTP Request node:
POST /v2/calls/transcriptwith call ID - Claude node: Grade transcript against your criteria
- Write File node: Save transcript + grade to local folder
- Google Drive node: Sync to shared folder
Step 3: Build the weekly digest workflow
- Schedule trigger (Monday 8am)
- Read local folder for last 7 days of graded calls
- Compile summary stats (avg grade, flagged calls, top performers)
- Slack/Email node: Send digest with link to review
Step 4: Create the review skill
/review-callspulls the week’s graded transcripts- Aggregates patterns across calls
- Flags coaching opportunities
- Allows drill-down into specific calls
What You’ll Need
- Gong API credentials
- n8n instance (cloud: ~$20/mo, self-hosted: free)
- Google Drive (optional but recommended for team access)
- Claude Code skills: grading criteria + review
- Slack or email for notifications
The Trade-off
More components to maintain, but once it’s running, you never think about it. Calls get graded whether you remember or not.
Sample Grading Criteria
Here’s a starting point — customize based on what matters for your team:
| Criteria | What You’re Measuring | Scale |
|---|---|---|
| Discovery quality | Did rep uncover pain, timeline, budget, decision process? | 1-5 |
| Talk ratio | Rep vs. prospect speaking time | % |
| Next steps | Clear commitment or vague follow-up? | 1-5 |
| Objection handling | Addressed directly or glossed over? | 1-5 |
| Personalization | Generic pitch or tailored to prospect? | 1-5 |
| Prospect engagement | Were they leaning in or checked out? | 1-5 |
Why This Matters
For sales leaders: You can’t listen to every call. But now you don’t have to. Weekly reviews show exactly where reps need coaching — before deals slip.
For agency owners: This is productizable. Build the system once, deploy it for clients. “We grade every call your team runs” is a compelling service add-on.
For RevOps: Systematized call review means consistent data. You can finally answer “why are we losing to Competitor X?” with evidence, not hunches.
Choose Your Path
| If you want… | Start with… |
|---|---|
| Quick insights, no setup | Good: Manual export + Claude analysis |
| Skip the Gong UI, run on-demand | Better: API integration |
| Set it and forget it | Best: Fully automated pipeline |
Pick one. Get it working. You can always level up later.
FAQ
Do I need Gong admin access?
For the API methods (Better and Best), yes. For manual exports (Good), you just need export permissions.
What if I use Chorus instead of Gong?
The concepts are the same — Chorus also has API access for transcripts. The specific endpoints will differ, but the workflow structure works.
How accurate is AI grading compared to a human?
It’s consistent, not perfect. AI won’t catch everything a seasoned manager would, but it catches patterns across volume that humans miss. Use it as a first filter, not the final word.
Can I customize the grading criteria?
Yes — that’s the point. The criteria listed here are starting points. Your team’s criteria should reflect what actually matters for your sales motion.
Related Playbooks
- Product Feedback Loop Pipeline — Turn call insights into product feedback
- Competitive Messaging Audit — Use call patterns to inform competitive positioning
Related Blog Posts
- Claude Code for RevOps: 7 Workflows — More AI-powered workflows for revenue operations teams
- What Is a GTM Engineer? — The role that builds automated sales intelligence systems
Want to build workflows like these?
The NativeGTM workshop is a hands-on, 2-day intensive where you build real AI workflows for your specific role.
See Workshops