---
source_url: "https://klero.ai/resources/airtable?utm_source=openai"
title: "Airtable Guide: Database, Spreadsheet & Workflow Automation | Klero"
mirrored_at: 2026-08-31T01:02:27.563Z
host: klero.ai
cited_in_42a: true
mirror_canonical: "https://index.42a.ai/klero.ai/resources/airtable__q__utm_source_openai"
---

> **Original source:** https://klero.ai/resources/airtable?utm_source=openai

Airtable is a spreadsheet-database hybrid. You build **bases** (databases) with **tables**, **views** (grid, Kanban, calendar, form, etc.), and **automations**. Use it when you need structure and relationships like a database, but want to work in a familiar grid and add views and automation without code. This guide covers what matters for product and operations: bases, views, and when Airtable fits your workflow.

How to Use Airtable & Getting Started Tutorial

## Why airtable fits product and operations work

-   **Tables and relations** - **Tables** are like sheets, but with **linked records** (relations). “Projects” linked to “Tasks”; “Contacts” linked to “Companies.” You get a real relational model without writing SQL.
-   **Views on the same data** - **Grid**, **Kanban**, **Calendar**, **Gallery**, **Form**, **Timeline**, etc. Each view is a lens on the same table. Use Grid for bulk edit; use Kanban for status; use Form for input; use Calendar for dates. One table, many ways to work.
-   **Automation** - **Triggers** (e.g. “when record created,” “when field changes”) and **actions** (e.g. “send email,” “create record elsewhere,” “post to Slack”). Use it for notifications, handoffs, and lightweight workflows without code.
-   **Free tier that’s usable** - Limited bases and records, but enough for small teams. Paid tiers add more records, automation runs, and extensions.

## Core concepts that matter

### Bases and tables

A **base** is your database (e.g. “Product backlog,” “Content calendar”). **Tables** are your “sheets” with **fields** (text, number, date, link to another record, etc.). **Linked records** connect tables: e.g. “Tasks” link to “Projects.” Plan tables and links up front so you don’t end up with one huge table or duplicate data.

### Views

**Views** are different ways to see and filter the same table. **Grid** is the default table view. **Kanban** groups by a select field (e.g. Status). **Calendar** shows records by a date field. **Gallery** shows cards (e.g. with image and title). **Form** collects input into the table. **Timeline** (where available) shows records on a timeline. Create views for each job: e.g. “Backlog – Grid,” “Sprint – Kanban,” “Planning – Calendar.”

### Fields and types

**Fields** define what each column holds: **Single line text**, **Long text**, **Number**, **Date**, **Select**, **Multiple select**, **Link to another record**, **Lookup**, **Formula**, **Attachment**, etc. Use **Link to another record** for relations; use **Lookup** and **Formula** to pull in related data or compute values. Keep field names clear so views and automation stay understandable.

### Automation

**Automation** has **triggers** (when something happens) and **actions** (what to do). Examples: “When record is created in Table X, send email” or “When Status = Done, add to Slack.” Use automation for: notifications, status-based handoffs, and syncing to other tools. Start with one or two automations; add more as patterns emerge.

Welcome to Airtable!

## Practical habits

-   **Model relations early** - Decide which tables link to which (e.g. Projects → Tasks, Contacts → Companies). Avoid one giant table; split into normalized tables and link.
-   **Use views for different jobs** - One view for “backlog review” (Grid, sorted); one for “sprint board” (Kanban, by Status); one for “planning” (Calendar). Name views so the team knows which to use when.
-   **Name fields and tables clearly** - “Project” and “Due date” beat “Field 1” and “Column B.” Helps when you add automation and onboarding.
-   **Start with one automation** - e.g. “When Status = Done, notify in Slack.” Prove the pattern, then add more triggers and actions.

## When airtable isn’t the fit

-   **Heavy reporting and BI** - For complex analytics, dashboards, and reporting, use a data warehouse and BI tool (e.g. BigQuery + Looker). Use Airtable for operational data and light reporting.
-   **High scale or low latency** - Large bases, many automations, or heavy concurrent use can hit limits. For core transactional systems at scale, use a proper database and app.
-   **Need for code-first or full control** - If you want everything in SQL, migrations, and version control, use Postgres and a proper backend. Airtable is for “database-like without code” and speed of iteration.

## Pricing (high level)

**Free** - Limited bases, records, and automation. **Plus** and above add more records, runs, and features. Check [Airtable pricing](https://www.airtable.com/pricing) for current tiers.

For product and operations teams that need structured data, multiple views, and lightweight automation without code, Airtable is a strong default. Use it for backlogs, content calendars, and workflows; add tables and automation as the work grows.