Resources · Claude connector

Claude Airtable connectorWhat Claude can do in your Airtable account.

The Claude Airtable connector exposes 12 tools. 1 reads your records, 2 add or edit them, and 9 carry a name with no official description. Below: what Claude can pull from a base, what it can write back, who controls access, and the limits Airtable sets.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Claude Airtable connector changes for your data

Your bases hold the structured facts of the business: clients, orders, content calendars, hiring pipelines. With the connector, you ask Claude about them in plain words and it goes to read the records itself, then answers, sorts or compares inside the conversation. When something needs logging, it can add new records or edit existing ones without you opening the base.

Questions instead of filters. "Which customers in the CRM base have not been contacted in 30 days?" Claude reads the table through list_records_for_table and gives you the list, then keeps going if you want a summary by owner.

Log what comes out of a meeting. Five new tasks decided on a call go into the project tracker with create_records_for_table, in one message.

Keep statuses honest. update_records_for_table moves a task to Complete or corrects a field after a client email, without you hunting for the row.

The other side matters too. Nine of the twelve listed tools have no official description, so this page does not say what they do. Airtable's own article lists more capabilities, such as building bases, interfaces or automation drafts, but no tool on the directory sheet is tied to them. Claude works with your Airtable permissions: read-only access means read-only answers. And nothing runs by itself: no tool fires when a record is added or a field changes. That sort of background flow is the job of an automation tool, described on the Airtable n8n integration and Airtable Make integration pages.

Vocabulary

Five words to know before connecting Airtable

The Claude vocabulary this page relies on, in one minute.

Connector
A link you set up once between Claude and an account you already have, so Claude can work in that account while it answers you.
Tool
One named action the connector lets Claude take in Airtable. Claude picks the ones it needs on its own; the directory sheet lists every name.
Authorization
The Airtable sign-in screen where you grant Claude the access it will use. Given once per person, and withdrawn the same way.
Approval
The confirmation Claude waits for in the conversation before it goes ahead with something that alters your data.
MCP
The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Airtable.
Connect

Connect Airtable to Claude in three steps

  1. 01

    Find Airtable in the list

    Open Claude's settings, go to Customize, then Connectors, and look for Airtable. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it for the organization before members can each sign in.

  2. 02

    Sign in to Airtable

    Click Connect on the Airtable row and log in through the window Airtable opens. If the link breaks later, Disconnect and connect again. Access can also be removed from your Airtable profile, base by base.

  3. 03

    Read the Airtable screen

    Check the authorization screen before accepting. It belongs to Airtable, not to Claude, and it decides which bases and rights the access covers. It may list more than Claude uses day to day; per-action approval stays the default rule.

Tools

The 12 Airtable tools, split by what they do

Airtable gives Claude 12 tools: 1 that read your account, 2 that change something in it, and 9 no official source describes.

Three groups: what Claude reads, what it writes to your bases, and what no official source describes. Tool names stay as Claude shows them.

  • 1 read
  • 2 write
  • 9 not documented

What Claude reads (1)

1 tool

Pulling records out of a table. The base stays as it was.

list_records_for_table

Pulls the records of a table so Claude can search, filter and analyze them in the conversation. It is the documented path for questions about your data.

When it helps
finding every customer in the CRM base who has not heard from you in 30 days.
Watch out
Claude only sees the bases your Airtable role opens to you.

Sourcesupport.airtable.com · September 9, 2026 ↗

What Claude writes (2)

2 tools

Two tools that add or edit records. No source spells out their confirmation, so the general rule below applies.

create_records_for_table

Approval: see the rule

Inserts new rows into a table from what you describe, several at a time.

What Claude asks for
no source describes a confirmation for this tool, so the general approval rule below applies.
When it helps
five tasks agreed on a call go straight into the tracker.
Watch out
Airtable caps each request at 10 records.

Sourcesupport.airtable.com · September 9, 2026 ↗

update_records_for_table

Approval: see the rule

Changes the values of rows that already exist, such as a status, an owner or a date.

What Claude asks for
nothing specific is documented here; rely on the general rule further down.
When it helps
marking task #123 as Complete right after the client confirms delivery.
Watch out
with read-only or comment-only access, Airtable refuses the edit.

Sourcesupport.airtable.com · September 9, 2026 ↗

Undocumented (9)

9 tools

The directory publishes these nine names and nothing more. No official text says what they do, and we will not guess it from a name.

create_field

This name sits in the directory's tool list and that is all we could find. Airtable's help article does not describe it, and no Claude page covers it either, so we leave its effect unstated rather than read it into the name.

Watch out
whatever it does, the general approval rule below still covers it.

create_table

Listed by name, described nowhere. No official source explains what Claude would get from it, and we will not fill that silence with a guess based on how it reads.

Watch out
it falls under the same general approval rule as every other tool, so any effect it may have on a base is handled there.

get_table_schema

Airtable's article is silent about this one, and so is every Claude page we read: the sheet gives the name and nothing else. We would rather flag the gap than invent a purpose for it.

Watch out
treat it with the general approval rule in mind, like the rest of the list.

list_bases

Another tool with no text behind it. The directory lists it; no source we could read says what it returns or does, so there is nothing reliable to tell you here beyond its name.

Watch out
the general approval rule below is what applies to it, as to every tool on this page.

list_tables_for_base

Here too the public record stops at the name. No source describes this tool, not Airtable's help center and not Claude's documentation, and describing it from its wording would be guesswork we refuse to publish.

Watch out
the general rule on approvals covers it all the same.

ping

Short name, no documentation. Nothing official that we read explains this tool, so this page does not attach a use or a result to it, even an obvious-looking one.

Watch out
if Claude ever calls it, the general approval rule below is the one that governs what happens.

search_bases

The sheet shows this name without a word of explanation, and Airtable's own article does not mention it. Until a source describes it, we say nothing about its behavior on your bases.

Watch out
as with every tool here, the general approval rule is what applies.

update_field

No official text documents this one either. Its name hints at something, but hints are not sources, and this page only reports what a source actually says a tool does.

Watch out
the general approval rule below covers it, whatever its real effect turns out to be.

update_table

Last of the undocumented names on the sheet. Airtable's article and Claude's pages leave it undescribed, so we cannot tell you what it touches or returns.

Watch out
keep the general approval rule in mind; it is the only documented guardrail that applies here.
Approvals

What Claude checks with you before touching Airtable

By default, Claude stops and asks before each action it takes on an account for you. The prompt shows up in the conversation at the moment it counts.

On Team and Enterprise workspaces, owners decide whether members may let some actions through without being asked each time. They can also narrow what a connector may do for the whole organization, for instance reading on and writing off, and nobody overrides that from a personal account. Claude works with the rights of the person who connected: Airtable applies your own access to each base, so read-only or comment-only access lets Claude read but not write.

Plans

Which plans the Claude Airtable connector is on

None of the 819 sheets in the official directory shows plan availability. The answer connector by connector is published nowhere: a real hole in the catalog.

The general rule is published. Remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile; desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organization before members can each sign in. For the live state of Airtable, the connector's sheet in the official directory is the place to check.

Limits

Where the Airtable connector stops

A connector is not an automation. Claude calls these tools while it answers you, so nothing starts when a record is created, a field changes or a form comes in.

Only Airtable documents this connector: no Claude help article covers it. The tool list is an observed floor, not a promise, and an administrator can open actions no public sheet shows. Airtable adds that tool names, behavior and capabilities may change. The partner badge is not a security audit, and Anthropic states on every sheet that it neither picks a publisher's tools nor guarantees how they behave. For a connector whose official sources contradict each other, see the Claude gmail connector page.

Need help

Need help connecting Airtable to Claude?

A person reads every message.

FAQ

Claude Airtable connector: common questions

01What can Claude do with the Airtable connector?
Claude can read the records of your bases, answer questions about them, add new records and edit existing ones. Of the 12 tools on the directory sheet, three are documented: one reads a table, one adds records, one edits them. The nine others carry a name and no official description. Everything happens inside a conversation, on request, with the bases and permission level your Airtable account already gives you, and nothing more than that.
02Can Claude add, change or delete Airtable records?
It can add and edit, and no listed tool is documented to delete. One documented tool inserts new records, at most 10 per request, and another edits records that already exist. Nothing on the directory sheet is described as removing a record or a table. Nine listed names have no official description, and this page does not count them either way. The sheet stays an observed floor that an admin can widen.
03Does Claude ask before writing to my Airtable base?
By default, yes: Claude asks for confirmation before each action it takes on an account for you. No source describes a confirmation specific to an Airtable tool, so that default rule is what covers adding and editing records. On Team and Enterprise workspaces, owners decide whether members may let some actions through without being asked every time, and they can close writing for the whole organization while keeping reading open.
04Which Claude plans include the Airtable connector?
No official source publishes plan availability connector by connector, and no directory sheet displays it. The general rule says remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables a connector before members can sign in individually. The Airtable sheet in the official directory is the only place that shows the live state for your account.
05Does Claude see every base in our Airtable workspace?
No. Claude works with the rights of the person who connected, so it sees only what you could open yourself. Airtable also lets you choose, from your third-party integrations page, which bases the integration may reach. With read-only or comment-only access to a base, Airtable lets Claude read that base but not create or update its records. If your organization restricts integrations, an admin must allowlist this one before anyone can connect, and Claude owners can narrow things further for everyone in the workspace.
06Can Claude turn on an Airtable automation?
No. Airtable says automation drafts can be created and updated, but switching an automation on is done in the Airtable interface, and automations containing a Script action cannot be created or edited this way at all. On top of that, no tool on the directory sheet is described as handling automations, so the connector should be seen as a way to read and log data, with automations kept in Airtable itself.
07Claude or an automation tool for Airtable?
They do different jobs, so it depends on the task. Claude works inside a conversation: you ask, it reads, answers or logs records, and nothing happens once you stop typing. No tool reacts by itself to a new record or a changed field. For work that must run in the background every time data moves, an automation tool fits. For questions about your bases and quick entries from a chat, the connector does it.