Guides: Airtable features explained

AI credits

AI credits are a metered unit used to access Airtable’s built-in AI features. Each AI-powered action consumes credits from the workspace balance, and workspace admins can view, manage, and purchase additional credits.

AI model selection for Field Agents

AI model selection for Field Agents lets you specify which AI model a Field Agent uses when executing its tasks. You can configure model-specific settings for each agent so prompts and responses are processed with the chosen model.

Airtable scripts: Inputs and Outputs

Scripts can declare configurable input variables (set in the Scripting app’s Input variables UI and read at runtime via input.config()) so scripts can access user-provided values. Scripts send results to the Scripting app’s output pane using the output API (for example output.markdown(), output.table(), and output.inspect()) to display text, tables, and interactive content.

Airtable Web API

The Airtable Web API is a RESTful HTTP API that exposes the tables, fields, and records in a specific Airtable base and provides endpoints for creating, reading, updating, and deleting records. Each base has an auto-generated API documentation page and the API supports authentication, pagination, filtering/sorting via query parameters, and batch operations.

Android app

The Airtable Android app lets you access your bases from Android devices and view, create, and edit records. You can attach files or photos, add comments, and switch between common base views such as grid, calendar, Kanban, and form.

Annotating attachment files

Annotating attachment files lets users open images and PDFs in the attachment preview and add drawings, text, shapes, highlights, and comments directly on the file. Annotated files are saved back to the record as an updated attachment.

Attach files to comments

Attach files to comments lets you add files (images, documents, etc.) directly within a record's comment thread. Attached files appear inline in the comment and are stored with the record so they can be accessed from the activity feed.

Attachment versioning

Attachment versioning (Proofing Versions) lets an attachment field store multiple iterations of the same file, automatically numbering each upload as a new version and preserving separate annotations and comments for each version. You can open a version history in the proofing viewer to navigate and compare versions side‑by‑side, upload new versions to the same field, download versions with or without annotations, and enabling it requires setting the attachment field’s Format to Versions.

Automation action: Create record

Creates a new record in a specified table when the automation runs. You choose the target table and provide field values—either static or mapped from the trigger or earlier actions—to populate the new record.

Automation action: Find records

The Find records automation action searches a table for records that meet specified conditions or that are in a selected view and returns up to 1,000 matching records per automation run; when searching by view, results are returned in that view’s sort order.

Automation action: Send email

The Send email automation action sends an email to one or more specified recipients when the automation runs. You can configure recipients (To/CC/BCC), subject and body (including dynamic field values from the triggering record) and attach files to the message.

Automation action: Sort list

The "Sort list" automation action accepts a record array from a preceding "Find records" step and returns that list sorted by one or more configured field conditions. It only accepts Find records outputs (not script outputs), does not support lookup, multi-select, linked-record/foreign-key, attachment, button, or multi-user fields, and records missing the chosen sort-field value always appear last.

Automation action: Update record

The Update record automation action modifies one or more fields on a specified record when the automation runs. You identify the record by providing a Record ID (from the trigger or a previous action like Find records) and set new field values using static input or variables from earlier steps.

Automation actions: Facebook Pages

The Facebook Pages automation action posts content from Airtable to a connected Facebook Page when an automation runs. You configure it by connecting a Facebook account, selecting the Page, and specifying the post content and any optional media or link fields to publish.

Automation actions: Generate image with AI

The "Generate image with AI" automation action uses a text prompt (which can include record field values) to create an AI-generated image and attach the resulting image file or image URL to a specified attachment field or return it as the action result. Configure the prompt and target field in the automation so images are produced and stored automatically when the automation runs.

Automation actions: Generate structure data with AI

The "Generate structured data" automation action lets you supply a prompt and an output JSON schema so Airtable's AI returns data in defined types (string, number, boolean, array, object, enum) that can be referenced by later automation steps (including looping over arrays for repeating actions). You configure the prompt, output schema, model/randomness, and an “Allow AI to access the Internet” toggle, and the action enforces limits such as a maximum of four levels of array/object nesting and model-dependent word/response size constraints.

Automation actions: Generate text with AI

The "Generate with AI" automation action uses Airtable’s Omni AI to generate text from a plain-text prompt within an automation, letting you create or update field values, produce structured outputs (e.g., lists/arrays), or query data and pass the generated text to subsequent automation steps.

Automation actions: GitHub Issues

Automation action "GitHub Issues" lets an Airtable automation create a new issue or update an existing issue in a specified GitHub repository. You can populate issue fields (such as title and body) from Airtable fields and specify the repository and issue number for updates.

Automation actions: Gmail

The Gmail: Send email automation action sends messages from a connected Google account as part of an Airtable automation and requires the user to connect and authorize their Google account; this action is available on paid workspaces. You can populate To/CC/BCC/Reply‑to with comma-separated addresses, use a custom From name or a verified From address, include Markdown or attachments, and the action is subject to Google-specific limits (100 total recipients per action and a 1 email/second send rate).

Automation actions: Google Calendar

Airtable's Google Calendar automation actions let a connected Google account create new events or update existing events from an automation. Create actions require a start and end date/time (or all-day) and accept title, description, location, attendees, and video conferencing options; Update actions require the Google Calendar Event ID and can modify those same fields (recurring events cannot be created).

Automation actions: Google Docs

Google Docs — Create/Update Doc actions let you insert a document creation or update step into an Airtable automation that creates or updates a document in a chosen Google Drive folder. The action includes a rich-text content editor, portrait/landscape layout options, and can render found records as lists or grids when paired with a Find records action.

Automation actions: Google Forms

The Google Forms automation action creates a new form response by appending a row to the Google Sheet that stores a form’s responses—you select the response Spreadsheet and Worksheet and map Airtable fields to the sheet’s columns. Responses added by the automation appear in the spreadsheet alongside user-submitted responses but are not synced back to the original Google Form.

Automation actions: Google Sheets

Automation actions for Google Sheets let an Airtable automation interact with specified Google Sheets spreadsheets and worksheets when a trigger runs. After connecting a Google account, you can configure actions to create, find, or update rows and write values to chosen sheets by mapping Airtable fields to sheet columns.

Automation actions: Hootsuite

The Hootsuite automation action schedules posts in Hootsuite from an Airtable automation by connecting a Hootsuite account and selecting one or more social profiles. You can set a static date/time or use a datetime field token for scheduling, compose the message with static text and record tokens, add attachments and comma-separated tags, test the action, and then enable the automation.

Automation actions: Jira Cloud

Jira Cloud automation actions (available on Business and Enterprise Scale plans) let Airtable automations create new Jira issues or update existing ones by connecting a Jira Cloud account, selecting site/project/issue type, and mapping Airtable fields to Jira fields. The Create issue action returns the Jira issue ID and key—which can be saved to an Airtable field for later use by an Update issue action—and supported custom fields are limited to string, single select, and multiple select types.

Automation actions: Microsoft Teams

Microsoft Teams automation actions let an Airtable automation send messages to specified Teams channels or chats when a trigger runs. These actions require connecting a Microsoft account and allow selecting the target channel/chat and composing the message content.

Automation actions: Outlook Calendar

Outlook Calendar automation actions let an Airtable automation create new events or update existing events in a connected Outlook Calendar. You can configure start/end times or all-day events, attendees, location, and video conferencing, and the Update action requires the Outlook Event ID for the event being modified.

Automation actions: Outlook Email

The Outlook Email automation action sends an email through a connected Microsoft Outlook (Microsoft 365/Exchange) account when the automation runs. You can configure recipients, subject, and message body with static text or record values, and include attachments from the record.

Automation actions: Salesforce

The Salesforce automation action lets an Airtable automation create, find, update, or upsert records in a connected Salesforce org. You configure the target Salesforce object, authenticate a Salesforce connection, and map Airtable fields or values to Salesforce fields.

Automation actions: Slack

Automation action: Slack — Lets Airtable Automations send messages to a connected Slack workspace by posting messages to channels or users. Messages can include dynamic Airtable field values and use Slack message blocks; the action requires connecting and authorizing a Slack account.

Automation actions: Twilio

The Twilio: Send SMS automation action lets Airtable automations send SMS messages via a connected Twilio account. To set it up you connect Twilio with your Account SID and Auth Token, configure the To/From/Body fields (optionally Media URL and status callback), test the action, and turn the automation on.

Automation revision history

Automation revision history is an audit trail of changes made to an automation's configuration over time. It shows which configuration changes occurred, when they were made, and which user made them, accessible from the automation's history panel.

Automation run history

Automation run history is a chronological log of each automation execution showing when runs occurred and their status (e.g., succeeded or failed). For each run you can inspect step-level logs including timestamps, inputs and outputs, and error messages.

Automation Scripts

Automation Scripts is the "Run a script" automation action that executes JavaScript using Airtable's scripting API. Scripts can read and update records, accept input variables from earlier automation steps, and return output variables for later steps.

Automation trigger: Button clicked

Button clicked is an automation trigger that runs when a record’s button field is clicked. You choose which table and button field to watch, and when clicked the automation runs with that record's context and available field values for subsequent actions.

Automation trigger: Email received

The "Email received" automation trigger fires when an email is sent to the unique address generated for the automation. It captures email metadata (sender, recipients, subject), the message body (plain text and HTML), and any attachments for use in subsequent actions.

Automation trigger: Record created

The "When record created" trigger runs an automation whenever a new record is created in the selected table and provides dynamic tokens (e.g., record ID, creation time) for use in subsequent actions. Because it can fire before manual data entry finishes, it's typically used when rows are created programmatically (for example, via forms or other automations).

Automation trigger: Record updated

"Record updated" is an automation trigger that fires when a record in a selected table is changed. You can optionally restrict the trigger to a specific view and/or to updates on one or more specified fields so the automation only runs when those changes occur.

Automation trigger: Webhook received

The "Webhook received" trigger fires an automation when Airtable receives an incoming HTTP request at a unique endpoint URL. The request’s payload (JSON body), headers, and query parameters are captured as input variables that subsequent automation actions can reference.

Automation trigger: When a form is submitted

The "When a form is submitted" automation trigger fires when a response is submitted to a specified Airtable form and starts the automation. The trigger provides the newly created record (record ID) and the submitted field values as input variables for subsequent actions.

Automation trigger: When record enters view

"When record enters view" is an automation trigger that fires when a record becomes included in a specified view. You choose the table and view, and the trigger runs whenever a record is created or updated (or otherwise changed) so that it matches the view's filter criteria, passing that record to the automation's actions.

Automation triggers

Automation triggers are event-based conditions that start an Airtable automation when specific events occur—examples include record creation or updates, a record entering a view, form submissions, scheduled times, or incoming webhooks. Triggers can be configured with filters and field conditions to limit which events fire the automation.

Automations

Automations lets you create rules that run actions automatically in response to triggers or on a schedule. You configure triggers (for example: record created/updated, form submission, scheduled time, webhook, or when a record matches conditions) and actions (for example: create or update records, send emails or Slack messages, run scripts) and can test runs and view run logs in the automation editor.

Base Extensions

Base Extensions are modular add-ons you install into an Airtable base to provide additional tools, custom UIs, and integrations that interact directly with that base’s tables, fields, and records. Extensions—installed and configured per base from the Extensions Marketplace—can include visualizations, custom interfaces, automation tools, and scripts.

Bases

A base is Airtable's top-level database that contains one or more tables, fields, views, records, attachments, and associated automations and apps. Bases can be created from scratch or templates, imported or duplicated, and shared with collaborators with configurable permission levels.

Build with Omni

Build with Omni launches Airtable’s conversational AI builder that generates complete apps—tables, interfaces, and automations—from natural-language prompts and attached context; outputs are fully editable inside Airtable. Asking Omni to build or iterate on apps does not consume AI credits, while analysis questions about your data incur AI credit charges per Airtable’s billing rules.

Claude MCP Connector

Claude MCP Connector is an implementation of Claude’s Model Context Protocol (MCP) that lets Claude connect to remote MCP servers (including Airtable’s MCP server) from the Messages API to access model context and tools. It enables the model to inspect base schemas and to read, create, and update Airtable tables and records via MCP requests.

Comments

Comments let collaborators leave threaded messages on a record’s activity feed. Comments support text, @-mentions, file attachments, and resolving threads, and are visible in the record’s activity log.

Conditional logic in Automations

Conditional logic in Automations lets you add If/Else branches and conditional actions to an automation workflow so different actions run based on tests of field values, trigger outputs, or formula results. You can combine multiple conditions with AND/OR and nest branches; only the actions in the branch that evaluates true will execute.

Custom domains for Portals

Custom domains for Portals let you serve a Portal at a domain you own by mapping that domain to the Portal. You configure the custom domain in the Portal settings and update your domain's DNS to point to Airtable.

Custom Interfaces (React)

Custom Interfaces (React) lets developers build fully coded, embeddable interfaces for Airtable bases using React. These interfaces use Airtable's Interfaces SDK to read and write base data and manage UI state inside the Interface Designer.

Dark mode

Dark mode is an appearance setting that switches Airtable’s user interface to a darker color scheme. It can be enabled or disabled in the app’s settings and applies across the Airtable UI (menus, sidebars, and record views).

Data library

The data library is an organization-wide collection of published data sets that administrators publish from shared views for others in the organization to discover and use. Published data sets can be added into bases as tables (including via HyperDB), and administrators can verify and control which data sets appear in the library.

Databricks via SQL

Databricks via SQL syncs a Databricks table, view, or the result of a custom SQL query into an Airtable base, with users selecting Databricks account, warehouse, catalog/schema, and mapping options during setup; syncs can be manual or scheduled (1/3/6/12/24 hours) and are limited to 100,000 records per sync.

Date dependencies

Date dependencies automatically cascade updates to datetime fields from predecessor records to dependent records, shifting dependent records’ start and/or end dates when predecessors change.

Default field values

Default field values let you specify an initial value for a field that is automatically applied to new records. Each field’s default is set in the field configuration and populates that field when a record is created.

Display names for linked records

Display names for linked records lets you choose a human-readable field from a linked table to display and search by instead of the linked record’s primary field or record ID. This value is shown when selecting or viewing linked records, replacing cryptic IDs with a readable field such as a project title or client name.

Edit records via Form

Edit records via Form opens a form pre-populated with a record's current field values so users can modify fields and submit changes. Submitting the form updates the existing record (keeps the same record identity) with the new field values.

Export to CSV

Export to CSV downloads the records from the current table or view as a CSV file. The file contains rows for each record and columns for the view’s visible fields in their current order; rich field types (attachments, linked records, collaborators, multi-selects, etc.) are converted to plain-text representations (e.g., URLs or display values).

Field dependency management

Field dependency management identifies where a field is referenced across a base—such as in formulas, views, filters, automations, apps, and synced tables—and provides controls to inspect and manage those references when editing, renaming, or deleting the field.

Field permissions

Field permissions let base owners and collaborators restrict who can edit individual fields in a table. Permissions are configured per field and can be limited to specific collaborators or roles, making the field read-only for others.

Field type: Attachments

Attachment fields store one or more files (images, PDFs, videos, etc.) in a record cell. Users can add files via upload, drag-and-drop, or URL and can preview, download, and view basic file metadata (name, size, dimensions).

Field type: Autonumber

Autonumber is a read-only field that automatically assigns a unique, sequential integer to each record (starting at 1 and incrementing by 1 for each new record). The assigned numbers persist with the record and cannot be manually edited.

Field type: Barcode

Barcode is a field type that stores a text value and renders it as a machine-readable barcode image. It supports multiple barcode formats and lets users scan barcodes into the field using the Airtable mobile app or external barcode scanners while retaining the underlying value as plain text.

Field type: Button

Button is a field type that shows a clickable button in each record which performs a configured action—for example, opening a URL, opening another record, or running a script/automation. The button's label and target can be set directly or dynamically constructed from other field values.

Field type: Checkbox

The Checkbox field stores a boolean (checked/unchecked) value and displays as a clickable checkbox in grid and expanded record views. Checkbox values can be used in filters, formulas, grouping, and sorting to organize and trigger actions.

Field type: Count

A count field displays the number of linked records in a record link column. To configure a count field, select the linked-record field to count and Airtable shows the count for each record.

Field type: Created by

The "Created by" field type automatically records and displays the collaborator who created a record. It is populated when the record is created and is read-only (cannot be manually edited).

Field type: Created time

The Created time field automatically captures and stores the date and time a record was created as a date/time value. The timestamp is set at creation and does not update later; display formatting (date, time, timezone) can be adjusted.

Field type: Currency

A Currency field stores numeric values with currency formatting (a selectable currency symbol and configurable decimal precision and number-formatting). Values are stored as numbers so they can be used in calculations, sorting, grouping, and rollups.

Field type: Date

The Date field type stores calendar dates and can optionally include a time component. It provides a date picker for entry and settings to enable time, apply a time zone, and choose the display format.

Field type: Duration

Duration fields store time intervals as numeric values in seconds and display them in selectable formats (h:mm; h:mm:ss; h:mm:ss.s; h:mm:ss.ss; h:mm:ss.sss). Duration fields can be referenced in formulas (treated as seconds), and numeric formula/lookup/rollup outputs can be formatted as durations.

Field type: Field Agents (AI)

Field Agents (AI) are AI-powered field types that automatically retrieve, analyze, or generate data at the cell level within a table. They can be configured as long text, formula, linked record, select, or number fields and can optionally use internet search, Google Drive/OneDrive, or attachments depending on field settings.

Field type: Formula

Formula is a read-only field type that computes values using expressions composed of other fields, literals, operators, and built-in functions. Formula fields recalculate automatically when referenced fields change and can produce text, number, date, or boolean outputs depending on the expression.

Field type: Last modified time

Last modified time is a field type that automatically records the date and time when a record was last changed. It can be configured to track changes to the entire record or only specific fields and updates its timestamp whenever those tracked fields are modified.

Field type: Linked record field

A linked record field lets you connect a record to one or more records in another table (or the same table) by selecting from that table; creating a link automatically creates a reciprocal linked record field on the linked table. The field displays linked record names and lets you open the linked records; it can be configured to allow single or multiple links.

Field type: Long text

Long text is a field type for storing multi-line, freeform text entries. It can store large bodies of text with line breaks, optionally enable rich text formatting, and opens an expanded editor to view and edit the full content.

Field type: Lookup

A Lookup field pulls values from a specified field in records linked to the current record and displays those values in the current table. Lookup values update automatically when linked records change and are read-only in the current table.

Field type: Multiple select

A Multiple select field lets you define a preset list of options and choose one or more of those options for each record. Options can be created, edited, reordered, and assigned colors in the field settings.

Field type: Percentage

The Percentage field stores numeric values and displays them with a percent sign, with configurable decimal precision. The underlying numeric value is available for calculations and formulas (for example, 0.25 displays as 25%). Percentage fields can also be displayed as visual colour-coded progress bars.

Field type: Phone number

The Phone number field type stores telephone numbers in a dedicated field and displays them as clickable tel: links for use with calling apps. It accepts digits and common separators (spaces, dashes, parentheses) and preserves the entered formatting.

Field type: Rating

Rating is a field type that lets users assign a numeric score to a record by selecting one or more icons (stars by default) with a configurable maximum and icon style. The rating is stored as a number and can be used in formulas, sorting, filtering, and grouping.

Field type: Rollup

A Rollup field aggregates values from a specified field in linked records by applying an aggregation function or custom formula to the array of those values. Common uses include numeric aggregates (sum, min, max, average), counts, or combining values with array/formula functions (e.g., ARRAYJOIN).

Field type: Single select

Single select is a field type that restricts a record’s value to one choice from a predefined list of options. Options are created and managed in the field settings, can be color-coded, and are chosen via a dropdown in the grid, forms, and other interfaces.

Field type: User

The User field type stores a reference to one or more workspace collaborators on a record, displaying each collaborator's name and avatar and can be configured for single or multiple selections. User fields are searchable and usable in filters, views, sorting, and automations.

Filter interface records by logged in user

Filter interface records by logged-in user lets you configure an interface to display only records where a collaborator (or user-related) field matches the current viewer. The filter is evaluated per viewer so each logged-in user sees only records associated with their Airtable account.

Form field validation

Form field validation lets form creators define rules on individual form fields to enforce correct data entry. Validation options include marking fields required and restricting inputs by field type (for example, number or date ranges, single-select options, and attachment types/sizes).

Forms

Airtable Forms are customizable web forms that map directly to a table’s fields so responses create new records in that table (or can edit records via record-specific edit links). Forms can be shared via a public link or embedded on a site and support field types, required fields, field descriptions, and file attachments.

HIPAA compliance

HIPAA compliance in Airtable includes a Business Associate Agreement (BAA) and implementation of required administrative, physical, and technical safeguards. These safeguards include role-based access controls, encryption in transit and at rest, and audit logging for workspaces configured to handle protected health information.

HyperDB Tables

HyperDB Tables are a storage layer in Airtable that lets Enterprise Scale customers work with very large datasets (up to 100 million rows) outside of a base. HyperDB tables can be populated from CSV files or connected to external data sources (e.g., Snowflake) and accessed in a base via on‑demand or synced reads.

Import by pasting data

Import by pasting data lets you paste rows and columns from your clipboard (for example, spreadsheet or CSV content) directly into a table to create or update records. Airtable parses the pasted content into fields and rows, attempts to map or create corresponding fields with appropriate field types, and inserts the data into the grid view.

Import from CSV

Import from CSV lets you upload a CSV file to create a new table or add records to an existing table. During import you can map CSV columns to Airtable fields, preview the data, and adjust header detection and field types before completing the import.

Import from Excel

Import from Excel lets you upload an Excel (.xlsx/.xls) file to create a new table or add records to an existing table. During import you map Excel columns to Airtable fields, convert headers into field names, and set or adjust field types before completing the import.

Import from Google Sheets

Import from Google Sheets brings the rows and columns from a selected Google Sheets spreadsheet into Airtable by mapping sheet headers to field names and importing row data. During import Airtable infers field types, lets you create a new base or add to an existing table, and requires you to authorize access to your Google account.

Inline editing in Interfaces

Inline editing in Interfaces lets users edit record fields directly within an Interface layout without opening the full record view. Edits are written back to the underlying table in real time and respect field types and Interface-level editability settings.

Integration: Google Drive

Google Drive integration lets you connect a Google account to Airtable and browse or search your Drive to attach files or insert file links into records. Drive files can be added to attachment fields or added as Drive file URLs to maintain a direct link to the original files.

Integration: JIRA

Jira Cloud integration creates a one-way Airtable Sync that imports issues from a selected Jira filter into a new table and keeps chosen Jira fields updated on a configurable schedule (manual or automatic). Changes made in Airtable do not sync back to Jira; the sync respects the permissions of the connected Jira account and supports a defined set of Jira fields and limits (for example, up to 10,000 issues).

Interface layout: Calendar

The Calendar interface displays records on a month/week/day calendar based on a selected date field. You can create, move (drag-and-drop), and edit records directly on the calendar, switch which date field to display, and apply filters and color-coding to control which records appear.

Interface layout: Dashboard

Dashboard is a grid-based Interface layout that lets you arrange multiple interface elements (widgets) on a single page. You can add, resize, and reposition elements such as charts, record lists, summaries, buttons, and filters to create a consolidated view of base data and controls.

Interface layout: Gallery

Gallery layout displays table records as configurable cards arranged in a grid; each card can show selected fields (including attachment thumbnails) and custom card labels. Clicking a card opens the record for viewing or editing, and the layout respects interface-level filters, sorting, and actions.

Interface layout: Kanban

Kanban layout displays records as customizable cards organized into columns based on a chosen field, allowing records to be grouped visually. Cards can be filtered and sorted, and you can drag cards between columns to update the grouped field value.

Interface layout: List

The List layout displays records in a vertical list where you choose which fields appear per row and can apply sorting, filtering, and grouping. Selecting a row opens the record’s details and exposes editing controls and any configured interface actions. Lists can also use multiple levels to display data from multiple tables in one interface via their linked record relationships. You may also show nested records for same-table linked record fields.

Interface layout: Overview

Overview is an Interface Designer layout that provides a landing page and navigation hub for an interface page. It lets you add text blocks, bookmarks, links, and customize a logo and cover image to link to other interfaces, pages, or records.

Interface layout: Record review

The Record review layout is an Interface layout that displays a list of records alongside a record detail pane so users can view, sort, and step through multiple records for review or triage.

Interface layout: Roadmap

The Roadmap interface layout displays records on a two-dimensional board with vertical columns and horizontal swimlanes so you can group records by two fields; cards are configurable and can be dragged between cells to update record groupings. Roadmaps allow for custom iconography to be used for the fields displayed in each card's footer.

Interface layout: Timeline

The Timeline interface layout plots records along a horizontal timeline using a single-date or date-range field, displaying records as points or bars that span their dates. You can change the timeline’s time scale and click a record to view its details. Timelines can also be viewed in Gantt mode to manage date dependencies.

Interfaces

Interfaces in Airtable are customizable, page-like layouts built on top of a base using components (grids, record review, galleries, charts, forms, buttons, filters, and controls) to display and interact with underlying tables and views. Components can show, filter, sort, and edit records, apply conditional visibility, and respect base and table permissions.

iOS App

The Airtable iOS app for iPhone and iPad lets you open, view, and edit your Airtable bases and records on mobile. You can create and update records, attach photos or files from your device (including the camera), fill and submit forms, comment on records, and have changes sync with your Airtable account.

Managed Apps

Managed Apps are pre-configured, installable Airtable apps that bundle a base schema, interfaces, and automations into a ready-to-use package. Admins can centrally manage and update Managed Apps via the Airtable Admin Panel.

Mark comments as resolved

Mark comments as resolved lets users mark a comment thread as resolved so it’s collapsed and removed from the active comment view. Resolved threads remain visible in the record’s activity feed (or comments panel) and can be reopened or filtered to view their resolved status.

Multi-source syncing

Multi-source syncing lets a single destination table consolidate synced records from more than one source. You can add multiple sync sources to that table, choose which fields to include from each source, and the destination table updates as those sources change.

Notifications

Notifications in Airtable report activity relevant to a user—such as record changes, comments, @mentions, and assignments—and appear in the notification center and record activity feeds. Users can adjust notification preferences and delivery channels (in-app, email, mobile) to control what they receive.

Omni

Omni is Airtable's integrated conversational AI assistant that builds apps, researches the web, analyzes data and documents, and can create or update records using natural-language prompts. It runs inside Airtable and can generate tables, interfaces, and automations or execute actions in a base based on user prompts.

Organisation audit logs

Organisation audit logs are a chronological record of administrative and security-related events across the organization, such as user sign-ins, role and permission changes, workspace/base creations or deletions, API key activity, and SSO events. Each log entry includes the timestamp, user identity, and the action performed.

Organisation branding

Organization branding lets admins upload an organization or org‑unit logo and create brand color sets in the admin panel; builders can apply or hide the org/org‑unit logo and select brand colors for bases and interfaces.

Personal access tokens

Personal access tokens are user-specific bearer tokens used to authenticate to the Airtable API and SDKs. Tokens are created and managed by individual users, carry configurable scopes and expiration, respect the creating user's permissions, and can be revoked.

Pivot tables

Pivot tables are a view that summarize and aggregate records into a grid by assigning fields to rows and columns and selecting aggregation functions (count, sum, average, min, max, etc.) for value cells. Pivot tables are available as an interface component for Dashboard interfaces.

Portals

Portals is an add-on that lets organizations share Airtable interfaces with external users (portal guests), using Interface Designer to grant those guests access to a subset of a base’s data and a customizable guest sign‑in page. Portal guests have interface-only permissions (editor/commenter/read‑only), cannot re-share interfaces, are generally hidden from other external users, and each base can have a single portal.

Preview people's utilisation in workload assignment

Preview people's utilization in workload assignment displays each collaborator's current assignments and utilization for the selected timeframe. It appears during assignment so you can view a person's load and availability before assigning new work.

Print interface

The Print interface lets you print or save certain Interface pages as PDFs — supported layouts include List, Timeline, Calendar, Record Details (individual pages, up to 100 record detail pages in one PDF), and Charts. Exports are triggered via Cmd/Ctrl+P or the Print option in the "..." menu and offer a "Format for printing" mode; Grid and Gallery interface layouts, Timeline in the Data tab, automation-based PDF generation, and other export formats are not supported yet.

Public forms

Public forms are shareable web forms that anyone with the link can open (no Airtable account required) to submit data directly into a table, with each submission creating a new record. Form fields mirror the table's fields and can include labels, descriptions, required settings, and be embedded in websites.

Record detail layouts (Sidesheet | Full-screen)

Record detail layouts let you open a single record in either a right-hand sidesheet or a dedicated full‑screen view to see and edit its fields, attachments, linked records, and activity. Layouts determine which fields and sections are shown and in what order, and provide inline editing, comments, and access to record activity.

Record revision history

Record revision history is a chronological log of all changes made to a record, accessible in the record's activity feed. It shows which user or automation made each change, when it occurred, and the before-and-after values for modified fields.

Record templates

Record templates let you save a set of field values and content (nested records) for a table and use that template to create new records pre-filled with those values. Templates are stored per table and can include values for any field types (text, attachments, linked records, collaborators, etc.).

Record-level permissions

Record-level permissions let you control which users can view, edit, or delete individual records within a table. Permissions can be scoped using collaborator fields or conditional rules and are enforced across the Airtable interface and API.

Repeating groups in Automations

Repeating groups in Automations let you loop over an input list (an array from a trigger or previous action) and run the same set of automation actions once per item in that list.

Same-table linked records

Same-table linked records let you link a record to one or more other records within the same table using a linked record field. Adding a link creates a reciprocal linked entry on the target record and lets you navigate to, add, or remove linked records directly from the field.

Sandbox mode

App sandbox creates a separate sandbox environment for a base where builders can make structural changes—tables, fields, views, automations, interfaces, and extensions—without impacting the production base. Records edited or created in sandbox do not sync to production, and structural changes can be reviewed in the sandbox and applied back to production via the Review changes → Apply changes workflow.

Scheduled automation intervals

Scheduled automation intervals let you run an automation on a recurring cadence by specifying how often it should trigger (for example, every N minutes, hours, or days). When the interval occurs, the automation's trigger fires and its configured actions execute automatically.

Secret keys for Automations

Secret keys for Automations let you store sensitive values (API keys, passwords, tokens) centrally in Builder Hub and reference them in Run Script actions using input.secret('your-secret-name'). Scripts that reference secrets have edit restrictions (only users with access to all referenced secrets can edit), secrets are redacted from console output, and secrets can be shared with specific user groups.

Snapshots

Snapshots are automatically captured point-in-time copies of an entire base that capture its schema, views, interfaces, forms and records. They can be created and stored to preserve a specific base state and later reviewed or restored. Each plan provides a different snapshot frequency and time that the snapshots are stored for.

Snowflake via SQL

Snowflake via SQL lets Airtable Sync pull the rows from a Snowflake table, view, or the result of a custom SQL query and import those results as records into an Airtable base.

Synced tables

Synced tables create a read-only table in your base that mirrors a table or view from another Airtable base, workspace, or supported external source. You choose the source and which fields to include, and the synced table updates to reflect changes made in the source (edits must be made in the source). You can also map fields from different tables to combine/merge in the destination table.

Tab navigation in record detail pages

Tab navigation on record detail pages provides a row of tabs that let you switch between different sections of a record’s expanded view (for example: field values, activity, comments, attachments, and linked records) without closing the record. Click a tab to view or edit the content for that section.

Test automations

Test automations lets you simulate an automation's trigger and actions to validate the setup without waiting for real trigger events. Use the Test button to fetch sample trigger data, run actions with that data, and inspect the test run results and logs in the automation run history.

Trash

Trash is Airtable’s recovery interface with two levels: base-level trash (shows and can restore deleted tables, views, fields, extensions, interfaces, and records for 7 days) and workspace-level trash (shows and can restore deleted bases/workspaces for 30 days by default, configurable up to 180 days on Enterprise). Users with appropriate permissions can view, restore, or permanently remove items from trash; base trash can be manually emptied while workspace trash cannot.

Two-way synced data

Two-way synced data synchronizes records between a source and a synced table in both directions: edits made in the destination update the source, and updates in the source appear in the destination. This requires enabling bidirectional sync and respects the sync configuration and permissions set on the source.

User groups

User groups let Enterprise admins and workspace owners create and manage named groups of users. These groups can be used to share workspaces, bases, and interfaces, populate user-type fields, and control org unit membership via the Enterprise admin panel.

User role: Commenter

Commenter is a user role that can view records and participate in record-level comment threads (add and reply to comments, include attachments, and resolve threads). Commenters cannot modify cell values, create/edit/delete records, or change base structure or settings.

User role: Viewer

Viewer (Read-only) is a collaborator permission that lets a user view bases, tables, views, interfaces, and record details they’ve been granted access to. Viewers cannot create, edit, or delete records or modify schema, nor can they perform Commenter/Editor actions (such as filling forms or editing via interfaces) without a higher permission level.

User roles

User roles let you assign permissions to collaborators at the workspace or base level, controlling which actions they can perform (for example: creating or editing records, commenting, viewing, and managing settings). Roles determine access to features such as table and field editing, sharing and link management, and workspace administration.

Video field agent

Video Field Agent is an AI-powered field that generates short videos (up to 8 seconds) from images or text prompts directly inside Airtable, optionally including audio, and uses Google's Veo 3 model. Workspace admins enable it via AI Labs and add the Video Field Agent to a base to generate videos inline; generation consumes credits based on duration and audio settings.

Web prototype fields

Web prototype fields are AI-powered field agents that generate interactive, clickable web prototypes from record data, natural-language prompts, or uploaded screenshots, outputting UI components as React/Next.js (Shadcn UI + Tailwind CSS) or basic HTML/CSS code with a real-time preview. Prototypes can be generated on demand or automatically, configured with custom instructions and model selection, and deployed to Vercel via one-click deployment.

Web search for Field Agents

Web search for Field Agents is an enableable option that lets a Field Agent query the live web to retrieve external information when populating or updating a field.

Workspaces

Workspaces are organizational containers that group related bases and workspace members. They centralize access control, member management, billing, and workspace-level settings for those bases.