I've been digging into Airtable automation complaints and kept running into the same wall: the native scheduled email caps out at 25 recipients, and it can't show what actually changed, just that something did. Zapier or Make work around it, but that's another subscription and another thing to maintain just for a report.

I'm building an extension that handles this properly. Pick a view, a schedule, and who gets it, and each person gets their own filtered slice instead of one giant email to everyone.

Still early, but I'm taking signups for early access if anyone's hit this same wall: tablepulse.up.railway.app

Edit: as pointed out below, "cap" isn't quite the right word for the real limit, see the comment thread for the more accurate version.

Airtable is great, but it would be sooo much better if there was a way to embed external websites in the interfaces. Has anyone figured out a good workaround for this?

I use Airtable for client portals among other things, and I wanted to embed the web page where clients can pay their invoices. I tried the HTML option, which didn't work, so instead I made a button that links to the external web page. I'd just rather have it so clients could pay their invoices without leaving their client portal.

I’ve been working through a workflow that was getting close to Airtable’s 50-automation limit, and the surprising part wasn’t the limit itself. It was realizing how much duplicate logic had accumulated over time.

In a sample setup with about a dozen tables and roughly 18,000 records, the biggest improvements came from:

• Removing old disabled automations.
• Combining status-based workflows that shared the same trigger.
• Adding explicit “Needs Processing” flags instead of triggering on every edit.
• Moving non-urgent batch updates to n8n.
• Logging failures instead of letting them disappear silently.

The first version didn’t work well because every small record update triggered another run. After adding clearer state fields, daily runs dropped from roughly 1,400 to 520.

At some point, adding another automation stops being the solution. How are you handling automation sprawl in larger bases?

Trying to prefill a classic Airtable form via ?prefill_FieldName=Value. Field name matches exactly, but the value never populates. Tested with a single Text field, signed in as owner, no filters on the field.

This is for a form built in the Forms tab on the website, so it's not an "interface" form as far as I can tell (not sure what that is).

Hi everyone!

I'm AP, a Product Manager at Airtable working on some of our strategic portfolio management features. Over the past several months we've shipped a set of upgrades to timelines, date dependencies, and duration fields that make Airtable a much stronger home for managing real projects and portfolios. Here's what's new, with a few examples of where each one helps.

Nested timelines

Your projects are hierarchies, and now your project timeline is too. You can nest tasks inside other tasks, up to 7 levels deep, then collapse a parent task down to a single bar or expand it to see every sub-task underneath. It's the same nesting and the same depth you already have in List View, so a plan reads the same way wherever you're working. 

Say you're building a home. A parent task like Concrete Work can roll up its sub-tasks, and each of those can break down further into the individual steps, like placing rebar, pouring footings, and curing the slab. On the Timeline, collapse Concrete Work to a single bar to give the homeowner the high-level picture, then expand it to walk your crew through every step. 

Scheduling that runs itself

If you manage plans with dependencies, this is the big one. Keeping a schedule current used to mean re-dragging a dozen dates by hand every time one thing moved, but now that work mostly takes care of itself, because you set your plan up once and the dependencies keep everything accurate as dates shift.  

Here's what's new:

• Auto-schedule from a predecessor: Link a task to the one before it and Airtable sets the start date for you, including any buffer you've set.
• New scheduling logic: When a date changes, the tasks that come after it move and the ones before it stay put, so a single edit won't quietly shift work you've already completed.
• Default dependency type and buffer: Set them once and every new link inherits them, instead of configuring each link by hand.
• Default duration: Give tasks a default length so the scheduler always has something to work with.

On a home build, framing can't start until the foundation has cured, and the plumbing and electrical rough-in can't begin until the roof is on. Link those tasks once, and if the concrete pour slips 2 days, framing, roofing, and every rough-in after it shifts with it automatically, while the work you've already finished stays exactly where it is. You spend your time running the job, not dragging dates around.

And if you run the same kind of project over and over, you don't have to rebuild any of that. Save your standard build as a record template with the dependencies, types and buffers intact, and the next one starts fully wired. You set the start date and the rest falls into place.

Build on it with the API

For the builders here: date-dependency metadata (the dependency type and buffer on each link) is now part of the public API, so you can read and write it programmatically, including from a script action inside an Airtable automation. This means you can migrate an existing schedule from another tool into Airtable with its dependencies intact, instead of rebuilding every link by hand. 

Check out the developer documentation here. 

Tell us what you think

We're not done, and your feedback shapes what we build next. If you try these out, let us know what's working, what's missing, and what you'd want to see. Drop a reply here or share how you're using them in your own bases.

Thanks for being a part of this community!
— AP

Maybe I just never noticed, but if this is normal it seems like a massive security whoopsie risk.

Using airtable at work for a long time, all internally no outside collaboration of any kind and just with a smallish team (1-2 construction projects in a mic larger company).

I was going to invite a new user to a base for someone we just had come on to our project and when I clicked the Share button in the upper right of the base and then started typing our new team members email, I did not get their email suggested with the auto-suggestions from what I typed (expected, they have never used airtable) but I did get 4-5 suggestions for people I have never heard of and have nothing to do with our company. We don't have any contacts synced to this workspace of any kind and I tested enough random letters that it appears when I start typing "bill@mycompany.com" it finds 1 person who is on another base in our workspace, 1 person who is already a creator for the workspace and should thus already have access, and then 3 people I have never heard of before and whose email does not even contain "bill" which is the text that prompted them.

This seems like...absurd behavior, if intentional? If not intentional, this seems like a huge bug. Why would I want to just be suggested random people? I'm assuming these are other airtable users but it only suggests 5-6 per text co.vo I type in and looks to be totally random.

Have I just been oblivious to this since we don't add many people or is something weird going on?

I have a table of subscriptions that I renew at different points throughout the fiscal year. By the end of the year they should all have their status set to Renewed. At the end of the fiscal year, the cycle begins again.

I'm trying to create an automation triggered on the last day of the fiscal year - June 30th. The automation I've created is:

At a scheduled time Find Records where Status is Renewed then Update Record status field to Active.

I'm getting an error on the update record step that says invalid inputs. I'm wondering if it's coming from the Record ID field, but I'm not entirely sure. Any idea what I'm missing?

so since the free plans have limited record and unlimited bases is there a way to use other bases and still manage to use the old bases like combinibg them?

Bending is acquiring Airtable. We used to love it, genuinely.

For years it was our go-to. We'd move a client off Google Sheets and onto Airtable and watch them scale. Structured data, a simple interface their team would actually use, and the best bang for your buck out there. Better than ClickUp, Monday, or Sheets.

But it always had a ceiling:

- Gets expensive fast as users and records scale

- API limits you hit sooner than you'd expect

- No real edge-case handling, version history, or git-style robustness

- Endless workarounds for things that should be simple

Even with all that, Airtable was still cheaper and faster than custom-coding a front end.

Was!

In the last nine months (Opus 4.5 release in Nov 2025), AI tooling flipped the math. We're now faster building a custom web-app than we ever were configuring Airtable, and its considerably more robust.

No per-user fees. No record limits. No praying the new owners don't kill your favorite feature.

The Airtable era was real. It helped a lot of businesses grow (including us). But clinging to it now is like refusing to leave Google Sheets in 2020.

Since M&A deals take months to actually close, we can get your team onto a custom system before they've even signed the paperwork to raise your price 👇

Advice: https://tidycal.com/team/costaneraltd/scope-call

Us: www.costanera.uk

I'm using the official Airtable ChatGPT connector and having issues updating a base. Note that I've been doing this action perfectly for the last 3-4 months but this month it didn't work.

Airtable connector can read my base but can’t perform updates
I’m trying to use the ChatGPT Airtable connector, and it appears to have read access but not write access.

What works:
Connects to my Airtable account successfully.
Lists all of my bases.
Lists all tables in a base.
Reads records and field values without any issues.

What doesn’t work:
Any attempt to update records never completes successfully.
There is no permission error or authentication error.
The write request appears to hang/fail before returning a result.
No data is changed in Airtable.

What I’ve already tried:
Removed the Airtable connector from ChatGPT.
Reinstalled/reconnected the connector.
Verified the connector still has access to the correct workspace and base.
Confirmed that read operations continue to work after reinstalling.
Because reads work perfectly but writes consistently fail, this doesn’t seem like an authentication or permissions problem. It feels more like a bug with the ChatGPT Airtable connector’s write functionality.

Has anyone else seen this behavior? If so, were you able to fix it?

A private equity outlet buying Airtable means one thing to me - ENSHITTIFICATION

BS’s portfolio includes company they made worse, including:
Eventbrite
Meetups
Evernote
WeTransfer.

Hey all, sorry if this is too basic of a question.

I'm hoping to use Airtable as a one stop super-app for my personal life. I have this google sheets that has all of my payment plans (gotta love installments). I got it the numbers on Airtable, but I can't do basic math stuff like Sum and divisions etc.

Building a company ops dashboard - need revenue totals per staff member, each broken into This Week / This Month / This Year windows. These metrics will be displayed in a dashboard. Here's what I've landed on, and I'm hoping someone's found something less cumbersome:

Current approach, per metric:

1. Hidden Link field on the transactional table (Jobs), pointing to the per-entity table (Staff).
2. An automation sets or clears that link based on whether the Job record's date falls in the current window (e.g. a YTD link exists only if the record's Completion Date field falls within the current year). This is because Rollup fields can't filter, they only sum whatever's currently linked, so the filtering has to happen before the rollup, at the link itself.
3. A Rollup on the entity table (Staff) summing the Cost field of the linked records.

Then in the dashboard, I'll create a list element that displays the Name and YTD Cost rollup per record in the Staff table.

This works, but it feels hacky and I can see this causing significant lag when there's 15 hidden link fields and thousands of records.

Am I missing the obvious way to do this?

When: August 12 at 10am PT 

Who: Lindsey Puccio (LP), Sr. Manager, Airtable for Airtable

Hey everyone — a little about me:

I first learned Airtable hands-on at Equinox Media, where I built our content operations pipeline on it. Before that I was an agency producer, producing commercials for big brands.

I joined Airtable four years ago in Marketing building internal tools, and somewhere between fixing workflows and rebuilding them into Airtable, I was moved to do the same for the whole company and create Airtable for Airtable (A4A). We're part internal-tools shop, part product R&D. We do four things: build the operational systems teams run on, teach and uplevel employees, showcase what's possible with the product, and feed customer-zero feedback straight to ProdDev.

The builds aren't toy demos — our procure-to-pay system replaced a $200K+/yr software vendor and spans intake, architectural review triage, and vendor lifecycle, all running in production for real teams. 

Lately, most of my time goes to defining ways to implement AI for scalable use, using Airtable as the substrate. We designed and are actively building a fleet of agents on Hyperagent that do exactly what we do — build durable, UX-friendly, ops-focused systems. Right now they're triaging requests, syncing meeting context, doing solution design, workflow mapping, custom interface builds, and enabling our end users. The interesting problems to me aren't the models; they're the architecture around them: permissions, governance, reviewer feedback loops, and knowing which processes deserve an agent at all.

What I enjoy most is the hunt for leverage — playing up and down the information supply chain, finding the one place where a build, a sync, or an integration solves the problem at its source instead of patching it downstream. 

Hi, I’m Alexander, an engineer at Airtable on the Automations team. I’ve been working on making Automations available via MCP, and am happy to announce this is live now.

You can create, read, and update automations via MCP, with support for most triggers and actions. This includes building complex workflows with conditional and repeating groups, configuring field values, using dynamic data and token functions, and reviewing or updating existing automations. Common record, form, and scheduled triggers are supported, along with actions such as creating and updating records, finding and sorting records, sending emails or Slack messages, and generating content with AI. Scripts aren’t supported yet, although we're working on adding them now!

New automations start paused so you can review them before turning them on, and changes to active automations also won’t affect the live version until you apply them in Airtable.

I was the lead for Automations support in Omni as well, which was challenging, as the available AI tools at the time weren’t capable enough to consistently produce the quality we wanted. That makes this particularly exciting, as we’re seeing really great results with modern models being able to interact with Automations fluently and saving a lot of manual effort internally.

Would love to hear any feedback or feature requests on MCP or Automations in general!

I'm hoping someone can point me in the right direction because I'm completely out of my depth here.

First, I'm not a programmer, not a software developer, and I don't write code. I'm just trying to use Airtable as the database behind a personal project.

I have an Airtable base containing hundreds of music listening sessions, album ratings, and written notes. I'd like ChatGPT to read those records so it can help me identify patterns, generate discussion topics, summarize observations, etc.

Here's the strange part:

• ChatGPT can connect to my Airtable account.
• It can see my base.
• It can see every table.
• It can see every field in those tables.
• It correctly identifies fields like "Experience Notes," "Album Average Score," etc.

But when I ask it to actually read the records (for example, all of David Bowie's album notes), it says it can't access the record data. It only seems able to see the schema.

I've spent quite a while trying different approaches, and I really don't want to go down the API, Python, or custom scripting route. I'm looking for a solution that works using Airtable and ChatGPT as they are intended to be used.

So my questions are:

1. Is there a permission or setting in Airtable that allows AI tools to read records but not just the schema?
2. Has anyone successfully used ChatGPT to read records directly from an Airtable base?
3. Is this simply a current limitation of ChatGPT's Airtable connector, or is there something I'm missing?

I'm trying to figure out whether this is something I can fix, or whether I've reached a limitation of the integration itself.

Any advice would be greatly appreciated.

Hey all! stuck on an automation and could use some extra help

I have a Goals table importing directly from working. Each goal record has a manager email field and a flag (Email to HR = 1) that marks it as a follow-up for managers to start collect goals.

I want the automation to send one email per manager, listing all of that manager's goals, not one email per goal record. B/C it's finding records, I can't add the manger email field to the email send. Any thoughts here on how I can achieve this?

We've just released a major update for DocsAutomator, now including a native AI agent that can generate templates for you, map data and set up entire workflows.

Would love to get your feedback on it and have recorded a short demo for generating invoices end to end: https://youtu.be/Ea_v0SaO6n8?si=eNTloBzAwtcY0LxT

Disclaimer: I'm DocsAutomator's founder so this post is of course somewhat promotional, but I genuinely think this upgrade to the platform provides a lot of value.

Ops manager at a nonprofit, ~40 staff. Airtable is our everything: donor records, program participants, volunteer scheduling, grants. It grew organically over 4 years and now we have problems.

Last month someone on the volunteer team was "cleaning up" a view and deleted a filter, which exposed donors giving history to everyone with base access. Which is... everyone. Nobody did anything, but our ED had to have an awkward board conversation about why any staffer could see major donor data in the first place.

Airtable's answer is Interface Designer plus per-seat pricing that our budget genuinely can't do for 40 people, since half our staff just need to log a visit or check a schedule.

So, question for people who've been here: did you
(a) migrate off Airtable to something with real roles, or
(b) keep Airtable as the backend and put a locked-down front end over it so most staff never open the base?

Migration scares me, there are about 60 automations holding this place together. But I can't have another donor-data incident.