# Gong

![Gong-logo.svg](https://assets.relyanceuat.xyz/images/docs/12411705424141/12410857711501.svg)
Gong is a revenue intelligence platform for B2B sales teams. It helps businesses close more deals by recording, transcribing, and analyzing sales calls to help highlight sales conversations.

In order to integrate Gong with Relyance AI you will need an **Access Key**, **Access Key Secret**, and **Subdomain**.

#### In Gong:

1. Login to your Gong account.
2. At the bottom left corner, click on **Company Settings**, then on **API**.
3. **If you choose API Keys:**
    1. Click on the **API KEYS** tab.
    2. Click on the **GET API KEY** button.
    3. Copy the **Access Key** and **Access Key Secret** to be used in Relyance.
4. **If you choose OAuth:**
    1. Click on the **INTEGRATIONS** tab.
    2. Click on **Create Integration.**
    3. Complete the form with the required information and click **Save**. This will generate the **Client ID** and **Client Secret** to be used in Relyance.  You can read more about creating an OAuth app on this article: [Create an app for Gong](https://help.gong.io/v1/docs/create-an-app-for-gong#set-up-oauth-access)
        - **Relevant scopes:** api:calls:read:transcript api:calls:read:extensive api:calls:read:basic api:calls:read:media-url api:crm:integrations:read api:users:read api:logs:read api:calls:create api:permission-profile:read api:permission-profile:write api:crm-calls:manual-association:read

        ![Screenshot](https://assets.relyanceuat.xyz/images/docs/12411705424141/35542044995085.png)

        ![Screenshot](https://assets.relyanceuat.xyz/images/docs/12411705424141/35542053644045.png)
        ![Screenshot](https://assets.relyanceuat.xyz/images/docs/12411705424141/35542045001485.png)

        ![image (1).png](https://assets.relyanceuat.xyz/images/docs/12411705424141/37906705549325.png)

#### In the Relyance AI application:

1. Login to your Relyance account.
2. Navigate to the **Settings** Menu in the bottom left-hand side.
3. Select **Integrations**.
4. Search and locate the **Gong** integration card and click on it **.**
5. Click on the **Add Connection** button on the top right.
6. Provide a meaningful name for the integration and click on the **Add** button.
7. In the **Overview** section, review the **Scope and Permission**, and **Endpoint** details and click on **Continue**. For more details, see [Integration Features](/docs/introduction-to-relyance-ai/integration-features/).
8. In the **Connection** section, provide the appropriate values and click on **Continue**,
    - **Connection Name**: This property allows you to update the integration specified in Step 6. If you have multiple integrations for the same vendor, you may want to assign distinct names to each. This helps streamline filtering by **Discovery Source** across the **Inventory**, **Visual** **Maps**, **Assets**, and **Data Flow Analysis** pages.
    - **Rescan Frequency**: This property allows you to configure how often Relyance executes scans against this Vendor connection.
    - **Business Atlas Associations** (required): the business entities or products that newly discovered third parties, services and assets from this integration are attributed to. Choose at least one from the **Select Associations** dropdown — the wizard will not advance past this step without one. For more details, see [Business Atlas](/docs/other-settings/business-atlas-overview/).
9. In the **Authentication** section, choose either **OAuth/App Token** or **Custom**.
    1. For **OAuth/App Token**, paste the **Client Secret** and **Client ID** retrieved from the **In Gong** section. The Gong Subdomain will be found in your Gong URL.
    2. For **Custom**, paste the **Access Key** and **Access** **Key Secret** retrieved from the **In Gong** section.The Gong Subdomain will be the subdomain found in your Gong URL
10. Review the configuration summary from the **Completion** section and click on **Finish.**

![Screenshot](https://assets.relyanceuat.xyz/images/docs/12411705424141/35542375515405.png)

![Screenshot](https://assets.relyanceuat.xyz/images/docs/12411705424141/35542367658381.png)

![Screenshot](https://assets.relyanceuat.xyz/images/docs/12411705424141/35542375519117.png)

![Gong-5.png](https://assets.relyanceuat.xyz/images/docs/12411705424141/12527765598733.png)

![Screenshot](https://assets.relyanceuat.xyz/images/docs/12411705424141/35542367659021.png)

![Screenshot](https://assets.relyanceuat.xyz/images/docs/12411705424141/35542367659277.png)

11. Confirm the integration Status reflects **Connected.**

<!-- failure-modes:begin (generated from the integration catalog; do not hand-edit) -->

## If the connection reports Connected but returns nothing

These are the ways this integration comes back empty without reporting an error. Generated from the integration catalog, so it tracks what the connection actually asks for.

1. **A feature you enabled returns nothing.** Some scopes belong to a feature rather than to the connection: **Data subject requests** needs `api:data-privacy:read`, `api:data-privacy:delete`. Turning the feature on after the connection exists does not widen the grant it already holds, so re-authenticate the connection.
2. **Authorised, then empty.** The connection carries an authorisation, not a password: it stops returning data if the account that granted it loses access, its own permissions narrow, or the grant is revoked at the vendor. None of that reports an error here -- the connection keeps its last status until the next scan.
3. **A credential rotated at the vendor is not picked up here.** **Client ID**, **Client Secret**, **Access Key** and 1 more are stored when you save the connection, so regenerating the value at the vendor breaks the next scan until it is re-pasted here. Recording the expiry on the connection means Relyance warns you before it lapses.
4. **Check the address fields before suspecting the credentials.** **Subdomain** identifies which tenant, region or host to talk to. A wrong value there fails authentication and looks exactly like a bad secret.
5. **Results are capped.** **Maximum Number of Records** defaults to `5000`, so a larger tenant returns a truncated picture that reads like a complete one.

<!-- failure-modes:end -->

<!-- auth-methods:begin (generated from the integration catalog; do not hand-edit) -->

## Authentication methods and fields

Pick one of these under **Authentication Method** on the connection wizard's **Authentication** step. This table is generated from the integration catalog, so it always matches what the form actually asks for.

| Method | Required | Optional |
| --- | --- | --- |
| **Oauth2 / App Token** | `Client ID` (secret), `Client Secret` (secret), `Subdomain`, `Maximum Number of Records` | — |
| **Custom** | `Access Key` (secret), `Access Key Secret` (secret), `Subdomain`, `Maximum Number of Records` | — |

<!-- auth-methods:end -->

<!-- terraform-examples:begin (generated from the integration catalog; do not hand-edit) -->

## Manage this integration with Terraform

Connections for this integration can be managed as code with the [Relyance Terraform provider](https://registry.terraform.io/providers/Relyance/relyance/latest). Non-secret fields go in `auth.params`; secret fields go in `auth.secrets_wo`, which is write-only — never stored in Terraform state. Rotate secrets by bumping `auth.secrets_wo_version`.

### OAuth (browser authorization)

The **OAuth (browser authorization)** method uses a browser authorization flow, so the connection is created in the Relyance app. Manage it in Terraform afterwards by importing it (`terraform import relyance_integration_connection.example gong/<connection_id>`) or reading it with the `relyance_integration_connection` data source.

### Access key & secret

```hcl
resource "relyance_integration_connection" "gong_1" {
  vendor = "gong"
  name   = "<your connection name>"

  auth = {
    method = "access-keys"
    params = {
      subdomain = "<subdomain>"
      maximum_number_of_records = "5000"
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      access_key = var.gong_access_key
      access_key_secret = var.gong_access_key_secret
    }
    secrets_wo_version = 1
  }

  scans = { "data-inspection" = { enabled = true } }
}
```

<!-- terraform-examples:end -->