Gong

Gong can provide call transcripts and revenue conversation metadata for oper8r workflows. Use it when your team wants meeting evidence to power account briefs, follow-ups, risk diagnosis, RFP/security responses, or internal graph curation.

Connection Pattern

Gong access is usually configured by an admin with an approved access key and secret or a customer-approved integration process.

Customer setup checklist:

1. Confirm Gong workspace and access policy.
2. Create or approve credentials with the minimum required access.
3. Connect Gong in oper8r or through the managed deployment process.
4. Import a limited set of calls first.
5. Validate transcript quality and participant mapping.
6. Expand to target teams, accounts, or date ranges.

Data Used

oper8r can use:

• Calls.
• Call transcripts.
• Call participants.
• Call dates and titles.
• Account or company references.
• Conversation themes and commitments.

Example Workflow

Prepare a renewal brief for Acme using CRM context and the last
three Gong calls. Include customer objections, product asks,
open commitments, and next actions with citations.

Graph Curation Examples

Source-backed call facts can be added to the employee graph when durable enough:

{
  "source": {
    "provider": "gong",
    "id": "778899",
    "type": "call"
  },
  "fact": {
    "relation": "raised_risk",
    "description": "Acme raised implementation timeline risk during the May renewal call.",
    "validAt": "2026-05-14T18:30:00Z"
  }
}

Avoid storing raw access keys, secrets, or entire transcripts as graph facts.

Limitations

• Transcript quality depends on the recording and speaker separation.
• Sensitive calls may need to be excluded.
• Some outputs require human review before customer use.
• Gong records should be joined to CRM accounts with stable IDs where possible.

Related Docs

• Call Recordings
• CRM
• MCP Tools