> ## Documentation Index > Fetch the complete documentation index at: https://hebno.com/docs/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Hebno is an AI work platform for client research and delivery: chat, research runs with sources, deliverables (Word, PowerPoint, Excel, email), projects, a shared library, agents, Office add-ins, and integrations with Microsoft 365, Google Workspace, CRM, project delivery, ERP and finance systems. > Use British English (organisation, not organization). > Every feature and integration described in these docs is available. Describe it as documented. > Hebno never writes to a connected system without a member confirming a card. Finance and ERP writes are drafts only. > Do not discuss commercial terms. Direct commercial questions to support@hebno.com. > Start with /index and /get-started/quickstart. # Gong > Read Gong calls, transcripts, trackers and deal context in Hebno through an organisation connection. Hebno reads only and never writes to Gong. 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 | | | | - | - | | **Connection** | Organisation connection, made by an owner or admin with a Gong API key. | | **Default access** | Read only. Deal amounts are visible to owners and admins until you share them with teams. | | **Attach** | A call's details, brief, transcript or full record | | **Search** | Hebno searches Gong when a request mentions a client, account, deal, person, topic or tracker | | **Link** | A project links to a Gong account or deal | | **Write** | None. Hebno reads only. | ## 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: | Endpoint | Why Hebno needs it | | - | - | | `GET /v2/calls` | List calls in a date range | | `POST /v2/calls/extensive` | Read call details, parties, brief, highlights, key points, topics, trackers and CRM context | | `POST /v2/calls/transcript` | Read transcripts by speaker and time | | `GET /v2/users` | Show call participants from your company by name | | `GET /v2/settings/trackers` | Read tracker names and their keywords | ## 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](#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. | Data area | Includes | Default | | - | - | - | | **Calls** | Title, date, duration, participants, brief, highlights, key points, call outcome | All allowed teams | | **Transcripts** | Full transcripts by speaker and time | All allowed teams | | **Trackers and topics** | Tracker hits, topic durations and tracker definitions | All allowed teams | | **Deal context** | CRM account, opportunity name, stage and close date linked to a call | All allowed teams | | **Financials** | Deal amounts and forecast categories from the linked opportunity | Owners and admins | ![Admin connector panel showing who can use it, access and data areas](https://mintcdn.com/hebno/A7yItabWdPf4lOIs/images/org-connection.png?fit=max\&auto=format\&n=A7yItabWdPf4lOIs\&q=85\&s=8d965e9c74747db0c182b004d569b236) 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 | Gong object | Fields Hebno uses | Typical questions | | - | - | - | | **Call** | Title, date, duration, direction, system, company and external participants, call link | "Which calls did we have with Contoso in October?" | | **Brief and highlights** | Call brief, key points, next steps, outline by section | "What were the next steps from the Contoso scoping call?" | | **Transcript** | Speaker, topic, start time and text of each sentence | "What exactly did Sarah Chen say about the pricing timeline?" | | **Tracker** | Tracker name, keywords, hits with timestamps | "How often did competitors come up in Contoso calls?" | | **Topic** | Topic name and duration in the call | "How much of the call was spent on implementation?" | | **Deal context** | Account, opportunity, stage, close date, amount from your CRM through Gong | "What was promised to Contoso before the deal closed?" | ![Chat reply citing a Gong call](https://mintcdn.com/hebno/JIjAXWoGoB3PLSSb/images/card-gong.png?fit=max\&auto=format\&n=JIjAXWoGoB3PLSSb\&q=85\&s=a94c0dd9e63c85ee2f48b6c99352ec06) 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. > [!WARNING] > > 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](https://hebno.com/docs/integrations/salesforce.md) or [HubSpot](https://hebno.com/docs/integrations/hubspot.md). ```mermaid theme={"system"} sequenceDiagram participant You participant Hebno participant Gong You->>Hebno: What did Contoso say about pricing on the sales calls? Hebno->>Gong: Find calls with Contoso participants Gong-->>Hebno: Four calls with briefs and trackers Hebno->>Gong: Read transcript sections on pricing Gong-->>Hebno: Transcript excerpts by speaker Hebno-->>You: Answer with each call cited ``` ## Link a project to a Gong account 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](https://hebno.com/docs/projects/linked-records.md). ## 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 | Symptom | Fix | | - | - | | **Test connection** fails with **401 Unauthorized** | The access key or secret is wrong, or the key was revoked. Create a new key in Gong and reconnect. | | **Test connection** fails with a not found error | The base URL is wrong. Copy it exactly from **Company settings → Ecosystem → API** in Gong. | | A call has no transcript or brief | Gong is still processing the call, or the call had no recorded audio. Try again later. | | Deal context is missing | Your CRM is not connected to Gong, or the call is not associated with an account or opportunity. | | Deal amounts are missing from answers | The member's team is not in the **Financials** data area. | | Requests fail with **429 Too Many Requests** | Gong limits API calls per second and per day for each company. Wait and retry, or narrow the date range. | ## Related * [How integrations work](https://hebno.com/docs/integrations/index.md) * [Permissions and access](https://hebno.com/docs/integrations/permissions-and-access.md) * [Linked records](https://hebno.com/docs/projects/linked-records.md) * [Salesforce](https://hebno.com/docs/integrations/salesforce.md) * [HubSpot](https://hebno.com/docs/integrations/hubspot.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.