Connect Airtable to GitHub Copilot CLI
Give GitHub Copilot CLI governed access to Airtable’s 46 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Airtable to GitHub Copilot CLI in four steps
Admins approve the server once. Everyone in GitHub Copilot CLI 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 GitHub Copilot CLI to Runlayer
Users add the Runlayer Plugin to GitHub Copilot CLI by following Runlayer’s setup guide. GitHub Copilot CLI reaches Airtable’s 46 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
GitHub Copilot CLI 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 GitHub Copilot CLI
Airtable’s approved tools appear in GitHub Copilot CLI. Every call is checked against policy and recorded.
Tools
46 Airtable tools in GitHub Copilot CLI
Runlayer policy decides which of these GitHub Copilot CLI 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 GitHub Copilot CLI
Some controls apply to every client at the gateway. Others depend on what GitHub Copilot CLI exposes to Runlayer.
Gateway policy (available)
Every Airtable call from GitHub Copilot CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, GitHub Copilot CLI 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 GitHub Copilot CLI runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before GitHub Copilot CLI’s model sees it.
Redact output in place (available)
Runlayer can mask sensitive parts of a successful tool’s output in GitHub Copilot CLI and pass the rest through.
In GitHub Copilot CLI
- When a tool fails, Runlayer records the error but cannot replace it.
Frequently asked questions
Connect more
