What you can do
Calls - list calls in a date range, and read what Gong understood about them: the AI brief, key points, highlights, topics, tracker hits, outcome, and the participants with their CRM accounts. Full speaker-attributed transcripts are there when a summary isn’t enough. People and setup - list users, workspaces, trackers, and scorecards, so a tracker hit reads as a name rather than an id. By person - find every call and email Gong holds involving one email address, without needing a call id first. Triggers - none. Use it through the assistant in chat or as an action node in an automation.Get your credential
1
Open Gong's API page
In Gong, go to Company Settings → Ecosystem → API. This requires a Gong technical
administrator.
2
Create an access key
Generate a key and copy both the Access Key and the Access Key Secret - Gong shows the
secret once.
3
Note the API base URL
Copy the API Base URL from the same page. Most accounts use
https://api.gong.io; some are
on a regional host such as https://us-11211.api.gong.io.Grant the key only the scopes you want arg.ai to have. The call, user, and settings read scopes
cover everything above; a scope you leave off makes just that action fail, with Gong’s own
message. A Gong API key is account-wide rather than scoped to one person’s calls.
Connect
1
Open Integrations
In arg.ai, go to Settings → Integrations and click Connect on Gong.
2
Enter the base URL and key
Paste the API base URL, then the access key and secret joined with a colon -
accessKey:accessKeySecret.3
Save
arg.ai checks them against your Gong account and connects.
Connecting a key for a Gong account you have already connected replaces that connection’s
credential, keeping the same connection - automations pointing at it keep working. Most Gong
accounts share the one
api.gong.io base URL, so arg.ai tells them apart by the account the key
belongs to. A key that isn’t allowed to read workspaces doesn’t say which account it is for; if
you already have a Gong connection on the same base URL, arg.ai asks you to confirm before it
replaces that connection’s credential rather than guessing. Granting the workspaces read scope
removes the question.Use it
- In chat: “What objections came up on Acme calls last month, and which trackers fired?”
- In an automation: add a Gong action node that reads last week’s call details, and chain a summary or a CRM write off its output.
How a call read works
- Every request is narrowed. Pass specific call ids, or a date range. An unnarrowed request is refused rather than walking your whole call history.
- Ask for the summary first. Call details return Gong’s brief, key points, highlights, topics, trackers, and outcome - usually enough to answer a question without a transcript.
- Transcripts are opt-in and long. Fetch them for specific calls once the summary points at the right ones.
- Results are paged. Gong returns a cursor; the assistant follows it when there is more to read.