feat(gong): align tools with official API spec + 4 new tools#5632
Conversation
…ef, unassign, and logs tools - fix gong_list_flows: query param was flowEmailOwner (typo copied from Gong's endpoint prose); the API requires flowOwnerEmail, so every call failed - create_call: drop phantom url output (API returns only requestId/callId) and make downloadMediaUrl optional per spec - list_scorecards: refresh to current spec (numeric IDs, questionType/answerGuide/minRange/maxRange/answerOptions, reviewMethod) - answered_scorecards: map selectedOptions on answers, correct score range description (1-50) - surface requestId uniformly across all read tools; totalRecords no longer fabricated from page size - normalize includeAvatars to a strict boolean param, uppercase aggregationPeriod, encode userId path param - validate email/phone format before irreversible GDPR purge calls - new tools: gong_ask_anything, gong_get_brief (AI entity Q&A/briefs), gong_unassign_flow_prospects, gong_get_logs
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
PR SummaryMedium Risk Overview New capabilities: Breaking / behavior fixes: Hardening: URL-encoded call/user IDs, strict Reviewed by Cursor Bugbot for commit f95748c. Configure here. |
Greptile SummaryThis PR aligns the Gong integration with the current API shape and adds more Gong operations. The main changes are:
Confidence Score: 5/5This looks safe to merge.
Important Files Changed
Reviews (3): Last reviewed commit: "fix(gong): final spec-alignment pass, re..." | Re-trigger Greptile |
…ration - ask_anything/get_brief: entityFromDateTime/entityToDateTime now conditionally required (UI) and validated tool-side when timePeriod is CUSTOM_RANGE - block params mapper: remaps are gated by the selected operation so stale values from previously configured operations can no longer overwrite fromDateTime/fromDate/workspaceId
|
@cursor review |
- ask_anything/get_brief: send fromDateTime/toDateTime only for CUSTOM_RANGE; declare mcpResult brief section field
- unassign: dedicated optional unassignFlowId subblock so a stale assign-flow ID can never silently narrow an unassign to one flow
- get_logs: logType is a closed enum (AccessLog, UserActivityLog, UserCallPlay, ExternallySharedCallAccess, ExternallySharedCallPlay) - dropdown in block, enumerated in tool description
- get_folder_content: folderId optional per spec; get_call: encode callId path param
- list_trackers: drop saidInCallParts (absent from the spec's KeywordTracker schema)
- get_extensive_calls: correct declared interactionStats item shape to {name, value}
- block inputs: list all remapped subblock params; optional flags on nullable outputs; absolute types re-export
- regenerate Gong integration docs and integrations.json entries (29 operations)
|
@cursor review |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit f95748c. Configure here.
Summary
gong_list_flows— it sentflowEmailOwner(a typo in Gong's own endpoint prose) instead of the requiredflowOwnerEmailquery param, so the tool failed on every callcreate_call: removed the phantomurloutput (the API returns onlyrequestId/callId) and madedownloadMediaUrloptional to match the speclist_scorecards: refreshed to the current spec — numeric IDs, new question fields (questionType,answerGuide,minRange,maxRange,answerOptions), andreviewMethodanswered_scorecards: now mapsselectedOptionson answers; corrected score range description (1–50)requestIduniformly across all read tools;totalRecordsis no longer fabricated from page size when missingincludeAvatars, uppercasedaggregationPeriod, URL-encodeduserIdpath param, and email/phone format checks before the irreversible GDPR purge endpointsgong_ask_anythingandgong_get_brief(Gong's AI entity Q&A/brief endpoints — flagged as credit-consuming),gong_unassign_flow_prospects(inverse of the existing assign tool), andgong_get_logsType of Change
Testing
Typecheck and lint clean; Gong webhook provider tests pass (9/9). Every endpoint, param name, and response field was cross-checked against the official Gong OpenAPI spec.
Checklist