Connect Airtable to Codex
Give Codex governed access to Airtable’s 46 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Airtable to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Approve Airtable in Runlayer
Add Airtable 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, Airtable’s 46 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 Airtable
Each user signs in to Airtable with OAuth. Runlayer keeps the tokens out of the client’s configuration.
- 4
Use Airtable from Codex
Airtable’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
46 Airtable tools in Codex
Runlayer policy decides which of these Codex users can call. 6 read data only and 1 can change or delete data.
Analyze table
Run statistical operations (count, sum, average, min, max, etc.) on an Airtable table, optionally grouped by columns and filtered.
Create automation
Creates and validates one automation in a base: a trigger plus ordered nodes — action nodes, repeatingGroup (run inner nodes once per item), and conditionalGroup (if/else-if/else branches).
Create base
Creates a new Airtable base with the specified tables and fields.
Create field
Creates a new field in an existing Airtable table.
Create interface
Creates a new interface within a base.
Create page
Creates a new page.
Create record comment
Creates a comment on a specific Airtable record.
Create records for table
Creates new records in an Airtable table.
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 Airtable 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