Records pushed into the Airtable base your operation actually runs on.
The base knows this client is on hold until the survey clears, and the message goes out anyway, because the thing that sent it had no way to ask. Somebody spots it a day later and apologises.
Nothing off the shelf fitted, so somebody built the base. It has the fields your business actually has — the site, the panel count, the finance status, the installer, the three dates that matter to you and to nobody else. It is the most accurate description of the operation that exists anywhere, and it is kept accurate by a person retyping into it. Connect Airtable and rows are written and updated without them, and the more useful half is the other direction: a step can look a row up partway through and carry on differently depending on what it says. The base stops being a place you copy things into and starts being the thing the business asks before it acts.
Reach for this when the shape of your work is your own and nothing generic holds it. The base is the source of truth, and a decision on an account depends on what a row says. It suits an operation that outgrew spreadsheets and never found a tool that fitted.
Need more than it doesTell us what the connection has to do and we will wire the rest of it.
Your columns, your names, your structure. Nothing is reshaped to suit a template somebody else designed for a different business.
A row is read partway through, and what it says changes what comes next. Nobody is checking a tab to see whether the next step is right.
A new record when work starts, and the same one updated as it moves. The base reads as today rather than as whenever somebody last caught up.
You will find it under Settings → Integrations → Airtable.
Open the setup guide →
Four things on records: finding one, creating one, updating one, and deleting one. That is deliberately small, and it is enough, because your base already holds the meaning. The scope is the rows; the structure stays yours.
Yes. Each step chooses its own base and table. One sequence can read from the operations base and write to the finance one. You are not picking a single base at the start and living with it.
The values in it, in the middle of the work. The status, the owner, the date, the flag somebody set. What happens next can depend on them. An account on hold is treated as on hold, and nobody has to remember that it is.
No. It writes into the fields you already have, under the names you already use. The base was built because nothing generic fitted. That is the reason to point this at it rather than rebuild it somewhere else.
Yes, and it is worth saying plainly. A record removed this way is gone rather than hidden. Most operations write and update and never delete at all. If you do use it, use it somewhere you have decided on purpose.
Your pipeline, your data. Not a slide deck.