Connect Airtable to Windsurf
Give Windsurf governed access to Airtable’s 46 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Airtable to Windsurf in four steps
Admins approve the server once. Everyone in Windsurf 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 Windsurf to Runlayer
Users add the Runlayer Plugin to Windsurf by following Runlayer’s setup guide. Windsurf reaches Airtable’s 46 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Windsurf 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 Windsurf
Airtable’s approved tools appear in Windsurf. Every call is checked against policy and recorded.
Tools
46 Airtable tools in Windsurf
Runlayer policy decides which of these Windsurf 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 Windsurf
Some controls apply to every client at the gateway. Others depend on what Windsurf exposes to Runlayer.
Gateway policy (available)
Every Airtable call from Windsurf passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Windsurf 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 before Windsurf runs it.
Block output after it runs (not available)
Windsurf ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.
Redact output in place (not available)
Windsurf has no way to receive replacement output, so Runlayer cannot mask it. The gateway still applies policy to the call.
In Windsurf
- Enforcement needs Windsurf 1.12.31 or newer.
- When Runlayer denies a call, Windsurf shows the reason to the user; Runlayer cannot adjust the call’s inputs.
Frequently asked questions
Connect more