> For the complete documentation index, see [llms.txt](https://www.cakewalk.security/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.cakewalk.security/docs/human-access/connections-and-integrations/integration-guides/gong.md).

# Gong

Connect Gong to Cakewalk for Auto Provisioning with a Tech admin account or Google sign in, plus your company's Gong subdomain.

### :sparkles: Auto Provisioning

| **Authentication method** | Username & password, or a connected Google account. See [Sign in with Google](/docs/human-access/how-to-guides/auto-provisioning/how-it-works/sign-in-with-google.md). |
| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Required permissions**  | `Tech admin`                                                                                                                                                           |
| **Required metadata**     | `Subdomain`. See details [here](#where-do-i-find-my-gong-subdomain).                                                                                                   |
| **MFA**                   | Not supported. Use an admin account that signs in with a password only                                                                                                 |

{% hint style="info" %}
**Signing in with Google:** if your Gong admin account signs in through Google, choose **Sign in with Google** on the Sign-in method step and pick a connected account. Cakewalk opens your company's Gong login page and uses Gong's Google sign in there. The `Subdomain` field is still required. See [Sign in with Google](/docs/human-access/how-to-guides/auto-provisioning/how-it-works/sign-in-with-google.md).
{% endhint %}

Agent Cake invites the user to Gong at the permission profile you mapped, and Gong sends them a welcome email. When access is revoked, Agent Cake deactivates the team member. Their recorded calls and data stay in Gong.

{% hint style="info" %}
**Use an admin account in the Workspace you want managed.** Agent Cake creates the user in the Workspace the admin account opens, and sets that as the user's home Workspace. If your company runs several Gong Workspaces, use a dedicated admin account in the one Cakewalk should manage.
{% endhint %}

<details>

<summary><strong>Where do I find my Gong subdomain?</strong></summary>

Sign in to Gong and look at the web address. It has the form `https://<subdomain>.app.gong.io`.

Enter only the middle part in Cakewalk. The `Subdomain` field already shows `https://` before it and `.app.gong.io` after it, so pasting the full address will not work.

For example, if your company's Gong address is `https://acme.app.gong.io`, enter `acme`.

</details>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.cakewalk.security/docs/human-access/connections-and-integrations/integration-guides/gong.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.