S26-E06 – BuiltOnAir Live Podcast Full Show
To get all the latest videos and demonstrations from the BuiltOnAir Podcast, subscribe and get notified on our Youtube channel here and our newsletter/community here.
FULL EPISODE VIDEO
Watch the full video of the show.
FULL EPISODE AUDIO
Listen to the full Audio podcast for this episode here. Or add to your favorite podcast player
Listen On: Apple | Overcast | Spotify
The BuiltOnAir Podcast is Sponsored by On2Air – Integrations and App extensions to run your business operations in Airtable.
Start a FREE 14 Day Trial of On2Air Now
In This Episode
Welcome to the BuiltOnAir Podcast, the live show. The BuiltOnAir Podcast is a live weekly show highlighting everything happening in the Airtable world.
Check us out at BuiltOnAir.com. Join our community, join our Slack Channel, and meet your fellow Airtable fans.
Episode Summary
In this episode of the BuiltOnAir DevOps series, Dan Fellars explores the critical phase of Airtable management: what happens after the build is complete. For many teams, the builder becomes a single point of failure, leading to chaos when systems break or people leave the company.
Dan breaks down three essential areas for maintaining long-term Airtable health: using field, table, and automation descriptions for self-documentation; building a simple internal support desk using forms and interfaces; and conducting successful knowledge transfers.
You will also learn how to leverage AI and MCP (Model Context Protocol) to read your base schema, generate documentation, and perform a “handover test” to ensure new users can make changes safely without breaking existing automations or scripts.
⏱ Timeline:
- 2:20 - Three essential areas of Airtable DevOps
- 3:07 - Using field descriptions for self-documentation
- 4:48 - Documenting Airtable automations and logic
- 6:52 - Building a simple Airtable support desk
- 8:59 - Knowledge transfer and the handover test
Full Transcription
The full transcription for the show can be found here:
[00:00:05] Dan Fellars: Hey everyone, welcome back into the BuiltOnAir Podcast.[00:00:09] Dan Fellars: This is the fourth episode we’re doing in our DevOps series where we’re looking at the admin side of running your business on Airtable.
[00:00:17] Dan Fellars: Good to be with you.
[00:00:18] Dan Fellars: I’m Dan Fellars, the founder of BuiltOnAir.
[00:00:21] Dan Fellars: So last time we talked about who controls your Airtable.
[00:00:25] Dan Fellars: And today is about what happens after they’ve built it.
[00:00:28] Dan Fellars: For most teams, the base is the only documentation you have, and the person who built it is your support desk answering all your questions.
[00:00:36] Dan Fellars: And that works fine until the person’s not available and it stops working completely when they leave the company.
[00:00:42] Dan Fellars: So today we’re gonna cover three areas.
[00:00:45] Dan Fellars: First, how to use your base as self-documentation and what the base.
[00:00:50] Dan Fellars: itself tell people about how it works.
[00:00:52] Dan Fellars: Second, how to build response and support into your systems.
[00:00:56] Dan Fellars: So when something breaks, who’s gonna answer it and how it gets fixed.
[00:01:00] Dan Fellars: And third is the knowledge transfer if somebody else had to take over tomorrow for your base.
[00:01:05] Dan Fellars: Could they?
[00:01:06] Dan Fellars: So let’s dig into those.
[00:01:08] Dan Fellars: First we’re gonna start with the same client onboarding base we’ve used in the past.
[00:01:13] Dan Fellars: And here’s a client record.
[00:01:15] Dan Fellars: So we have a field called health.
[00:01:16] Dan Fellars: And it says it’s on track.
[00:01:18] Dan Fellars: And there’s also a renewal date, but it’s empty.
[00:01:21] Dan Fellars: So what does on track mean?
[00:01:23] Dan Fellars: Who sets it?
[00:01:24] Dan Fellars: Is the renewal date being empty a problem?
[00:01:26] Dan Fellars: If I hover over the field name, all it tells me is that it’s a formula.
[00:01:31] Dan Fellars: So if I open the field name, here’s where we get more information.
[00:01:34] Dan Fellars: We see the formula itself.
[00:01:36] Dan Fellars: It says if it’s active and the welcome email has been sent, then it’s on track.
[00:01:40] Dan Fellars: If the email Email hasn’t been sent, then it’s missing the welcome email.
[00:01:45] Dan Fellars: Pause shows that needs a call, and it’s all clear if you can read the formula, but most people can’t see it and don’t know where to look for that.
[00:01:53] Dan Fellars: So if you see here also it says add description, but rarely do people take the time to add one, and often it it’ll become stale and out of date if there is one to begin with.
[00:02:03] Dan Fellars: So But adding one is easy, and you don’t need to open the field editor if you have base level access from any record.
[00:02:10] Dan Fellars: Open the fields menu and pick edit field description, and you can type it in right there under the field.
[00:02:16] Dan Fellars: Also use AI to update these as well is very useful.
[00:02:20] Dan Fellars: So here’s what I wrote for the health.
[00:02:22] Dan Fellars: It’s description of what each value means, who sets it, and what not to do.
[00:02:26] Dan Fellars: There’s even a generate description button where if you want a first draft from AI, you can get that.
[00:02:31] Dan Fellars: And now when somebody hovers over the health, they get the answer right there in the grid, in the record, or in the interfaces and forms, you can see the description there.
[00:02:41] Dan Fellars: So very useful to do that.
[00:02:43] Dan Fellars: And fields aren’t the only thing that can describe themselves.
[00:02:47] Dan Fellars: The base has a description too.
[00:02:49] Dan Fellars: It’s called the base guide, and it’s what teammate.
[00:02:52] Dan Fellars: see the first time they open the base.
[00:02:54] Dan Fellars: Here’s what I wrote about this base, who owns it, where to start, and where to send problems to.
[00:03:00] Dan Fellars: And every table can have its own description straight from the tables menu.
[00:03:05] Dan Fellars: One row per client, who keeps it current and who to ask for help.
[00:03:09] Dan Fellars: So fields are only half of it, the other half is in the logic layer, your automations.
[00:03:14] Dan Fellars: What does each one do?
[00:03:15] Dan Fellars: What does it touch?
[00:03:17] Dan Fellars: Why does it exist, and who owns it.
[00:03:19] Dan Fellars: Airtable gives you a place for that too.
[00:03:22] Dan Fellars: The automation has a description under its name and each step can have one as well.
[00:03:27] Dan Fellars: This script step says what it reads and when it stops.
[00:03:31] Dan Fellars: The generated API doc doesn’t show these, but if you have AI reading the base through MCP, it can pick that up.
[00:03:39] Dan Fellars: So otherwise if it isn’t written here, it’s only in somebody’s head.
[00:03:42] Dan Fellars: So be sure to document these, use AI again to document them.
[00:03:46] Dan Fellars: So every base has generated documentation and it’s always current.
[00:03:50] Dan Fellars: Here with the health, it’s the formula.
[00:03:53] Dan Fellars: And here we see the formula.
[00:03:55] Dan Fellars: That’s the how, but it doesn’t tell you the why.
[00:03:57] Dan Fellars: Why the field is there, who owns it, and none of your automations or interfaces are in there at all.
[00:04:03] Dan Fellars: So a hand kept document might have the opposite problem.
[00:04:07] Dan Fellars: It might be right last month, but not now, and that’s potentially more dangerous than having no documentation of having bad documentation.
[00:04:15] Dan Fellars: So where do you get the rest?
[00:04:17] Dan Fellars: You can ask the base directly now with AI, using Omni AI or Airtable’s MCP MCP server, an AI system can read the entire schema on request.
[00:04:27] Dan Fellars: Can ask it to document the base.
[00:04:29] Dan Fellars: Here’s what came back when I did that.
[00:04:31] Dan Fellars: It tells you me the three tables, how they’re linked together, the automations with its triggers, the descriptions I wrote, on the script steps itself, and the interface with its pages.
[00:04:41] Dan Fellars: So nothing changed, it’s read-only and it’s the current every time you ask it.
[00:04:46] Dan Fellars: So the descriptions you wrote.
[00:04:48] Dan Fellars: Stop being notes in an editor and become documentation anyone can pull through AI.
[00:04:54] Dan Fellars: Now the second area, response and support.
[00:04:58] Dan Fellars: When someone in the company has a problem with a base, where do they go?
[00:05:02] Dan Fellars: In most companies it’s a message or email to whoever built it and they just work around it.
[00:05:08] Dan Fellars: And you don’t need but you don’t need an enterprise process to fix that.
[00:05:13] Dan Fellars: Here’s a very simple small support desk I asked Omni to build.
[00:05:17] Dan Fellars: Said one table for request, a form, and a view for the owner.
[00:05:21] Dan Fellars: Thirty seconds later, it was built.
[00:05:23] Dan Fellars: So the form I just said define it as something’s wrong with the base, give it a summary.
[00:05:29] Dan Fellars: which base you’re referring to, what’s wrong, who is asking, and how urgent it is.
[00:05:34] Dan Fellars: So now we have one link that everybody in the company knows how to access and send input into for feedback.
[00:05:41] Dan Fellars: So it’s a great way to centralize it.
[00:05:43] Dan Fellars: You have one request landing right here in a table.
[00:05:46] Dan Fellars: has a status and i priority.
[00:05:48] Dan Fellars: You can set it up for with automations to send out notifications and email to let people know a new request has been submitted.
[00:05:56] Dan Fellars: The owner gets its own interface with a open request by priority and an automation that emails them when a new one comes in.
[00:06:04] Dan Fellars: And that’s it.
[00:06:05] Dan Fellars: It’s a simple form, a table, the owner with its automations and interface, and now you have a response system in its simplest form, and you can expand from there.
[00:06:15] Dan Fellars: When a request does come in, the owner doesn’t have to answer from memory either.
[00:06:19] Dan Fellars: So to find out Who needs a call, you can ask Omni or use your MCP to figure this out.
[00:06:26] Dan Fellars: And also performed updates as well.
[00:06:29] Dan Fellars: You can change the status directly through your client or through the interface as well to update it and keep things moving along and tracking.
[00:06:39] Dan Fellars: So you can ask the same thing through your AI assistant.
[00:06:43] Dan Fellars: make sure it only checks the tables.
[00:06:46] Dan Fellars: Tell it not to update things if you don’t intend it to update it.
[00:06:49] Dan Fellars: That’s important as well.
[00:06:52] Dan Fellars: So another place to look also is the manage fields.
[00:06:55] Dan Fellars: We talked about this in last episode, but it tells you everything right there from the menu, all the tables that touch it, the descriptions, the dependencies.
[00:07:04] Dan Fellars: right here the status has four dependencies between automations, fields, and interfaces.
[00:07:11] Dan Fellars: And sometimes Omni can’t see the interfaces and the relationships, so this field you might get more than asking Omni or your MCP client.
[00:07:20] Dan Fellars: So that’s important to check out there.
[00:07:23] Dan Fellars: Okay, so the third area is your knowledge transfer.
[00:07:26] Dan Fellars: If you have a new person take over your most important base today, how long do you think it would take them to be able to make changes safely and know all the impacts that it would have?
[00:07:36] Dan Fellars: So here’s something we’re trying.
[00:07:38] Dan Fellars: I asked Omni to explain the base to somebody taking it over and told it not to change anything.
[00:07:44] Dan Fellars: In about 2 seconds it came back and it described every table, automation, and interfaces.
[00:07:49] Dan Fellars: So that’s a pretty decent way to hit start a handover task.
[00:07:53] Dan Fellars: But remember it it reads what’s built, not what you meant when you were building it and all the other things that are in there.
[00:08:00] Dan Fellars: So useful part is what not to touch.
[00:08:03] Dan Fellars: Not to rename fields or the status options because they’ll break the scripts or the triggers.
[00:08:08] Dan Fellars: That’s what we talked about in episode two to check out.
[00:08:12] Dan Fellars: It also will flag any automations or status fields that need re-triggering, two-way links.
[00:08:18] Dan Fellars: So check that with the person who built the base.
[00:08:20] Dan Fellars: Make sure you know the intent around that, if that person is available to discuss with.
[00:08:26] Dan Fellars: and try to get that as documented in the descriptions as possible for future reference.
[00:08:32] Dan Fellars: So here’s the handover test.
[00:08:33] Dan Fellars: Pick a base you didn’t build and have never opened, and use AI to read what’s there and see if you can make a safe change and see the impact on it.
[00:08:44] Dan Fellars: Ask questions of your AI if what if it can find the impact there and evaluate how safe it is to make changes.
[00:08:53] Dan Fellars: So how important how how long do you think it would take to really get your arms around a new base?
[00:08:58] Dan Fellars: A week, a month?
[00:09:00] Dan Fellars: We’ll see.
[00:09:01] Dan Fellars: So here’s what I would recommend for future reference, especially once you get to the point of having more than one base, is build a center of excellence where all your data can go into a centralized repository, sync it in there through API or MCP, get all your descriptions, who owns.
[00:09:20] Dan Fellars: what the current state is and have that syncing with all that information into one location where you can put your documentation and allow people to have a central place to also document your connections and integrations, which we’ll talk about next time.
[00:09:36] Dan Fellars: So here’s a good checklist to help you see where you’re at.
[00:09:40] Dan Fellars: Is your base self-documenting?
[00:09:42] Dan Fellars: All the descriptions and bases and tables and fields all updated, formulas documented on what they do, are your automations documented on what they touch and who owns them, where to go for help?
[00:09:55] Dan Fellars: Does your schema get pulled into a central place?
[00:09:58] Dan Fellars: All of that.
[00:10:00] Dan Fellars: is a good way to to see where you’re at.
[00:10:02] Dan Fellars: You can now use AI and Omni or your MCP to pull all this information in, put it into a central place, add your documentation.
[00:10:11] Dan Fellars: Now you have one place where you can help transfer knowledge, help people get up to speed on all the underlings of how everything works.
[00:10:19] Dan Fellars: I highly recommend a center of excellence for any business running your base your business in Airtable.
[00:10:27] Dan Fellars: So with that, next week we’re gonna talk about integrations and data and how to document those.
[00:10:32] Dan Fellars: So be sure to like, subscribe, join our community.
[00:10:35] Dan Fellars: And if you’ve ever inherited a base with no documentation, I want to hear about it.
[00:10:39] Dan Fellars: Leave your comments.
[00:10:40] Dan Fellars: Let me know how you got up to speed in it.
[00:10:42] Dan Fellars: And I’d love to hear.
[00:10:43] Dan Fellars: So until next time, we love, we’ll see you on the BuiltOnAir Podcast.
[00:10:48] Dan Fellars: Take care.