> For the complete documentation index, see [llms.txt](https://notara.gitbook.io/notara-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://notara.gitbook.io/notara-docs/connectors/gong.md).

# Gong

The Gong connector gives the agent read access to your Gong call recordings — listing calls, reading transcripts, and mapping speakers to users.

## What It Enables

| Tool                  | Capability | Description                                                                    |
| --------------------- | ---------- | ------------------------------------------------------------------------------ |
| `list_calls`          | `read`     | List calls in a date range with title, duration, and participant count         |
| `get_call_details`    | `read`     | Fetch detailed call data including parties, topics, and interaction metadata   |
| `get_call_transcript` | `read`     | Get the full transcript for one or more calls as speaker-attributed sentences  |
| `list_users`          | `read`     | List Gong users with name and email (needed to map speaker IDs in transcripts) |

All tools are read-only.

## Setup

**Required:** Gong Access Key and Access Key Secret.

**Where to find them:** Gong Admin panel → Company Settings → Ecosystem → API. An admin must create an API key pair with Read: Calls and Read: Transcripts scopes.

1. In the Notara dashboard, go to **Tools**.
2. Click the **Gong** tile.
3. In Gong, go to **Company Settings → Ecosystem → API** and generate an access key pair.
4. Paste the **Access Key** and **Access Key Secret** into the connector fields.
5. Click **Verify & Save**.

Your credentials are encrypted at rest with AES-256-GCM.

## Example Prompts

> "List all Gong calls from last week."

> "Get the transcript from call ID abc123 and summarize the key objections."

> "Who are the reps in our Gong workspace?"


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://notara.gitbook.io/notara-docs/connectors/gong.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.