What Airtable is: between spreadsheet and application
Airtable is a cloud platform for organising related data and building configurable work applications. It combines a familiar table appearance with typed fields, relationships, interfaces, forms and automations. It has belonged to Bending Spoons since September 2026.
Its difference from a spreadsheet goes beyond appearance. Spreadsheets commonly contain different formulas in individual cells; Airtable defines a field whose behaviour applies across the table’s records. Nor does it remove the design work of a traditional database: relationships still matter, but users configure them visually and present them to people who do not need to write queries.
It can coordinate projects, content, inventories and internal processes. Its value emerges when several people need to work with the same entities from different perspectives. A well-designed base becomes a small operational system for the process; an improvised structure can become a collection of ambiguously connected lists.
Reference documentation: Airtable — About · Airtable — AI-native platform launch · Bending Spoons — Airtable acquisition completed.
Origins, funding, AI and a change of ownership
Airtable was created by Howie Liu, Andrew Ofstad and Emmett Nicholas. Its corporate page dates its origins to 2012, while some founders’ accounts use 2013; this discrepancy is distinct from the product’s public launch in 2015, recalled by the company itself. The original proposition made relational data organisation accessible to people without specialist database training.
Expansion was supported by successive venture rounds. The December 2021 Series F raised $735 million and announced an $11 billion pre-money valuation. These are historical funding figures, not revenue or a current sale price. That period also established Interface Designer and its positioning as an enterprise application platform.
In June 2025, Airtable introduced an AI application phase, with Omni as an assistant and field agents working on records. Its acquisition of DeepSky led to a separate product line, Superagent. Following the 2026 ownership change, Liu announced his departure from Airtable and his focus on Hyperagent as an independent company; these products should not be confused with capabilities automatically included in an Airtable base.
Bending Spoons completed the acquisition on 4 September 2026. In October, new product lead Alessandro Savarese announced a substantial reduction of the previous team and priorities for core functionality, AI and administrative control. The restructuring prompted debate about continuity and vendor dependence. It does not by itself establish service deterioration, but makes maintenance, export and ownership arrangements relevant for dependent processes. Improvements announced for later months must be distinguished from available features.
Reference documentation: Airtable — About · Airtable — Series F financing · Airtable — AI-native platform launch · Bending Spoons — Airtable acquisition completed · Airtable — Back to bases · Howie Liu — Acquisition and departure statement · InformationWeek — Post-acquisition layoffs · Airtable team — Introducing Superagent.
Related records rather than isolated rows
Airtable organises information into bases, tables and records with defined fields. Unlike a spreadsheet used simply as a list, records can be linked: one site can relate to several actions, and each action to its evidence, without copying the whole site description into every row. Design the structure around the real entities in the process.
Interfaces can display record details and related items with configured viewing and editing options. An interface may simplify an action owner’s work without requiring navigation through every table. However, visual design and permissions are separate issues: check effective access to the base, interface and related data. A simplified screen is valuable only when it still provides the information required for the user’s actual responsibility.
Reference documentation: Airtable Help — Linking records in Airtable · Airtable Help — Interface layout: Record detail.
Data model: bases, tables, fields and relationships
A workspace groups bases. A base contains an application’s tables; each table holds records of an entity type, such as a site, activity or document. Fields can contain text, numbers, dates, selections, collaborators, attachments or links. Choosing suitable types supports more consistent sorting, filtering and calculation than free-text columns.
Links represent relationships between records. A lookup displays values from related records; a rollup summarises them through aggregation. A formula operates on the record’s fields rather than freely referring to an arbitrary cell. When a related value is blank, inspect the link and original data first: adding a formula cannot create missing information.
The primary field helps people recognise a record, but a readable name is not an identification rule. Two actions can have the same title while remaining different; one action can change its title without becoming another action. Retain a stable key for migration and integration, and document the entity represented by each table.
Reference documentation: Airtable Help — Linking records in Airtable · Airtable — Formula fields · Airtable — Lookup fields · Airtable — Attachment fields.
Views, forms and interfaces
Views show the same records in different ways. A grid supports editing and comparison; kanban groups by status or category; a calendar positions dates; a gallery highlights visual items; timeline and Gantt views represent duration and planning. Switching views does not create an independent copy of the records.
A form collects information in a planned structure. An interface can combine lists, details and controls for a specific role, such as the person completing an action. Start with the task: what must they inspect, what may they change and how will they notice an error? Hiding a field in a view is not a replacement for configuring permissions.
Airtable works in a browser and has Windows, macOS, iOS and Android applications. Mobile does not reproduce every desktop feature: extensions, some views and interface capabilities differ. Before adopting a shop-floor workflow, test the actual journey on the intended device, including attachments, editing and connectivity; do not assume a desktop mock-up behaves identically on a phone.
Reference documentation: Airtable Help — Interface layout: Record detail · Airtable — Timeline views · Airtable — Desktop and mobile differences · Airtable — Views guide · Airtable — Interface Designer guide.
Automation, synchronisation and integrations
An automation combines a trigger with one or more actions. When an action reaches a particular status, for example, it might create a follow-up record or send an authorised notification. A trigger is not itself a valid decision: define which change counts as an event and how duplicate processing is prevented.
Check conditions, run history and plan limits. A flow that updates its own triggering field can repeat; one that iterates through many records can consume unexpected runs. Test new, existing, incomplete and repeated cases, and establish how work resumes after partial failure.
Sync transfers records from a source into destination bases, with modes and restrictions depending on configuration and plan. Define where the original is maintained and which changes propagate. A synced table should not be treated as a disconnected copy. API integrations use permissions and scopes, including personal tokens limited to particular bases and operations. A broad token can expose much more than the currently open view; design access around the specific task.
Reference documentation: Airtable — Automations guide · Airtable — Managing automations · Airtable — Sync guide · Airtable — Personal access tokens.
Omni, field agents and connections to assistants
Omni is the built-in assistant for working with applications and data through natural language. It can help build structures, analyse documents, and create or update records within the user’s permissions. Field agents perform tasks such as summarising or classifying record content. They require AI configuration, model availability and credits; availability across plans does not mean unlimited use.
The October 2026 release presented Omni 2.0 as available and Canvas as a beta for generating applications, dashboards or presentations on base data. The same announcement distinguished expanded audit logging for Enterprise Scale from finer agent permissions still described as forthcoming. This avoids assigning every account a capability dependent on rollout, region or edition.
The MCP server connects compatible assistants, including ChatGPT and Claude, to query or modify authorised data. A read-only integration supports exploration without granting modification rights. OSH examples include preliminary classification of descriptions or finding related materials; review categories and ambiguous records before feeding the output into an indicator or decision.
Reference documentation: Airtable — AI-native platform launch · Airtable — Omni AI · Airtable — MCP server · Airtable team — Fall release, October 2026.
Plans, limits, export and continuity
The range distinguishes Free, Team, Business and Enterprise Scale. Compare records per base, attachment storage, automations, history, sync, collaborators and administration. User count is only one factor: a small base may need governance features from another edition, while attachments can matter more than record numbers.
CSV export operates by table or view, not as a complete application. Relationships, formulas, interfaces and automations require additional documentation to reconstruct a process. Attachments appear as links: download URLs expire, so retrieve the files themselves when preserving a usable copy.
A continuity check exports a sample, opens it outside Airtable and verifies identifiers, dates, links and associated files. Include an archived record, one without attachments and one with several. This shows what depends on the platform and what the planned recovery procedure can recover, without confusing possession of a CSV with a complete backup.
Reference documentation: Airtable — Attachment fields · Airtable — Desktop and mobile differences · Airtable — Plans overview · Airtable — Attachment URL behavior.
Preventive processes it can help organise
- Actions and evidence: link an action to several verification documents while keeping ownership and dates in one reference record.
- Material inventories: relate training resources to their version, language, owner and activities using them, so changes can be traced when materials are updated.
- Visit preparation: connect sites, contact people and outstanding questions before a review, without presenting the list as a completed technical assessment.
These are designs proposed by Sabentis. Airtable supplies a configurable structure; the organisation must define and maintain categories, closure evidence and preventive decisions. Start with a bounded process whose relationships can be explained clearly before extending the base to more teams.
Worked example: one action with several evidence items
Hypothetical example. A team wants to record improvement actions without creating a different copy of the same action for every photograph or document.
- Create separate tables for sites, actions and evidence. Assign stable identifiers and decide which fields the process requires.
- Link every action to its site and every evidence item to its action. Check that relationships support the intended number of associated records.
- Prepare an interface where the owner can review the action, add authorised information and distinguish received evidence from reviewed evidence.
- Define closure as a verifiable decision: who reviews, which criterion applies and where the outcome is recorded. Do not close an action merely because a file is attached.
- Test an action without evidence, one with several items and another mistakenly linked to a different site. Review what each user role can see and change.
Accept the result when the action retains one identity, all its evidence can be located and its status corresponds to a documented review. Exceptions should remain identifiable for resolution rather than disappearing behind a filtered view.
Proposed check: the sample contains 10 actions and 18 evidence items: two actions have none, six have two each and another two have three each. The action count must remain 10, not 18. If only four actions have an approved closure review, the result is four closed and six outstanding, even though eight have files. Upload the same attachment again to check that the procedure identifies duplication without changing status.
Reference documentation: Airtable Help — Linking records in Airtable · Airtable Help — Interface layout: Record detail.
Filters, permissions and structural maintenance
Airtable documents that limiting record selection to a view or condition restricts what the picker displays but does not necessarily prevent linking records outside that filter. Treat this as a selection convenience, not a complete integrity or confidentiality rule.
Renaming fields, changing relationships or allowing multiple links can alter how interfaces and automations behave. Document these choices before changing a base already in use. Check plan limits, feature availability and the export options the process needs. When personal information is involved, avoid collecting unnecessary detail and verify that shared links do not unintentionally broaden access. Keep an accountable owner for the base when its original designer changes role.
Reference documentation: Airtable Help — Linking records in Airtable.
When a configurable base adds value
Airtable fits a need to relate entities and provide tailored working views where the team can maintain the base’s design. Do not select it merely because a table looks more attractive: define relationships, responsibilities and the route for handling an exception first.
Excel may be sufficient for bounded analysis without complex operational relationships. Compare Notion where combining documentation and records matters more. In either case, a decisive criterion is how information will remain reliable when processes or owners change.
Frequently asked questions about Airtable in OSH
Does linking records prevent every duplicate?
No. It represents relationships, but identifiers, record-creation rules and review remain necessary.
Does an interface always display everything in the base?
Configuration may expose only some information. Check actual permissions; an invisible field is not, by itself, a confidentiality guarantee.
Can an action with attached evidence be closed?
Only after the defined review confirms that the evidence is relevant and sufficient. Attaching and verifying are different operations.
Reference documentation: Airtable Help — Linking records in Airtable · Airtable Help — Interface layout: Record detail.
