> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloudglue.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Gong

> Connect your Gong recordings to Cloudglue

Connect your Gong account to use your cloud meeting recordings with Cloudglue APIs.

## Adding the Gong Data Connector

1. Navigate to the [Data Connectors page](https://app.cloudglue.dev/home/data-connectors) in the Cloudglue app.
2. Click the Gong data connector card. <img src="https://mintcdn.com/aviary/tPIU4S1yLMHZDipi/images/data-connectors/gong-import.webp?fit=max&auto=format&n=tPIU4S1yLMHZDipi&q=85&s=9b4cd6dea71b5776b428bc7cc5c46eba" alt="Gong data connector focused" width="1002" height="448" data-path="images/data-connectors/gong-import.webp" />
3. Follow the popup instructions to authorize Cloudglue access to your media.
4. Verify the connection by checking for the **Connected** indicator on the card.

<Note>
  Ready to set up your Gong data connector? Visit [our
  app](https://app.cloudglue.dev/home/data-connectors) to get started.
</Note>

<Info>
  **Need help setting up your data connector?** Contact our team directly for
  assistance with the setup process.
</Info>

## Using Gong with Cloudglue

To use Gong recordings with Cloudglue, you can use the `gong://call/` prefix in your Cloudglue API requests.

Example:

```bash theme={null}
gong://call/1234567890
```

**Example API Request to get [a multimodal description](/api-reference/endpoint/describe/post) of a recording:**

```bash theme={null}
curl --request POST \
  --url https://api.cloudglue.dev/v1/describe \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
  "url": "gong://call/1234567890",
  "enable_summary": true,
  "enable_speech": true,
  "enable_visual_scene_description": true,
  "enable_scene_text": true
}'
```

## Browsing and filtering calls

[`GET /data-connectors/{id}/files`](/api-reference/endpoint/data-connectors/list-files)
lists calls from your Gong workspace, newest first. Private calls are never
listed (they also can't be synced). `from`/`to` filter by call start date —
when `from` is omitted, listing looks back 6 months — and `title_search`
matches call titles.

```bash theme={null}
curl --request GET \
  --url 'https://api.cloudglue.dev/v1/data-connectors/YOUR_CONNECTOR_ID/files?from=2026-06-01&title_search=kickoff' \
  --header 'Authorization: Bearer YOUR_API_KEY'
```

<Note>
  When filters are applied, a page can contain fewer than `limit` items — even
  zero — while more calls remain. Keep paginating until `next_page_token` is
  null rather than stopping at the first short or empty page.
</Note>

<Note>
  Listed calls include audio-only and still-processing calls for visibility, but
  **only calls with video media can currently be synced** — check each item's
  `mime_type`: `video/mp4` means importable, `audio/mpeg` or `null` means sync
  will fail with a not-found error.
</Note>

## Source metadata

When a Gong call is imported, Cloudglue captures the call's source metadata
onto the resulting file under `source_metadata`: title, start/scheduled times,
duration, direction, system, scope, language, workspace, the participants
(names, emails, affiliations), and — when your Gong tenant has Call Spotlight —
the AI brief, key points, topics, and trackers. Signed media URLs are never
stored. The `source_metadata` field is returned on the
[file object](/api-reference/endpoint/files/get-id).

<Note>
  The AI content fields are captured at sync/lookup time. Items returned while
  browsing carry the call facts only, and tenants without Call Spotlight simply
  get `null` for the AI fields.
</Note>

[`GET /data-connectors/{id}/source-metadata`](/api-reference/endpoint/data-connectors/source-metadata)
previews a call's source metadata without importing it:

```bash theme={null}
curl --request GET \
  --url 'https://api.cloudglue.dev/v1/data-connectors/YOUR_CONNECTOR_ID/source-metadata?url=gong://call/1234567890' \
  --header 'Authorization: Bearer YOUR_API_KEY'
```

## UI Importing for Testing

Use the Cloudglue integration UI to quickly import Gong files for testing your endpoints.

<img src="https://mintcdn.com/aviary/tPIU4S1yLMHZDipi/images/data-connectors/gong-quick-import.webp?fit=max&auto=format&n=tPIU4S1yLMHZDipi&q=85&s=6526ce35b760a1d10adc6d27ba1ac166" alt="File Chooser" width="1005" height="493" data-path="images/data-connectors/gong-quick-import.webp" />

To access this page, visit [our app](https://app.cloudglue.dev/home/data-connectors) and click on **Select Videos** on the Gong connector. <img src="https://mintcdn.com/aviary/tPIU4S1yLMHZDipi/images/data-connectors/gong-import-connected.webp?fit=max&auto=format&n=tPIU4S1yLMHZDipi&q=85&s=ad7516da95e5751f43b6b35ffdbe72f5" alt="Quick Import Button" width="1043" height="232" data-path="images/data-connectors/gong-import-connected.webp" />

## Managing Access

You maintain full control over your data access. Remove this data connector by doing the following:

* **Remove connection** by revoking the connector on our [website](https://app.cloudglue.dev/home/data-connectors).

Once removed:

* You cannot import new recordings into Cloudglue until you reconnect.
* Any recordings you previously imported will remain in Cloudglue. These can be viewed and deleted from [File Management](https://app.cloudglue.dev/home/files).

## Security

<Info>
  The Gong data importer does not have access to videos marked as private on the
  Gong platform. To access these videos, you can manually add the recording to
  Cloudglue using the API.
</Info>

Cloudglue uses Gong OAuth to securely access your recordings with minimum required permissions. This approach:

* **Maintains your control** - You own and manage the connector
* **Follows Gong security standards** - Uses OAuth with minimum permissions
