Airtable Is Now Live: AI Agents That Keep Your Bases Current

Airtable just joined the catalog. Connect it and your AI employee works in your bases the way a teammate does: it picks up the records assigned to it, sorts what comes in through your forms, keeps status fields current, and comments where your team works. Rows pile up and fields go stale because keeping a base current is nobody's main job. With AI agents for Airtable, it becomes someone's.

Below is what it can do, three setups to start with, and how the connection works. The AI agents for Airtable page has the overview, and the Airtable help page has every step and permission.

What your AI employee can do in Airtable

• Records assigned to it. Set a person field, like an assignee or an owner, to your AI employee's account, and it reads the record and its comments, does the work its tools allow, updates the status and comments with what it did.
• Finding and updating records. It finds records by words in them, by any field, through a view or with a formula, and reads a record with all its fields. It adds, updates and deletes records, up to 50 at a time, and matches on a field like an email or an order number, so nothing is entered twice.
• Every kind of field. Text, numbers, checkboxes, dates, selects, people, links to other records and files. Fields Airtable computes itself, like formulas and lookups, it reads but never writes.
• Form submissions. It reads each new submission, fills in what's missing from your other tools, sets the right status or owner, and flags what needs a person.
• Comments and mentions. It reads the conversation on a record, comments and replies, and mentions the person who needs to act, so they're notified in Airtable. It can also edit or remove its own comments.
• Files. It reads the PDFs, documents, spreadsheets and images attached to a record, and attaches the files it produces, up to 5 MB each.
• Bases, tables and fields. It knows how your bases are built, and adds bases, tables and fields when the work needs a new place to live. It can also rename tables and fields and change a formula. Airtable doesn't let apps delete tables or fields, or add computed ones like formulas and lookups: a person does that in Airtable.

Three setups to start with

• Requests and feedback. Customer requests arrive through an Airtable form. Switch on the reaction to form submissions, and your AI employee reads each one, adds the account details from the CRM it also works in, like HubSpot or Pipedrive, tags the topic, sets a priority, and assigns it to the right person with a comment that sums it up. Anyone with the form's link can fill it in, so it treats the answers as information, never as instructions.
• Content calendars. Each piece of content is a record with a status and an owner. Make your AI employee the owner of a piece, and it writes the draft, attaches it to the record, moves the status on, and mentions the reviewer.
• Hiring pipelines. Applications land in a base. With the reaction to new records on, your AI employee reads the attached CVs, fills in each candidate's details, flags who matches the role, and keeps each stage's status current for the hiring team. Say in the reaction's instruction which table holds the applications, since it fires for the whole base.

How the connection works

You connect Airtable from your AI employee's Tools tab: choose Airtable, click Sign in with Airtable and sign in with the account your AI employee should use, yours or one of its own. Airtable then asks which bases to share. Add each base, or a whole workspace, the employee should reach, and allow AgentTeams. The wizard checks the connection and switches on the default reaction. To share more bases later, or fewer, open Airtable's Account settings, then Integrations.

Your AI employee works as the Airtable user who signs in. Records whose person field names that user go to the employee, and the records and comments it writes carry that user's name. An account of its own, with the employee's name, is the cleanest choice, because teammates can then assign it records like anyone else. Editor access is enough to work with records, and it reaches only the bases you share, as far as that account's access goes.

One reaction is on from the start: a record assigned to your AI employee, whether a teammate set the person field or an Airtable automation did. On the Tasks page you can also switch on reactions to form submissions, new records and changed records. Many records added at once, like an import, reach it as one event, not one each. For your AI employee to hear about changes on its own, one of your AI employees has to be connected with an account that is a creator of the base, because Airtable lets only creators set up the notifications we use. One is enough: every AI employee whose account reaches the base then hears it.

Common questions about AI agents for Airtable

• Will it change records on its own? You decide. Every change it wants to make in Airtable goes through a review step first, and your company's rules decide which changes need a person to approve them. Start strict and loosen it per action once the updates look right. The guardrails guide shows how teams usually stage it.
• Will it clash with our Airtable automations? No, they work well together. Airtable's automations handle fixed rules, and your AI employee handles the judgment: reading what came in, deciding what it means, and writing it up. It never reacts to its own changes, even when an automation acts on a record it made, so one update can't set off another.
• Does it answer when someone mentions it in a comment? Not on its own. Airtable doesn't tell apps about comments, and emails the mention to the employee's address instead. Your AI employee reads and writes comments whenever it works on a record, and a person field set to its account is how a teammate hands it work.
• Which Airtable plan do we need? Any plan, including the free one. On the Free plan, a workspace takes 1,000 requests a month from connected apps, and everything your AI employee does in its bases counts toward them, so busy bases are better on a paid plan.
• How do we stop it? Disconnect Airtable on the employee's Tools tab, and it stops working in Airtable at once. Then remove AgentTeams in Airtable under Account, Integrations, because Airtable gives apps no way to end their own access. What it already wrote stays in place.

Where this fits

Airtable joins Notion and Asana in the integrations catalog, so wherever your team keeps its work (a base, a doc or a project), your AI employee can work there too. The connection pays off most next to the tools where your details start: when your AI employee also works in your inbox, your CRM or Slack, it fills in a record's gaps from there. Nobody copies details into the base by hand anymore.

Ready to hand off the base upkeep? Give your AI employee an Airtable account of its own, then open its Tools tab and connect Airtable. New to AgentTeams? Start with the first-agent onboarding guide.