PollyHub

Gong Connector

Clean

Access Gong with managed OAuth to retrieve call recordings, transcripts, and user data using the Gong API.

SKILL.md

---
name: gong-connector
description: "Access Gong revenue intelligence with managed OAuth. Retrieve call recordings, transcripts, and user data. Use when the user wants to list Gong calls, read call transcripts, search recordings, get call details, or view Gong user data."
metadata:
  polly:
    polly_managed_connector: true
    auth:
      - env: GONG_ACCESS_TOKEN
        type: oauth2
        integration_id: gong
        description: Gong OAuth access
        scopes:
          - api:calls:read:extensive
          - api:calls:read:transcript
          - api:calls:create
          - api:users:read
    primaryEnv: GONG_ACCESS_TOKEN
---

# Gong Connector

Access Gong through the Gong REST API v2 using managed OAuth.

## First-Time Setup

If Gong is not connected yet, run:

`manage_auth(action="connect", integration_id="gong", auth_env="GONG_ACCESS_TOKEN")`

## Auth & Security

- Authentication is managed by Polly + Nango from `metadata.polly.auth`
- Never ask users to paste tokens in chat
- Never print or log token values
- If auth fails, reconnect with:
  `manage_auth(action="connect", integration_id="gong", auth_env="GONG_ACCESS_TOKEN")`

## Base URL

`https://api.gong.io/v2`

All requests include:

`Authorization: Bearer $GONG_ACCESS_TOKEN`

**Note:** Gong uses POST for many read operations, passing filters in the request body.

## Quick Usage

List calls:

```bash
curl -sS -X POST \
  -H "Authorization: Bearer $GONG_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"filter":{"fromDateTime":"2026-01-01T00:00:00Z","toDateTime":"2026-01-31T23:59:59Z"}}' \
  "https://api.gong.io/v2/calls/extensive"
```

Get call transcript:

```bash
curl -sS -X POST \
  -H "Authorization: Bearer $GONG_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"filter":{"callIds":["<callId>"]}}' \
  "https://api.gong.io/v2/calls/transcript"
```

Get a call:

```bash
curl -sS \
  -H "Authorization: Bearer $GONG_ACCESS_TOKEN" \
  "https://api.gong.io/v2/calls/<callId>"
```

List users:

```bash
curl -sS \
  -H "Authorization: Bearer $GONG_ACCESS_TOKEN" \
  "https://api.gong.io/v2/users"
```

## Rules

- Many Gong read endpoints use POST with filter bodies instead of GET with query params
- For pagination, pass `cursor` from prior responses in the request body
- Date filters use ISO 8601 format (`fromDateTime`, `toDateTime`)
- On API errors, surface status + response body clearly
- On 401/403, reconnect with:
  `manage_auth(action="connect", integration_id="gong", auth_env="GONG_ACCESS_TOKEN")`
- Never log, echo, or expose credential values in any output
Authorstella
Downloads2
Versions2
Published1d ago
Auth Requirements
GONG_ACCESS_TOKENoauth2

integration: gong

Version History

v1.1.0latest

Add polly_managed_connector flag and connector-skill tag

Apr 9, 2026

Clean.zip
v1.0.0

Initial release of v0.8 Tier 3 connectors

Apr 9, 2026

Clean.zip

SHA-256 (latest)

1f787e1594fc634fa7fe5332980ef2532ebd6af6284bc6aa0e0a9a34f7815426