Load Gong data to DuckDB

Gong is a revenue intelligence platform that provides programmatic access to call data, transcripts, and metadata via a REST API. Everything needed to build a working Gong → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.

---

Build your Gong to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from Gong to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Gong API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.

---

Gong API at a glance

These values come from the Gong API reference — the authoritative source if anything here looks out of date.

---

How do I authenticate with the Gong API?

Gong supports two authentication methods: Basic Auth using an Access Key (username) and Access Key Secret (password) provided in the Authorization header as 'Basic <base64_encoded_creds>', or OAuth 2.0 using a Bearer token in the Authorization header as 'Authorization: Bearer '.

1. Get your credentials

To obtain API credentials, you must be a Gong technical administrator. Log in to your Gong account, navigate to the Admin Center (Company Settings) > Ecosystem > API (or Settings > API > Integrations), and click 'Get API Key' (or 'Create'). Copy the generated Access Key and Access Key Secret immediately, as the secret is only displayed once. These credentials provide Basic Authentication access to the Gong Public API.

2. Add them to .dlt/secrets.toml

Copy
[sources.gong_source]
access_key = "your_access_key_here"
access_key_secret = "your_access_key_secret_here"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.

---

What Gong data can I load into DuckDB?

These are the Gong endpoints dlt can load into DuckDB:

---

How do I load only new Gong records?

Gong exposes cursor on v2/users, so dlt can request only the records that changed since the last run. Set it as the cursor_path and dlt tracks the high-water mark for you between runs.

Copy
{"name": "users", "endpoint": {
    "path": "v2/users",
    "incremental": {"cursor_path": "cursor", "initial_value": "2024-01-01T00:00:00Z"},
}}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.

---

What does the generated Gong pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /v2/calls and /v2/users from the Gong API into DuckDB:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def gong_source(access_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.gong.io (or a region-specific host like https://{region}.api.gong.io).",
            "auth": {"type": "http_basic", "username": "REPLACE_ME", "password": access_key},
        },
        "resources": [
            {"name": "users", "endpoint": {"path": "v2/users"}},
            {"name": "calls_extensive", "endpoint": {"path": "v2/calls/extensive"}}
        ],
    }
    yield from rest_api_resources(config)


def load_gong_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="gong_pipeline",
        destination="duckdb",
        dataset_name="gong_data",
    )
    load_info = pipeline.run(gong_source())
    print(load_info)


if __name__ == "__main__":
    load_gong_to_duckdb()

Run it with python gong_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I query Gong data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("gong_pipeline").dataset()
df = data.users.df()
print(df.head())

SQL:

Copy
SELECT * FROM gong_data.users LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the Gong to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

• Deploy & schedule — run the pipeline as a managed job with automatic retries.
• Monitor — observable job queues, alerting, and load metrics for every run.
• Transform — promote raw Gong loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load Gong data to?

dlt loads into any of these — only the destination argument changes:

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.

---

Next steps

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack