Most people discover Airtable’s automation layer by accident. They’re clicking around, building out a base, and they notice there’s an “Automations” tab at the top of the screen. They open it, see a list of triggers and actions, quietly close it again, and go back to doing things manually. Which is a shame, because what’s sitting in there can handle a surprising amount of useful work before you’ve connected a single external tool or spent an extra penny.
This article is about that built-in layer. What it can actually do, how to set up your first automation from scratch, and where it runs out of road. I’ll be straight with you about the limits, because the goal here is to help you understand what you already have access to, not to pitch you on a more complicated setup than you need.
What Airtable’s native automations can handle
The automation builder inside Airtable works on a simple principle: something happens (the trigger), and then Airtable does something in response (the action). That’s the whole model. The triggers are things like a record being created, a form being submitted, a field value changing, a date arriving, or a condition in your base being met. The actions are things like sending an email, sending a Slack message, creating a new record, updating a field in an existing record, or running a script.
What that combination makes possible is more than it sounds.
Say you’re using Airtable to track client projects. Every project has a status field: Not Started, In Progress, In Review, Complete. You can build an automation that watches for the moment that field changes to “In Review”, and immediately sends an email to a specific address, say yourself or a team member, with the project name and a link to the record. No checking required. No one has to remember. The moment the status changes, the notification goes. That’s a real workflow, built entirely inside Airtable, using the free automation layer, and it takes about ten minutes to configure once you know where to look.
Here’s another common one. A client fills in an intake form linked to your Airtable base. The form submission creates a new record. You want that new record to automatically get tagged with a status of “New Enquiry”, have today’s date written into a “Date Received” field, and trigger an email to acknowledge receipt. All of that is possible inside a single Airtable automation. One trigger, a sequence of actions, done.
The third pattern worth knowing is conditional record creation. If a record in one table meets a certain condition, you can instruct Airtable to create a linked record in another table automatically. This is useful if you’re managing something like a services business where each new client should automatically generate a corresponding project record, or each completed onboarding should kick off a separate invoicing record. You’re essentially telling the database to do the filing for you.
Setting up your first trigger and action pair
Open your Airtable base and click the “Automations” button at the top. You’ll land on the automation builder. Click “Create automation” or “Add automation”, depending on which version of the interface you’re on.
Step 1: Choose your trigger
This is the event Airtable will listen for. For a first automation, the easiest starting point is “When a form is submitted” or “When a record enters a view”. The form submission trigger is exactly what it sounds like. The “enters a view” trigger fires whenever a record appears in a filtered view, which means you can set up a filtered view for records matching certain conditions and the automation kicks off whenever something new qualifies. That’s a more flexible pattern than it first appears.
Step 2: Configure the trigger
Select which base and which form or view you’re pointing at. Airtable will ask you to run a test to find an example record. Do this properly rather than skipping it, because the test result is what populates the field options in the next step. If you skip it, you’ll be building the action without knowing what data you have available, and that gets confusing quickly.
Step 3: Add your action
Click the plus button below the trigger and choose what should happen. If you’re sending an email, select “Send email”. You’ll be asked for a recipient address, a subject line, and a message body. Here’s where it gets useful: you can insert dynamic values from the trigger record directly into the email. The project name, the client’s email address, whatever fields exist in your base, you can pull them into the message. So instead of a generic notification, the email says “New enquiry received from Kirsty at Meadow & Co, submitted at 9:42am. Click here to view the record.” That took you thirty seconds to configure and will run forever without you touching it.
Step 4: Turn it on
Toggle the automation from “Off” to “On” and test it with a real submission or a manual record change. Watch the automation log (there’s a history view) to confirm it fired and what it did. If it didn’t work, the log will usually tell you why in plain enough language to fix it.
That’s genuinely it for a first automation. Trigger, action, test, on.
Step 5: Think about sequences
Once one automation is working, the natural question is whether you need more than one action to fire from the same trigger. Airtable lets you chain multiple actions under a single trigger, running them in sequence. So a form submission could simultaneously create a record, send an email, and update a field, all from one automation. You don’t need three separate automations for that.
Where the built-in layer stops being enough
I want to be honest about this part, because the built-in automations are genuinely capable but they are not infinitely capable.
The main constraint is that Airtable’s native actions are largely confined to things that happen within Airtable, or a small set of connected apps it supports natively, like Gmail, Slack, Microsoft Teams, Outlook, and a handful of others. If the thing you want to do lives outside that list, you’re working against the grain. You can’t, for example, automatically generate a PDF invoice and attach it to an email, create a Notion page, post to LinkedIn, update a Xero contact, or do anything that requires talking to an API that Airtable doesn’t natively speak to. The moment your automation needs to touch external software that isn’t on the approved list, you need an external tool like Make.com in the middle.
Make.com (and similar tools) acts as a bridge. It can listen for triggers from Airtable, take the data, pass it through whatever logic and transformations you need, and then hand it off to a different system entirely. That’s where genuinely complex workflow automation lives, and it’s what we build for clients at Avocado AI when a process has outgrown what the native layer can do.
There’s also a practical limit around conditional logic. Airtable’s built-in automations support basic conditions, if a field equals a value, if a record matches a filter, but the more sophisticated branching logic, where different actions happen depending on multiple conditions, can become difficult to manage inside the native builder. It’s possible in some cases, but it gets messy, and messy automations break in confusing ways.
The other thing to keep in mind is that Airtable’s automation run limits are tied to your plan. The free and lower-tier paid plans include a monthly allowance of automation runs, which is fine for low-volume workflows. But if you’re running automations against hundreds or thousands of records regularly, you’ll want to check what your plan includes before you build something that depends on it.
None of this is a reason to avoid the native automations. Quite the opposite. Start there, build what you can, and only reach for an external tool when you’ve hit a wall that actually matters to what you’re trying to do. The built-in layer is free, it’s already set up, and for a significant chunk of small business admin tasks, it’s more than enough.
Go and build the first one. See how quickly it stops feeling like a technical task and starts feeling like something you should have done six months ago.
