Airtable automation
Airtable Automation Services
Airtable sits between a spreadsheet and a database, which is why it is so useful and so easy to misuse. We design the base as a data model first, then build the automations and interfaces on top of something that will still make sense in a year.
What we build
Relational base design
Tables, links and rollups modelled on the real entities — customers, jobs, invoices — rather than a wide sheet with a column added every time something new comes up.
Automations and scripting
Record-triggered flows for the routine work, and scripting where the logic genuinely needs it, kept in one place rather than scattered across views.
Interfaces for people who do not live in Airtable
Focused screens that show one team exactly what they need to act on, so the base can be structured properly without everyone having to understand it.
Integrations in and out
Forms, CRMs, billing and reporting connected through an automation platform, with Airtable as the operational record rather than another island.
Where it stops
Every tool has limits worth knowing before you build on it. These are the ones that change a decision.
- Record limits per base are real and arrive sooner than expected on transactional data. Airtable is excellent for thousands of records and the wrong shape for millions.
- Automation runs are capped per month by plan, and a chatty base burns through them faster than the row count suggests.
- There are no database constraints. Nothing stops a duplicate or an orphaned link except the process around it, so data quality has to be designed rather than enforced.
- Performance degrades on large views with many rollups and lookups — usually the first symptom that the base has outgrown the tool.
Worth reading first
Which processes are worth automating
Repetitive is not the same as automatable. The shapes of work that automate well, the ones that do not, and how to tell them apart first.
Integration Checklist: Key questions before connecting your CRM, billing, and ops tools
Questions to ask before connecting CRMs, billing, and ops tools so your data stays consistent end to end.
Airtable FAQ
- Airtable or a real database?
- Airtable while people need to see and edit the data directly, the volume is in the thousands, and the structure is still moving. A database once the data is transactional, the volume runs to hundreds of thousands of rows, or correctness matters more than editability — a database can enforce that a record cannot exist without its parent, and Airtable cannot. Plenty of systems end up with both: Airtable as the working surface, a database underneath for what has to be reliable.
- Airtable or Google Sheets?
- Sheets when the job is calculation and the data is genuinely a grid. Airtable when the data has relationships — customers with jobs, jobs with invoices — because that is exactly what a spreadsheet cannot represent without duplicating everything. The tell is a sheet where the same customer name is typed in forty rows: that is a table that wants to be a link.
- Can Airtable run our whole operation?
- It can be the centre of it, which is different. Airtable holds the operational record well and hands off badly at the edges: heavy documents, high-volume transactions, and anything needing strict permissions per field. The systems that last treat it as the working database with an automation platform doing the integration work around it, rather than trying to make it the only tool.
- We are hitting record or automation limits. What now?
- First, check what is actually consuming them — archived records nobody deleted and automations firing on every field edit account for most surprises. If the usage is genuine, the choice is a plan upgrade or moving the high-volume table out to a database while keeping Airtable for the parts people work in directly. Upgrading buys time; moving the transactional table is what fixes it.
Need help automating a process?
Tell us about the repetitive work on your team—we’ll map a practical custom automation plan.