Connect Gong to Codex
Give Codex governed access to Gong’s 22 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Gong to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Approve Gong in Runlayer
Add Gong from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Codex to Runlayer
Runlayer’s CLI adds the Runlayer Plugin to Codex’s local plugin marketplace, and users then enable it in Codex. With direct tool listing turned on for your deployment, Gong’s 22 tools show up in Codex’s own tool list (Codex 0.122 or newer, installed through the Runlayer CLI).
Codex setup guide - 3
Sign in to Gong
Sign in the way Gong requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Gong from Codex
Gong’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
22 Gong tools in Codex
Runlayer policy decides which of these Codex users can call.
Assign prospects
Assign prospects (contacts or leads from CRM) to a Gong Engage flow.
Find by email
Find all references to an email address in Gong.
Find by phone
Find all references to a phone number in Gong.
Get call
Get detailed information about a specific Gong call by its ID.
Get call slim
Get a Gong call by ID (slim response).
Get calls in folder
Get a list of calls saved in a specific library folder.
Get library folders
Get the structure of public library folders in Gong.
Get transcripts
Retrieve transcripts for Gong calls.
Control
What Runlayer can see and stop in Codex
Some controls apply to every client at the gateway. Others depend on what Codex exposes to Runlayer.
Gateway policy (available)
Every Gong call from Codex passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Codex as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Stop a call before it runs (available)
Runlayer can deny a tool call or permission request before Codex runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before Codex’s model sees it.
Redact output in place (not available)
Codex cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.
Frequently asked questions
Connect more