# Linking Gong as a source - Docs

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

`npx @posthog/wizard warehouse`

[Learn more](/wizard.md)

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

**Alpha release**

This source is currently in **alpha**. The interface and available tables may change.

Enter your Gong API credentials to pull your Gong data into the PostHog data warehouse.

## Adding a data source

1.  Go to the [sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section in PostHog.
2.  Click **\+ New source** and then click **Link** next to Gong.
3.  In Gong, go to **Company Settings → Ecosystem → API** and create an **Access Key** and **Access Key Secret**. Grant the following read scopes so the connected endpoints can sync: `api:calls:read:basic`, `api:users:read`, `api:settings:scorecards:read`, and `api:workspaces:read`. To also sync the `calls_extensive` table (call participants and CRM associations), additionally grant `api:calls:read:extensive`.
4.  Back in PostHog, enter the `Access key` and `Access key secret`, then click **Next**.
5.  Select the tables you want to sync, set the sync method and frequency, then click **Import**.

Once the syncs are complete, you can start using Gong data in PostHog.

## Available tables

| Table | Description | Sync method |
| --- | --- | --- |
| calls | Call records | Incremental |
| calls_extensive | Call records with participants and CRM associations | Incremental |
| users | Gong users | Full refresh |
| scorecards | Scorecard settings | Full refresh |
| workspaces | Gong workspaces | Full refresh |

**Incremental** tables sync only new or updated records on each run. **Full refresh** tables reload all data on each sync.

The `calls` table syncs basic call metadata. The `calls_extensive` table includes the same metadata plus `parties` (participant name, email, and affiliation) and `context` (linked CRM objects such as Salesforce or HubSpot accounts, opportunities, and contacts).

## Sync limitations

The `calls` and `calls_extensive` tables only sync the last 365 days of data on the initial sync.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| Access key | text | Yes |
| Access key secret | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| calls | Only syncs the last 365 days on initial sync | Incremental, Full refresh | started | — |
| calls_extensive | Only syncs the last 365 days on initial sync | Incremental, Full refresh | started | — |
| users | A Gong user (team member whose calls and activity are tracked). | Full refresh | — | — |
| scorecards | A scorecard template used to evaluate calls in Gong. | Full refresh | — | — |
| workspaces | A Gong workspace grouping users, calls, and settings. | Full refresh | — | — |

### Community questions

Ask a question

### Was this page useful?

HelpfulCould be better