Airtable sits in the rare overlap between spreadsheet and database — it looks like a spreadsheet when you first open it, but behaves like a relational database underneath. The result is a tool that spreadsheet users can pick up immediately while gaining far more power than Excel or Google Sheets for structured, interconnected data. This fits into the wider topic we cover in our Complete Guide to Software and Apps.
Once you see how linked records work — a content calendar where every post links to the client it was written for, a project tracker where tasks link to both the team member and the project — it becomes difficult to manage complex information any other way. This guide covers how to actually use Airtable to build those systems.
Bases, tables, fields, and views
Everything starts with a base — a container for all tables, records, and views related to a specific project or function. Think of it as a database file. Within a base, you create tables — each one like a spreadsheet tab but structured as a proper database table with consistent fields. A marketing base might have tables for Campaigns, Content, Clients, and Channels.
Each row in a table is a record; each column is a field with a specific data type. This is where Airtable differs from a spreadsheet — rather than all cells being generic text, each field has an explicit type that enforces data consistency. A Date field only accepts valid dates; a Single select field only allows values from a predefined list; a Number field only accepts numeric input.
Views are different ways of displaying the same table’s records without changing the underlying data. Every table starts with a default Grid view; add additional views from the left sidebar “+” button. Views don’t create new data — they’re just different windows into the same records.
Field types that drive real power
Link to another record — the relational field that makes Airtable a database rather than a spreadsheet. A Link field in the Content table pointing to the Clients table allows each content record to be associated with a specific client. Each client record shows all content linked to it — the relationship is bidirectional automatically.
Lookup — pulls data from a linked record into the current table. If Content links to Clients, a Lookup field pulls the client’s contact email directly into each content record — no switching between tables.
Rollup — aggregates values from linked records. A Clients table with a Rollup field counting linked Content records shows how many pieces have been created for each client. Other rollup options: sum, average, max, min, concatenation.
Formula — calculates values from other fields in the same record. Airtable formulas use a JavaScript-like syntax: IF(), CONCATENATE(), DATEADD(), DATETIME_DIFF(), SWITCH(). Formula fields are read-only and update automatically.
Single select / Multiple select — dropdown fields with predefined options, each with its own colour. These coloured tags appear in every view, making record status scannable at a glance. A “Status” Single select (To Do / In Progress / Review / Done) powers the Kanban view as well as Rollup counts by status.
Attachments — stores files directly in a record cell. Images, PDFs, videos. Gallery view displays attachment images as card thumbnails — perfect for product catalogues, photo libraries, and design asset management.
The Link + Lookup + Rollup trio is the architecture that makes Airtable genuinely different from a spreadsheet. These three fields together allow building a properly normalised data model — each piece of information stored exactly once, with relationships connecting it wherever needed — something a flat spreadsheet cannot achieve without data duplication and the consistency problems that follow.
View types and plan comparison
| View type | Best use case | Free? |
| Grid | Data entry, editing, bulk operations | Yes |
| Gallery | Visual content libraries, image-heavy records | Yes |
| Kanban | Workflow status tracking, drag-to-update pipeline | Yes |
| Calendar | Scheduling, date-based record overview | Yes |
| Form | Public data collection, client intake workflows | Yes |
| Gantt | Project timelines with dependencies | Team+ only |
| Timeline | Multi-record date range visualisation | Team+ only |
The Form view surprises most new users. Clicking “+ Add a view” → Form creates a public-facing web form that, when submitted, adds a new record directly to the table. The form inherits all the table’s fields — choose which to show, mark fields as required, customise branding and success message. Share the link with clients, applicants, event registrants — every submission becomes a structured Airtable record immediately available in all other views.
A client project intake form capturing name, brief, deadline, budget, and files creates a properly-structured project record without any manual data entry — and Automations can then trigger off that new record to notify the team in Slack, create follow-up tasks, and send the client a confirmation email.
Automations and integrations
Automations (toolbar → Automations) create trigger-action pairs that run automatically without coding. Triggers: when a record matches conditions, when a record is created/updated, when a form is submitted, or on a schedule. Actions: create/update a record, send an email, send a Slack message, run a script, and many more.
Example content workflow automation: “When a Content record’s Status changes to ‘Published’ → update the Publish Date to today → send a Slack message to #content-team with the article title and URL.” Zero manual steps — the status change triggers everything.
Beyond native automations, Airtable integrates with Zapier, Make (formerly Integromat), and n8n for connections to thousands of additional tools. A workflow that creates an Airtable record from a form submission, sends the data to a CRM, and notifies a Slack channel can be built without any code.
The Airtable API provides programmatic access to every base for developers. No-code tools like Softr, Stacker, and Glide build customer-facing web apps and internal tools using Airtable as the backend database — making Airtable as an application backend accessible without custom development.
Practical setup — a content calendar in Airtable
A concrete example of how to use Airtable’s relational structure for a common workflow:
Create a base with two tables: Content and Clients.
Content table fields: Title (single line text), Status (single select: Idea / Brief / Writing / Review / Scheduled / Published), Publish Date (date), Platform (multiple select: Blog / LinkedIn / Instagram / Email), Client (link to Clients table), Assigned To (collaborator), Notes (long text), Attachment (drafts and final files).
Clients table fields: Client Name, Contact Email, Monthly Content Budget, Published Count (Rollup counting published Content records linked to each client).
Views on the Content table: Calendar on Publish Date (the publication schedule), Kanban on Status (the production pipeline), Form (client-facing intake form for new briefs). The same records appear in all three views — add a brief through the Form, track it through Kanban as it progresses, see it on the Calendar when it’s scheduled for publication.
Shared views and Interface Designer
Shared views let anyone see a specific view’s data without a Airtable account or edit access. From any view → view name → Share view → toggle on “Enable shared view link.” Create a Grid view filtered to one client’s records with internal fields (Cost Per Item, Margin, Internal Notes) hidden, and share that link — the client sees a clean, current snapshot without the overhead of weekly report preparation.
Interface Designer (Team plan and above) is Airtable’s no-code app builder — creates custom dashboards and data entry forms on top of existing bases. Instead of sharing the full base (which exposes all tables and fields), build a purpose-specific interface: a client portal showing only their records, a simplified data entry screen for team members who don’t need the full database view, or a management dashboard with summary charts and KPI metrics. Our guide on using Notion covers the document-and-database hybrid alternative for teams combining structured data with long-form notes.
Airtable vs alternatives — when to use each
- Choose Airtable if: data has multiple interconnected types that need relational links; the same data needs to be viewed in multiple formats (spreadsheet, Kanban, calendar, gallery) simultaneously; intake forms feeding directly into a database are needed; no-code app building on top of structured data is appealing
- Choose Google Sheets or Excel if: the data is primarily flat (one record type, no relational links); financial calculations are the primary use case; everyone on the team already uses Google Workspace or Microsoft 365
- Choose Notion if: the team needs a combination of structured data, long-form documentation, and wiki-style content in one connected workspace
- Choose Asana or Monday.com if: project management and task tracking are the primary use case, and the relational database aspect isn’t needed
Airtable’s free plan supports 1,000 records per base and 5 editors — enough to build and evaluate a working base before committing to the Team plan. The limitation that most commonly triggers an upgrade: the 100 automation runs per month ceiling on the free plan, which is exhausted quickly once useful automations are running. The record limit (1,000 per base) also becomes a constraint for growing datasets within a few months of active use. See also How to Use Todoist for a related case.
The learning curve for Airtable is real but front-loaded: the first base takes longer to set up correctly because you’re learning the field type choices and relational model. By the second or third base, the patterns become intuitive and setup is significantly faster. The payoff — structured, relational data that can be viewed in multiple formats, automated, and shared with custom access levels — compounds with every additional workflow that gets moved into Airtable from a chaotic spreadsheet or a disconnected set of tools. You might also run into How to Use Asana.
