Connect Salesforce to Codex
Give Codex governed access to Salesforce’s 21 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Salesforce to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Approve Salesforce in Runlayer
Add Salesforce 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, Salesforce’s 21 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 Salesforce
Sign in the way Salesforce requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Salesforce from Codex
Salesforce’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
21 Salesforce tools in Codex
Runlayer policy decides which of these Codex users can call. 7 read data only and 1 can change or delete data.
Create record
Create a new Salesforce record.
Delete record
Delete a Salesforce record by ID.
Describe object
Get detailed metadata for a specific Salesforce sObject including all fields, their types, picklist values, relationships, and constraints.
Get limits
Get the org's API usage limits including daily API calls, data storage, file storage, and other governor limits.
Get record
Retrieve a single Salesforce record by its ID.
List objects
List all sObjects (standard and custom objects) available in the Salesforce org.
Query
Execute a SOQL (Salesforce Object Query Language) query.
Query more
Retrieve the next page of results from a SOQL query.
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 Salesforce 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