gong.
Connect
Gong uses HTTP Basic authentication with the key and secret, not a Bearer token:
Node
ancha connect gong --lang ts prints.
Endpoints
All five are partial. Responses carry
requestId; paged responses carry records and a cursor while more pages remain. Dates need a timezone, and time ranges include the start and exclude the end. Unknown routes and fields return HTTP 501 with x-ancha-gap: 1.
Behavior
- Access. The credentials belong to the Acme account and can read only the Revenue team workspace. Calls in other workspaces or accounts return 404 and are left out of lists.
- Transcript timing. A transcript can become available after its call. Before then, it is left out of mixed requests, and a request for only unavailable transcripts returns 404.
- Limits. Pages hold at most 100 records. Requests are limited to 3 per simulated second and 10,000 per simulated day; past that, Gong answers 429 with
Retry-After. - CRM context. Extensive call data links the Salesforce starter records: the Ridgeway Robotics account, Erin Walsh and the rollout opportunity, and the Pinecrest Health, Bluefield Logistics, Kestrel Credit Union and Lakeview Retail accounts and opportunities. It is seeded data; changing Salesforce does not change it.
Starter data
Thegong-starter dataset is the account Acme.
A second account, Helix Manufacturing, with its own workspace (
200001), user (700002) and call (400001), exists to test that access stays inside the right account.
Checks
Gong is read-only and has no state checks. Use trace checks, for example{ called: "POST /v2/calls/transcript" }.
Limits
- Read-only: no uploads, no call creation.
- No speech recognition, audio, analysis, trackers or summaries.
- No OAuth or credential provisioning.