Skip to main content
The Gong integration brings recorded client conversations into your delivery work. Ask what Contoso said about pricing across the sales calls, which objections came up before the deal closed, or what the account team promised in scope, and Hebno answers from Gong with each call cited. Gong is read only: Hebno never writes to it.

​
At a glance

​
Before you start

You need:
  • An owner or admin role in Hebno.
  • A Gong technical administrator, who creates the API key. Only technical administrators can open the API page in Gong.
  • An access key and access key secret, created in Gong under Company settings → Ecosystem → API with Create. Gong shows the secret once, so copy it before you close the dialog.
  • The base URL shown on the same page, for example https://us-12345.api.gong.io.
  • Your CRM connected to Gong, if you want deal context such as account, opportunity and stage.
Hebno uses these Gong API endpoints:

​
Connect Gong

1

Allow the integration

Open Admin → Connectors → Catalogue, find Gong under Meetings and calls, and set it to Allow.
2

Connect the organisation

Select Connect, enter the base URL, access key and access key secret, then select Test connection. Hebno checks that it can read calls, transcripts and users.
3

Choose teams and data areas

Under Who can use it, choose All teams or pick teams. Under Data areas, choose what members can see. See Data areas.
The card shows Connected with your Gong base URL. Access is Read only and cannot be changed. Members in the selected teams can use Gong in chat straight away. Members do not link their own Gong account, because Gong API keys belong to the company, not to a person.

​
Data areas

Data areas control what members of the allowed teams can see through the organisation connection.
Admin connector panel showing who can use it, access and data areas

An organisation connection with team access and data areas. Financial figures default to owners and admins.

To share deal amounts with engagement leads, open the Gong card in Admin → Connectors, select Financials and add the teams that should see them.

​
What Hebno reads

Chat reply citing a Gong call

A Gong call attached to a chat.

When Hebno reads a call, it uses the brief and highlights first, then a transcript excerpt, then the call details, and the source label shows which. Gong processes a call after it ends, so transcripts and briefs appear once processing is complete. Reads are live. Hebno queries Gong when a request needs it and never copies calls or transcripts into Hebno. Only what a reply used is stored with the conversation as its sources.
Transcript excerpts a reply uses become part of the conversation. Anyone you share the conversation with can read them, including what clients said on the call.

​
Hebno reads only

Hebno does not write to Gong. It does not create calls, edit trackers, add comments, share calls or change call privacy. To record a follow-up, use your CRM integration, such as Salesforce or HubSpot. Linking marks which Gong account or deal belongs to an engagement, so you can ask “what did the client tell sales?” without naming the account.
  1. Open the project and select Brain.
  2. Under Linked records, select Link record, then Gong.
  3. Search by account or opportunity name and select it, for example the Contoso Retail account or the Contoso pricing review deal.
In chats tagged to the project, Hebno starts with calls on the linked account or deal for any question about what the client said. See Linked records.

​
Use Gong in chat

  • Attach: open the + menu, choose Sources → Gong, pick a call, then pick the brief, transcript or full record. Or type / and choose Gong.
  • Ask: name the client, deal, person or topic. For example:
    Summarise everything Contoso said about pricing and margin pressure across the sales calls before we started the engagement.
    What did the account team promise Contoso about scope and timing? Quote the calls.
    Which objections came up most often in Contoso calls, and who raised them?
  • Research runs show a Checking Gong step, with a chip for each call it read.
  • Agents can read Gong on a schedule, for example a weekly brief on new calls with active clients. Gong has no write actions, so agents only read.

​
Troubleshooting