Airtable ships two things that both get called an AI agent, and they do genuinely different jobs. Confusing them is the most common reason a promising automation stalls: people ask the app builder to do per-record work, or they try to reshape an app with something designed to fill in a column. Sorting out which is which takes about two minutes and saves a fortnight.
The three ways to run an AI agent on Airtable
Two of the three are Airtable's own, and the split between them is the thing worth understanding before you compare anything else.
| Route | What it is for | Works at the level of | Reaches beyond Airtable? |
|---|---|---|---|
| Omni | Building and changing apps by describing them | The app | Includes web research, but builds inside Airtable |
| Field Agents | Research, analysis and content generation per record | The row or field | No, they run inside your apps |
| External agent platform | Work that starts on a record and ends elsewhere | The whole process | Yes, it holds credentials for each tool |
What Omni and Field Agents each actually do
Airtable is reasonably clear about this on its own pages, but the distinction gets flattened everywhere else, so it is worth restating in the vendor's language.
Omni is described by Airtable as "your expert AI app builder, data analyst, and web researcher that takes the work out of your workflow", and as a "sidekick who seamlessly integrates with your data, information, and insights" to build "production-ready apps at prototype speed". Airtable's own FAQ calls it "Airtable's conversational AI builder" and says no technical experience is needed. So Omni is conversational, and its output is an app or an analysis.
Field Agents are described as "your own personal AI-powered researchers, analysts, and content creators", with examples including generating campaign-ready content and triaging feedback "by detecting sentiment and routing issues automatically". Airtable's platform navigation describes deploying "thousands of agents inside your apps". So Field Agents are the workers, and their output is a filled field on a record.
The test we would apply: if your sentence starts with "for every record, ..." you want a Field Agent. If it starts with "I need a tool that ...", you want Omni. If it starts with "when this record changes, go and ..." and the going-and-doing happens in another product, you want neither, and you want something that can hold credentials for both.
What it costs before AI
Airtable states plainly that plans are charged per seat, and that on the Free plan all users are free. That per-seat base is the number to start from, because AI usage is an additional line rather than an included allowance you can ignore.
| Plan | Price | Notes from Airtable |
|---|---|---|
| Free | No charge | Airtable describes it as the key building blocks to start building applications, with all users free |
| Team | $20 per user per month, billed annually | Positioned for teams that like the Free plan but need more capacity |
| Business | $45 per user per month | One of two plans Airtable positions for large company usage |
| Enterprise Scale | Quoted by sales | The other large-company plan |
Running the arithmetic on those published figures: a six-person ops team on Team is $120 a month, and the same team on Business is $270, before any AI usage at all. The pattern is the familiar one for per-seat tools, which is that the bill tracks how many people can open the base rather than how much automated work you actually run. That matters here more than usual, because a base often has a handful of people doing the automating and a long tail of people who just need to look at it.
Which Airtable work is actually worth automating
Airtable rewards a specific shape of automation, and it is unusually easy to spot: work you would otherwise repeat once per row.
- Record enrichment. Filling in what is not in the base yet, such as company details against a list of leads.
- Data cleanup and normalisation. Inconsistent casing, split names, four spellings of the same city, dates stored as text.
- Classification and tagging. Sentiment on feedback, category on an inbound request, priority on a bug.
- Summarising long text. Turning a wall of notes into a column somebody can actually scan.
- Routing. Assigning the record to the right owner based on what is in it.
The work to keep behind a human is anything destructive: deleting records, merging duplicates, and bulk overwriting a field across a view. A base is very often the only copy of that data, and an overwrite does not announce itself. By the time anyone notices the enrichment ran against the wrong view, the original values are gone and the revision history is the only route back, if it goes back far enough.
Set the permission model before you connect anything
Decide what the agent may change before you decide which agent to use, because in a database the blast radius of "apply" is much larger than in a helpdesk or a task tracker.
- Let it write to new or empty fields. Enrichment into a blank column is the safest possible starting point.
- Prefer a new field over overwriting an existing one. Write the AI value next to the human value and compare before you switch over.
- Scope it to a view, and check the view. Most enrichment accidents are a correct agent pointed at the wrong set of rows.
- Never grant delete or merge unattended. Propose duplicates, let a person confirm the merge.
- Run the first batch small. Twenty records, read them all, then scale. This costs an hour and catches the systematic errors.
Task-by-task guides
The two Airtable jobs we see most often, each written up in full.
- AI agent for Airtable record enrichment, on filling in what the base does not know yet.
- AI agent for Airtable data entry cleanup, on normalising a base that grew organically.
- Notion AI agent, if your team keeps its documents in one tool and its records in another.
How to choose without a long evaluation
Three questions and you are done.
- Is the unit of work a record or an app? Records mean Field Agents. Building or reshaping means Omni. Getting this right first is most of the decision.
- Does the process finish inside Airtable? If the record update has to trigger an email, a document or an invoice, no Airtable-native agent can follow it there, and you want a platform that holds credentials for both ends.
- How many seats versus how many automators? Per-seat pricing charges for everyone who can open the base, including the people who only ever read it.
Vendor AI inside a database tool is tied to seats, so the cost tracks how many people can open the base rather than how much work you automate. An external platform priced by the work is usually cheaper when a couple of people do the automating for everyone else. Gravity has a free tier at $0 a month for one agent, and paid plans from $20 a month with a lot of usage included; buy more usage if you run out. New to this? Start with what is an AI agent, or see AI agents for every profession for the work mapped by role.
Frequently asked questions
Is there an AI agent for Airtable?
Yes, and Airtable ships two different things under that heading. Omni is what Airtable calls its conversational AI builder, described on its own AI page as an expert AI app builder, data analyst and web researcher. Field Agents are the per-record workers, described as AI-powered researchers, analysts and content creators that run inside the apps you build. The third route is an external agent platform that connects Airtable to the tools your work also touches, which is what you need when a record update has to end somewhere else.
What is Airtable Omni?
Omni is Airtable's conversational AI builder. Airtable describes it as your expert AI app builder, data analyst and web researcher, and as a sidekick that integrates with your data, information and insights to build production-ready apps at prototype speed. Airtable also states that no technical experience is needed to use it. The practical framing: Omni is who you talk to when you want to build or change an app, not the thing that processes ten thousand rows once the app exists.
What are Airtable Field Agents?
Field Agents are Airtable's per-record AI workers. Airtable describes them as your own personal AI-powered researchers, analysts and content creators, and gives examples such as producing campaign-ready content and triaging feedback by detecting sentiment and routing issues automatically. They run inside the apps you build, and Airtable's platform pages talk about deploying thousands of agents inside your apps. This is the route for column-shaped work: enrich this record, classify this row, summarise this entry.
How much does Airtable cost in 2026?
Airtable's pricing page lists a Free plan at no cost, a Team plan at $20 per user per month when billed annually, and a Business plan at $45 per user per month, with Enterprise Scale quoted by sales. Airtable states that plans are charged per seat and that all users are free on the Free plan. AI capabilities sit on top of that seat cost, so budget the per-seat figure and the AI usage as two separate lines rather than one.
What Airtable work should an AI agent handle first?
Column-shaped work, meaning anything you would otherwise do once per row: enriching records with information that is not in the base yet, cleaning and normalising messy fields, classifying or tagging entries, summarising long text into a usable column, and routing records to the right owner. Keep deletion, merging and bulk overwrites behind a human, because a base is often the only copy of that data and an overwritten field has no undo that anybody will notice in time.
Do I need Omni to run an AI agent on Airtable?
No. Omni is the fastest route when you are building or reshaping the app itself and everything lives in Airtable. If the work starts on a record and finishes in an email, a document or a billing tool, an external agent platform that holds credentials for all of those is the better fit, and it is priced by the work rather than by how many Airtable seats your team holds. Airtable-only agents cannot reach the system where the rest of the process happens.