How to Build a Kanban Board in Airtable

A Kanban board makes the state of work obvious. Open the Airtable Kanban view and you see exactly how many deals are in negotiation, how many candidates are waiting on interviews, how many articles are stuck in editing. No filter clicks, no pivot tables — just stacks of cards grouped by stage, ready to drag.

This guide covers how to build a Kanban board in Airtable end-to-end, the field setup that makes stacks work, the filters and colors that keep the board scannable, and the real-world templates we deploy in client projects.

What an Airtable Kanban Board Actually Is

An Airtable Kanban board is a saved view that displays each record as a card and arranges those cards in vertical stacks based on a single-select field. Drag a card to a new stack and Airtable rewrites the underlying field value. Close the Kanban view, open the Grid view, and the change is already there — Kanban is one of several windows over the same table.

This matters because Kanban in Airtable is never just a Kanban tool. The cards link back to Clients, Projects, or Candidates. The Status field that drives the stacks also triggers automations. The records you drag into "Done" feed reports in Interface Designer. One change in one view propagates everywhere.

For a deeper look at how views layer over the same data, see our custom views guide.

Prerequisites: The Single-Select Field

A Kanban view needs a stacking field, and that field has to be either a single-select or a collaborator field. You cannot stack by a multi-select (a card has to live in one stack), a formula (Kanban needs an editable field to update on drag), or a linked record (Airtable does not support it as a primary stack).

Most workflows use a single-select named Status or Stage. Decide your stages before you create the view — adding options later is easy, but renaming or merging stages once cards exist takes cleanup. Five to seven stacks is the sweet spot. Three stacks under-uses the format; ten or more becomes impossible to scan on a 13-inch laptop.

Step 1: Create the Kanban View

From any table that has a single-select field:

1. Click the + next to the view list in the left sidebar.
2. Choose Kanban under the visual layouts.
3. Name the view (e.g. Sales Pipeline — Kanban).
4. Pick the single-select field that should drive the stacks.
5. Click Done.

Airtable creates one stack per option in the single-select, plus an Uncategorized stack for records where the field is empty. If you do not see an option you expect, check the field's choices in the Grid view — Kanban shows them in the order they appear in the field's option list.

Step 2: Configure Visible Fields on Cards

By default, a card shows the primary field and three or four additional fields. That is usually too many for a scannable board. Click Customize cards in the toolbar and trim the visible fields to the four or five that matter for the user in front of the board.

A sales pipeline card needs Company, Amount, Owner, and Expected Close. Adding Industry, Source, and Notes turns each card into a wall of text that defeats the point. If a teammate needs the extra context, they click the card to expand it — the data is still there.

Three patterns for what to surface on the card:

• For salespeople: Company, Deal Amount, Next Step, Owner avatar.
• For content editors: Title, Author, Due Date, Word Count.
• For recruiters: Candidate Name, Role, Source, Last Activity Date.

The rule is the same in every case: show only what the person needs to make the next move.

Step 3: Color Cards by Condition

Stack color is one signal. Card color is a second signal layered on top. Color rules let you flag urgency, risk, or ownership without adding fields to the card.

Click Color in the view toolbar, then Add condition.

Color stacks visually so a glance at the board surfaces what to act on first. Pair coloring with stacking — never duplicate. If the stack already shows Status, do not also color by Status. Use color for the dimension the stack does not show.

Step 4: Filter the Noise

A Kanban board with 800 cards is useless. Filters cut the visible records down to what the current user is working on now.

Common filter patterns:

• Active work only. Status is not Done and not Archived. Closed-out cards stop cluttering the board.
• Current period. Created is in the last 90 days, or Expected Close is in this quarter.
• By owner. Owner is current user. Each rep sees their own pipeline by default; the manager has a separate view showing all reps.
• Tag-driven. Tags contains Priority so only flagged items show.

Make filtered views collaborative so the team shares the same baseline. Personal filters belong on personal views so they do not affect anyone else.

Step 5: Hide the Empty Uncategorized Stack

If every record has a Status, the Uncategorized stack is dead weight. Right-click the stack header and choose Hide stack. Hidden stacks still exist — drag a card into the strip at the right edge of the board to see them — but they no longer eat horizontal space.

Conversely, if you do see records piling up in Uncategorized, that is a signal that the Status field is missing data on records that need attention. Build an automation that pings the owner whenever a new record lands without a Status.

Real-World Templates

The same Kanban mechanics power very different operations. Four templates we use in client projects.

Sales Pipeline Kanban

Table: Deals. Linked to Companies and Contacts. Stack by Stage. Color by Amount tier. Filter to open deals (Stage is not Won and not Lost). Cards show Company name, Amount, Owner avatar, and Expected Close Date.

Combine with a CRM build and Kanban becomes the daily-driver view for sales. Rollups on the Companies table show total open deal value per account. An automation triggers a Slack notification when a card hits Negotiation.

Content Production Kanban

Table: Articles. Linked to Writers and Topics. Stack by Status: Idea, Outline, Drafting, Editing, Design, Scheduled, Published. Filter to current quarter. Color by Due Date proximity (red if due this week).

Each card shows Title, Writer collaborator avatar, Due Date, Word Count rollup. Editors live in this view all day. The Idea stack acts as the inbox — anyone can drop a record in, and the editor triages by moving it into Outline (approved) or marking it Killed (a separate single-select option that hides the card via filter).

Hiring Pipeline Kanban

Table: Candidates. Linked to Roles and Interviewers. Stack by Stage: Sourced, Screening, Interview, Reference, Offer, Hired, Rejected. Color by days-in-stage (orange if stuck for more than 7 days). Filter to active roles only.

A junction table called Interviews records each individual interview with the interviewer, date, and rating. The Candidate card shows their primary role, source, and a rollup of the latest interview rating. Drag the card from Interview to Offer and an automation creates a draft offer letter using a mail merge workflow.

Product Roadmap Kanban

Table: Features. Linked to Teams and Customers (for upvote tracking). Stack by Build Status. Cards show Feature name, requesting customer count rollup, target release. Filter to current and next quarter. Color by Customer Request count tier (green if over 10 requests).

The Backlog stack acts as the prioritization queue. Product managers drag items into Discovery to commit to them. Engineering pulls from In Build to In QA when work is done. The Shipped stack auto-archives weekly via a scheduled automation that moves records older than 14 days to a Done table.

Stacking, Grouping, and Stack Order

A few advanced controls that most people miss.

Reorder stacks. Drag a stack header left or right to change its position on the board. The order applies to that view only. Reorder so the most-used stages sit in the natural reading direction — typically left-to-right for forward progress, with the inbox stack on the far left.

Hide stacks per view. Right-click a stack header to hide it. Useful when an "Archived" stack should exist for completeness but never appear on the active board.

Group within stacks. Click Group in the toolbar to subdivide each stack by another field. A sales Kanban stacked by Stage and grouped by Owner shows each rep's deals separately within each stage. Use sparingly — grouping inside Kanban gets visually busy fast.

Sort within stacks. Sorts apply within each stack. Sort by Amount descending and the highest-value deal sits at the top of each stage stack. Sort by Due Date ascending and the most urgent work surfaces in each column.

Combining Kanban with Other Views

Kanban is rarely the only view a team uses. The standard pattern is three views on the same table, each tuned for a different task.

Every collaborator picks the view that fits their job, and edits in any view flow back to the single source of truth. For a complete project setup using this layered pattern, see our project management tutorial.

Automations Triggered by Kanban Moves

Dragging a card to a new stack updates the Status field. That field change is a perfect automation trigger. Common patterns:

• Stage = Won → create Project record. When a deal closes, automatically spin up a project in the Projects table linked to the same Company.
• Stage = Offer → send offer email. A hiring move into Offer triggers a mail merge that drafts the offer letter.
• Status = Editing → notify editor in Slack. A content card moving to Editing pings the editor with a link to the record.
• Status = Done → archive after 14 days. A scheduled automation finds records that have been Done for two weeks and moves them out of the active view.

Always use the When record matches conditions trigger rather than When record updated — it fires only when the field hits the target value, avoiding loops and false positives. See our automation guide for the full pattern catalog.

Common Mistakes

Three things that go wrong on most Kanban boards we audit.

Too many stacks. Twelve stages might mirror the real-world process, but the board becomes unscannable. Collapse adjacent stages where the team treats them the same — Submitted and Received are usually one stage in practice.

No filter on completed work. Without a filter, the Done stack accumulates forever and dwarfs the active stacks. Filter the view to active records only and let a separate Archive view show historical Done items.

Stacking by a field that should be a linked record. If "Owner" should be a single-select to drive Kanban, but you actually want each owner to have their own profile record with contact info and permissions, you have a modeling mismatch. Use a collaborator field for the Kanban stack instead — it works as a stacking field and stays a real user reference.

Troubleshooting

A few quick fixes for the issues that come up most often.

• A new option does not show as a stack. Refresh the Kanban view — sometimes options added in Grid take a moment to propagate. If still missing, confirm the option exists on the actual field being used to stack.
• Cards disappear after a drag. Almost always a filter problem. The Status field changed to a value that fails the view's filter. Drop the filter temporarily to find the record, then adjust the filter.
• Drag-and-drop is locked. Read-only share links and views without edit permissions disable dragging. Confirm you opened the editable collaborator view, not a shared view link.
• Color rules not applying. Color rules evaluate top-to-bottom and the first match wins. Reorder rules so the most specific conditions sit at the top.

Where to Go Next

A Kanban board is one of the highest-leverage views in Airtable because almost every business process has stages. Once the Kanban is running, layer in automations to handle the side effects of each stage transition, add an Interface dashboard for stakeholders, and consider moving from a simple Status field to a junction table when you need to track time-in-stage history.

If you are migrating from Trello, our Trello-to-Airtable migration guide covers the data shape conversion in detail. For the official spec on Kanban configuration options, see Airtable's Kanban view documentation.