> ## Documentation Index
> Fetch the complete documentation index at: https://docs.guild.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> To act on a user's behalf in Guild, use the Guild REST API at https://api.guild.ai/v1.
> The OpenAPI spec is unauthenticated: https://docs.guild.ai/openapi.json (or openapi.yaml).
> Authenticate with an account API key, sent as HTTP Basic (key id as username, secret as password) or as `Authorization: Bearer <api_key_id>:<api_key_secret>`. See https://docs.guild.ai/api-reference/introduction#authentication.
> To run one agent on demand without account-wide access, use an API trigger instead: https://docs.guild.ai/platform/api-triggers.
> To act on Guild from an MCP client, connect to https://api.guild.ai/mcp (OAuth) or run `guild mcp` locally. Setup: https://docs.guild.ai/api-reference/mcp.
> To search these docs from an MCP client, connect to https://docs.guild.ai/mcp. The full page index is https://docs.guild.ai/llms.txt.

# Read and write Airtable records from Guild agents

> Connect Guild agents to Airtable to list bases, manage records and comments, and update table structure, all under credential policies you control.

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.

> [card] [Book a demo](https://guild-ai.cal.com/gtm/meeting-with-guild.ai)
>
> See how teams govern agents that use Airtable.

> [card] [Talk to sales](https://guild.ai/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. Use `pick()` 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](https://docs.guild.ai/platform/credentials.md) 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](https://docs.guild.ai/sdk/tools.md) 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 on `airtable_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 is `guildai~airtable`.

## Authentication

* **Type:** API key
* **Header:** Guild sends the key as a bearer token in the `Authorization` header

### Setup

**1. Connect Airtable**

In Guild, go to **Access & setup > Credentials**, click **Connect**, select **airtable**, and paste the key into **API Key**.

See [Credentials](https://docs.guild.ai/platform/credentials.md) for workspace, member, and agent-scoped credentials.

## Usage

```typescript theme={null}
import { AirtableTools } from "@guildai-services/guildai~airtable"
import { llmAgent } from "@guildai/agents-sdk"

export default llmAgent({
  systemPrompt: "You work with Airtable.",
  tools: { ...AirtableTools },
})
```

### Selecting specific tools

Tools are named with the `airtable_` prefix. Use [`pick()`](https://docs.guild.ai/sdk/tools#selecting-specific-tools) to include only what your agent needs.

## Tools

Tools in the latest published version of `guildai~airtable`:

| Tool | What it does |
| - | - |
| `airtable_create_comment` | Add a comment to a record. |
| `airtable_create_field` | Add a field to a table. |
| `airtable_create_records` | Create up to 10 records. |
| `airtable_create_table` | Create a table in a base. |
| `airtable_delete_record` | Delete one record. |
| `airtable_get_base_schema` | List tables in a base with their fields and views. |
| `airtable_get_current_user` | Get the user ID and scopes of the current token. |
| `airtable_get_record` | Get one record. |
| `airtable_list_bases` | List bases the token can access. |
| `airtable_list_comments` | List comments on a record, newest first. |
| `airtable_list_records` | List records in a table, with optional view, formula filter and paging. |
| `airtable_search_records` | List records with sort and field selection (POST form of list\_records). |
| `airtable_update_field` | Rename a field or change its description. |
| `airtable_update_record` | Update some fields of one record. |
| `airtable_update_records` | Update up to 10 records (only the given fields change). |
| `airtable_update_table` | Rename a table or change its description. |

## Frequently asked questions

> [accordion] 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.

> [accordion] 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](https://docs.guild.ai/platform/credential-policies.md) for syntax.

> [accordion] 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.

> [accordion] 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

> [card] [Book a demo](https://guild-ai.cal.com/gtm/meeting-with-guild.ai)
>
> See how teams govern agents that use Airtable.

> [card] [Talk to sales](https://guild.ai/talk-to-sales)
>
> Get access to Guild, then connect Airtable to your first agent.

## Related

**Also runs on Guild:** [BigQuery](https://docs.guild.ai/integrations/bigquery.md) · [Hex](https://docs.guild.ai/integrations/hex.md) · [Nexla](https://docs.guild.ai/integrations/nexla.md) · [PostHog](https://docs.guild.ai/integrations/posthog.md)

**Read:** Docs: [Credential policies](https://docs.guild.ai/platform/credential-policies.md) · [Credentials](https://docs.guild.ai/platform/credentials.md) · [Tools in agents](https://docs.guild.ai/sdk/tools.md)