If your Airtable base feels messy, duplicated, and hard to report on, there is a good chance you are using it like a spreadsheet.
The feature that changes this is linked records. Linked records are what allow Airtable to stop acting like a grid of rows and columns and evolve into a true business system. This guide breaks down exactly how they work, how to set them up, and the mistakes that trip up most builders.
Disclosure: The link above is an affiliate link. We only recommend tools we use ourselves.
Here is the pattern. You have a client name typed into a Projects table. Then you type it again into a Tasks table. Then again into an Invoices table. Each time, it looks slightly different — maybe the capitalization changes, maybe there is a typo, maybe someone abbreviates it differently.
Now nothing connects. Your reports do not add up. Your automations misfire. You cannot get a clean view of everything associated with a single client because the data is not actually related — it is just repeated text that happens to look similar.
This is what Airtable looks like when it is used as a spreadsheet. And it is fixable.
A linked record field connects one table to another. Instead of typing a client name into your Projects table, you select the actual client record. That creates a real relationship — a pointer from one record to another.
The connection is bidirectional. When you link a project to a client, Airtable automatically creates the reverse link on the client record too. You can see the project from the client and the client from the project. You only set it up once.
This is the foundation of a relational database. And it is what unlocks everything else in Airtable — rollup fields, lookup fields, filtered views, automations that actually know which records belong together.
In any table, add a new field and choose Link to another record. Airtable will ask you two questions:
Which table are you linking to? Choose the table that holds the records you want to connect. If you are in the Tasks table and want to connect tasks to projects, select the Projects table.
Can one record link to multiple records on the other side? This is the one-to-many question. Think through the real-world relationship:
The answer shapes how the field behaves and what you can do with rollups and lookups downstream.
Linked records work best when you think about your business entities and how they actually relate before you start building. A typical service business data model looks like this:
Clients — who you work for. One record per client company.
Projects — the engagements you run. Each project links to one client. A client can have multiple projects.
Tasks — the individual work items. Each task links to one project. A project can have many tasks.
Invoices — the billing records. Each invoice links to a project or a client, depending on how you bill.
Each of these tables links to the others through the relationships you define. Once they are connected, you can pull data across the chain — see all tasks for a client, all invoices for a project, total hours logged across an engagement.
When you link records, Airtable shows you the primary field of the linked record — the leftmost field in the table. This is what you see when you pick from a dropdown, what appears in rollup summaries, and what shows up in automations.
If your primary field is something like a website URL or an ID number, your linked record dropdowns will be confusing. Make sure the primary field is the human-readable name: the client name in a Clients table, the project name in a Projects table.
You do have the option to choose a different display field when setting up a link — but defaulting to a clear, descriptive primary field saves headaches later.
Retyping instead of linking. If you catch yourself typing the same information into multiple tables, stop. That information should live in one table and be linked everywhere else it is needed.
Too many tables. It is tempting to create a new table for every category of thing. More often, a single-select field or a filtered view handles the distinction better. Link tables when the two things are genuinely separate entities with their own records and fields.
Wrong primary field. If your linked record dropdowns show URLs, numbers, or cryptic codes instead of names, your primary field is wrong. Fix it in the source table first.
Ignoring the bidirectional link. When you create a link from Table A to Table B, the reverse link on Table B is created automatically. Do not create a second manual link going the other direction — you will end up with duplicate fields and confusing data.
Once your tables are properly linked, a different set of capabilities opens up:
None of this works reliably on a spreadsheet-style Airtable base. All of it becomes straightforward once linked records are in place.
If you have been treating Airtable like a smarter spreadsheet, linked records are the shift that changes what it can do for your business. Start building in Airtable here.