Integrations · Airtable
A Guild agent reads, creates, updates, searches, and deletes Airtable records, manages table structure, and posts comments without any credential ever reaching agent code. Guild injects the Airtable API key server-side through its credential proxy, so secrets stay out of prompts, containers, and agent state. Credential policies let you restrict which operations and resources each agent can reach, and every request is auditable.
Book a demo
See how teams govern agents that use Airtable.
Talk to sales
Get access to Guild, then connect Airtable to your first agent.
What the Airtable integration exposes
The tools cover base discovery, schema inspection, and full record lifecycle operations including filtered list and search queries. Additional tools handle table and field management, letting an agent rename tables, change field descriptions, and add new fields. Comment tools let agents read and post comments on individual records. Usepick() with the airtable_ prefix to include only the tools a given agent needs.
How it works
1
Open credentials and connect
In Guild, go to Access & setup > Credentials, click Connect, and select airtable. Paste your Airtable personal access token into the API Key field.
2
Scope the credential
By default the credential serves every workspace the account owns. You can scope it to one workspace, to yourself as a member, or dedicate it to a single agent. See Credentials for the full scoping options.
3
Import and spread the tools
Import
AirtableTools from the guildai~airtable package and spread it into your agent’s tools object. Use pick() from the SDK tools reference to include only the specific operations your agent requires.Why Airtable access needs governing
Airtable credentials can read and mutate records, delete data, and alter table structure across every base the token can reach. Guild stores the API key and adds it to requests server-side through its credential proxy, so agent code, prompts, and containers never see it. You can scope a credential to a single workspace, a single member, or one agent, keeping a shared token from reaching agents that do not need it. Credential policies let you write ALLOW and DENY rules that the proxy enforces before any request leaves Guild. A DENY rule onairtable_delete_record blocks deletions for every agent using that credential unless a tighter scoped rule says otherwise. Scoping rules to specific agents lets one agent search records read-only while another posts comments, all on the same connected credential. Without policies, the default posture is allow-all; deleting the allow-all policy switches the fallback to deny.
About the Airtable integration
Agents can browse Airtable bases and inspect their schemas, then read, create, update, search, and delete records across any accessible table. They can also manage table structure by adding or renaming fields and tables, and read or post comments on individual records. The integration isguildai~airtable.
Authentication
- Type: API key
- Header: Guild sends the key as a bearer token in the
Authorizationheader
Setup
1
Connect Airtable
In Guild, go to Access & setup > Credentials, click Connect, select airtable, and paste the key into API Key.
Usage
Selecting specific tools
Tools are named with theairtable_ prefix. Use pick() to include only what your agent needs.
Tools
Tools in the latest published version ofguildai~airtable:
Frequently asked questions
Does the agent ever see my Airtable API key?
Does the agent ever see my Airtable API key?
No. Guild’s credential proxy injects the key as a bearer token in the Authorization header server-side. The key never enters the agent’s code, container, prompt, or state.
Can I stop an agent from deleting records while still letting it read them?
Can I stop an agent from deleting records while still letting it read them?
Yes. Add a DENY rule for
airtable_delete_record and an ALLOW rule for the read operations you want. The proxy enforces DENY rules before ALLOW rules, so deletions are blocked regardless of any other matching rule. See Credential policies for syntax.Does the integration support webhook events from Airtable?
Does the integration support webhook events from Airtable?
Not yet. The catalog entry for
guildai~airtable lists no webhook events, so the integration does not receive push notifications from Airtable.Can I use a different Airtable account in one workspace than in the rest of my organization?
Can I use a different Airtable account in one workspace than in the rest of my organization?
Yes. Connect a second credential scoped to that workspace. Guild resolves credentials in order: a workspace credential takes precedence over the account default, so agents in that workspace use the workspace-scoped token and agents elsewhere use the account credential.
Put a governed agent on Airtable this week
Book a demo
See how teams govern agents that use Airtable.
Talk to sales
Get access to Guild, then connect Airtable to your first agent.