Skip to main content
Integrations · Gong
A Guild agent reads Gong call recordings, retrieves transcripts, manages Engage flows, and updates permission profiles on your behalf. Guild stores the Gong API key server-side and injects it into every request, so agent code never sees the credential. Credential policies let you restrict which Gong operations each agent can call, and every request runs through Guild’s audit trail.

Book a demo

See how teams govern agents that use Gong.

Talk to sales

Get access to Guild, then connect Gong to your first agent.

What the Gong integration exposes

The integration is guildai~gong-openapi and provides tools that cover calls, transcripts, interaction statistics, users, permission profiles, Engage flows, tasks, CRM data, scorecards, meetings, and keyword trackers. Tools follow the gong_openapi_ prefix convention. Use pick() to include only the tools your agent needs.

How it works

1

Open credentials in Guild

Go to Access & setup > Credentials in your Guild account. Click Connect and select gong-openapi.
2

Paste your Gong key

Enter your Gong access key and secret, base64-encoded as key:secret, into the API Key field. Guild sends it as Authorization: Basic <key> on every request.
3

Scope the credential

Choose account, workspace, member, or agent scope when connecting. See Credentials for the full scoping options and how Guild resolves which credential to use.

Why Gong access needs governing

Gong holds sensitive call recordings, transcripts, and CRM data, so uncontrolled agent access can expose confidential conversations or allow unintended mutations such as purging email addresses or deleting meetings. Guild addresses this through credential policies: you write ALLOW and DENY rules that Guild’s credential proxy enforces before any request leaves Guild. Rules can target specific gong_openapi_ operations, scope access to particular agents or workspaces, and block HTTP methods to enforce read-only access. Credentials are injected server-side, so agent code never handles the Gong API key directly. You can restrict a workspace to its own credentials to prevent account-level shared keys from reaching agents in that workspace. Because enforcement happens inside the proxy, agents cannot bypass policy regardless of what instructions they receive.

About the Gong integration

Agents can access Gong call recordings, transcripts, and interaction statistics, as well as manage users and permission profiles. They can work with Engage flows by assigning prospects, searching flows, and managing tasks. CRM data, scorecards, and meeting management are also available through the integration. The integration is guildai~gong-openapi.

Authentication

  • Type: API key
  • Header: Guild sends the key as Authorization: Basic <key>

Setup

1

Connect Gong

In Guild, go to Access & setup > Credentials, click Connect, select gong-openapi, and paste the key into API Key.
See Credentials for workspace, member, and agent-scoped credentials.

Usage

Selecting specific tools

Tools are named with the gong_openapi_ prefix. Use pick() to include only what your agent needs.

Tools

Tools in the latest published version of guildai~gong-openapi:

Frequently asked questions

Yes. Write a credential policy that allows only the read-oriented gong_openapi_ operations and adds a DENY rule for operations such as gong_openapi_delete_meeting or gong_openapi_purge_email_address. You can also restrict the policy to GET methods using the methods resource constraint. See Credential policies for the full rule syntax.
No. The catalog entry for guildai~gong-openapi lists no webhook events, so the integration does not support event-driven triggers from Gong.
Yes. Connect a credential scoped to a single agent from the installed agent’s detail page using the Dedicated to this agent option. That credential is used ahead of any workspace or account credential when that agent runs. See Credentials for the full resolution order.
Import GongOpenapiTools and pass it through pick() with the tool names you want. Tools follow the gong_openapi_ prefix, so for example you can pick gong_openapi_get_call and gong_openapi_get_call_transcripts without exposing the rest. See Tool sets for usage details.

Put a governed agent on Gong this week

Book a demo

See how teams govern agents that use Gong.

Talk to sales

Get access to Guild, then connect Gong to your first agent.
Also runs on Guild: Affinity · Attio · Brex · Google Ads Read: Docs: Credential policies · Credentials · Tools in agents
Last modified on November 20, 2026