← Back to Skills Marketplace
jdrhyne

Gong

by Jonathan Rhyne · GitHub ↗ · v1.1.0
cross-platform ✓ Security Clean
2104
Downloads
1
Stars
2
Active Installs
2
Versions
Install in OpenClaw
/install gong
Description
Gong API for searching calls, transcripts, and conversation intelligence. Use when working with Gong call recordings, sales conversations, transcripts, meeting data, or conversation analytics. Supports listing calls, fetching transcripts, user management, and activity stats.
README (SKILL.md)

Gong

Access Gong conversation intelligence - calls, transcripts, users, and analytics.

Setup

Store credentials in ~/.config/gong/credentials.json:

{
  "base_url": "https://us-XXXXX.api.gong.io",
  "access_key": "YOUR_ACCESS_KEY",
  "secret_key": "YOUR_SECRET_KEY"
}

Get credentials from Gong: Settings → Ecosystem → API → Create API Key.

Authentication

GONG_CREDS=~/.config/gong/credentials.json
GONG_BASE=$(jq -r '.base_url' $GONG_CREDS)
GONG_AUTH=$(jq -r '"\(.access_key):\(.secret_key)"' $GONG_CREDS | base64)

curl -s "$GONG_BASE/v2/endpoint" \
  -H "Authorization: Basic $GONG_AUTH" \
  -H "Content-Type: application/json"

Core Operations

List Users

curl -s "$GONG_BASE/v2/users" -H "Authorization: Basic $GONG_AUTH" | \
  jq '[.users[] | {id, email: .emailAddress, name: "\(.firstName) \(.lastName)"}]'

List Calls (with date range)

curl -s -X POST "$GONG_BASE/v2/calls/extensive" \
  -H "Authorization: Basic $GONG_AUTH" \
  -H "Content-Type: application/json" \
  -d '{
    "filter": {
      "fromDateTime": "2025-01-01T00:00:00Z",
      "toDateTime": "2025-01-31T23:59:59Z"
    },
    "contentSelector": {}
  }' | jq '{
    total: .records.totalRecords,
    calls: [.calls[] | {
      id: .metaData.id,
      title: .metaData.title,
      started: .metaData.started,
      duration_min: ((.metaData.duration // 0) / 60 | floor),
      url: .metaData.url
    }]
  }'

Get Call Transcript

curl -s -X POST "$GONG_BASE/v2/calls/transcript" \
  -H "Authorization: Basic $GONG_AUTH" \
  -H "Content-Type: application/json" \
  -d '{"filter": {"callIds": ["CALL_ID"]}}' | \
  jq '.callTranscripts[0].transcript[] | "\(.speakerName // "Speaker"): \(.sentences[].text)"' -r

Get Call Details

curl -s -X POST "$GONG_BASE/v2/calls/extensive" \
  -H "Authorization: Basic $GONG_AUTH" \
  -H "Content-Type: application/json" \
  -d '{
    "filter": {"callIds": ["CALL_ID"]},
    "contentSelector": {"exposedFields": {"content": true, "parties": true}}
  }' | jq '.calls[0]'

Activity Stats

curl -s -X POST "$GONG_BASE/v2/stats/activity/aggregate" \
  -H "Authorization: Basic $GONG_AUTH" \
  -H "Content-Type: application/json" \
  -d '{
    "filter": {
      "fromDateTime": "2025-01-01T00:00:00Z",
      "toDateTime": "2025-01-31T23:59:59Z"
    }
  }'

Endpoints Reference

Endpoint Method Use
/v2/users GET List users
/v2/calls/extensive POST List/filter calls
/v2/calls/transcript POST Get transcripts
/v2/stats/activity/aggregate POST Activity stats
/v2/meetings GET Scheduled meetings

Pagination

Responses include cursor for pagination:

{"records": {"totalRecords": 233, "cursor": "eyJ..."}}

Include cursor in next request: {"cursor": "eyJ..."}

Date Helpers

# Last 7 days
FROM=$(date -v-7d +%Y-%m-%dT00:00:00Z 2>/dev/null || date -d "7 days ago" +%Y-%m-%dT00:00:00Z)
TO=$(date +%Y-%m-%dT23:59:59Z)

Notes

  • Rate limit: ~3 requests/second
  • Call IDs are large integers as strings
  • Transcripts may take time to process after call ends
  • Date format: ISO 8601 (e.g., 2025-01-15T00:00:00Z)
Usage Guidance
This skill appears to do what it claims: read a local Gong credentials JSON and call Gong API endpoints. Things to check before installing: 1) Ensure you only place a Gong API key with minimal (read-only) scope in ~/.config/gong/credentials.json and keep that file access-limited. 2) Confirm the skill will call only your configured base_url (the script uses whatever base_url is in the credentials file). 3) The helper script depends on curl, jq, base64 and standard date — make sure those are available; the registry metadata does not list these dependencies. 4) Because the skill will send transcripts and call metadata to Gong, review your Gong API key permissions and rotate keys if needed. 5) Source/homepage is absent; if you require provenance, ask the publisher for upstream source or a repository before trusting it in sensitive environments.
Capability Analysis
Type: OpenClaw Skill Name: gong Version: 1.1.0 The skill bundle is designed to interact with the Gong API, requiring credentials stored in `~/.config/gong/credentials.json`. Both `SKILL.md` and `scripts/gong.sh` demonstrate standard API interaction patterns using `curl` and `jq`. The `SKILL.md` file contains no prompt injection attempts. The `gong.sh` script uses standard shell utilities and does not exhibit any signs of data exfiltration to unauthorized endpoints, malicious execution, persistence mechanisms, or obfuscation. While user input for `call_id` is directly embedded into a JSON string in `gong.sh`, this is unlikely to lead to shell injection due to `curl -d` quoting and would primarily result in API errors rather than local code execution or data compromise, thus not meeting the threshold for 'suspicious' or 'malicious' behavior.
Capability Assessment
Purpose & Capability
Name/description match the behavior: the SKILL.md and script only call Gong endpoints using credentials from ~/.config/gong/credentials.json. Requested access (the credentials file) is appropriate for the stated purpose.
Instruction Scope
Instructions and the provided shell script limit actions to reading the specified credentials file and calling the user-provided Gong base_url endpoints. They do not attempt to read other system files or call external endpoints beyond the configured base_url. Note: the SKILL.md/script reference the optional GONG_CREDS env var but that environment variable is not declared in the registry metadata.
Install Mechanism
No install spec and the skill is instruction-only plus a small helper script — nothing is downloaded or installed automatically, which minimizes install-time risk.
Credentials
The skill requires a credentials JSON (base_url, access_key, secret_key) which is proportional for calling the Gong API. Minor inconsistency: no required env vars or binaries are declared in the registry metadata, yet the script uses environment variable GONG_CREDS and depends on external tools (curl, jq, base64, date).
Persistence & Privilege
The skill does not request always:true or any elevated persistence. It does not modify other skills or system-wide settings; it only reads its own credentials file.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install gong
  3. After installation, invoke the skill by name or use /gong
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.1.0
Fix: add metadata.openclaw with credentials config requirement
v1.0.0
Initial release - list calls, fetch transcripts, user management, activity stats
Metadata
Slug gong
Version 1.1.0
License
All-time Installs 4
Active Installs 2
Total Versions 2
Frequently Asked Questions

What is Gong?

Gong API for searching calls, transcripts, and conversation intelligence. Use when working with Gong call recordings, sales conversations, transcripts, meeting data, or conversation analytics. Supports listing calls, fetching transcripts, user management, and activity stats. It is an AI Agent Skill for Claude Code / OpenClaw, with 2104 downloads so far.

How do I install Gong?

Run "/install gong" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Gong free?

Yes, Gong is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Gong support?

Gong is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Gong?

It is built and maintained by Jonathan Rhyne (@jdrhyne); the current version is v1.1.0.

💬 Comments