Airtable Data Sync Updates: What's New, What's Coming, and What to Know

Hey everyone,

With our updated data sync for Airtable coming to completion in the coming days, there are some updates you should be aware of regarding Airtable Views, a few known issues we’re actively fixing, and some exciting features on the way.

Airtable Views

With the new data sync model, we’ve changed how Airtable Views are handled:

  • Existing blocks using Airtable Views continue to work normally. These blocks will remain on the old syncing mechanism and won’t be affected by this migration.
  • New blocks cannot be filtered with a View. When creating new blocks in the updated data model, you’ll need to connect directly to the Airtable table and filter with Softr conditional filters rather than a specific View.

If you need to use Views right now, here are your options:

  1. Use legacy blocks, which still support Views
  2. Duplicate an existing View-backed block and modify from there

That said, most of what Views offer can be achieved directly in Softr Studio using conditional filters. And once this migration wraps up, we’ll be extending our conditional filtering capabilities to include grouping with AND/OR logic early next year. This will make it even easier to replicate View-like functionality natively in Softr without relying on Airtable Views at all.

Known Issues We’re Fixing

Read-only fields not updating immediately – When a read-only field value changes in Airtable, it’s not syncing to Softr right away. This is due to a limitation in the Airtable API (their metadata doesn’t update when read-only fields change). We’re working around this and expect a fix next week.

Deleted data sync delay – Data deleted in Airtable currently has a small delay before it’s removed in Softr. We’re optimizing this and expect a fix next week as well.

What’s Coming

With this new syncing mechanism wrapping up, Airtable users will start getting access to some of our latest features, including Ask AI, inline editing, and more. Some of these may already be available to you. The rest will roll out over the next week or two as we finish this migration.

The Bigger Picture

I know it might feel like this transition is creating more problems than it’s solving. But once complete, this new data model will be well worth the wait. It’s designed to help you build faster, more scalable applications with Airtable than ever before.

Questions? Drop them below.

6 Likes

Very excited about these improvements! (And all of my team who doesn’t know they’re coming are going to not notice and still benefit greatly from them!)

Will I be notified in Studio as these new features roll out or should I just keep an eye out here?

2 Likes

We will be sure to notify in studio + forum + social media as best we can =)

1 Like

Awesome update. Thanks.

Great News, lets keep our figures crossed that it solves some of the slow updating, formular and lookup field issues.

Is there any way to join a beta features program? I am really curious to checkout these airtable updates asap :smiley:

Airtable updates have since rolled out to everyone. You should be experiencing them already =)

2 Likes

Yes, thanks. forgot to build new blocks, as you mentioned :slight_smile:

1 Like

Should the issue with Read-only fields not updating immediately be resolved now or is that still in progress?

Still in progress. Hoping to have it live tomorrow or by EOW latest.

1 Like

This was posted 21 days ago. As of this week, users deleted in Airtable are not then immediately deleted in Softr when advanced user sync settings are set to do so. It was working for a short period last December, but now there is either a significant lag or sync must be manually triggered after this lag for Softr user is deleted. What we were told this past year was that AT DSV2 would “handle” this. @artur, can we have the status (explanation) as to why this doesn’t work as intended?

I am seeing changes in airtable that are 20 minutes (edit: 2 hours old, still not updated), not reflected in Softr. For more than 24 months our app has functioned without issue until December of 2025 and almost daily issues now. Very unnerving. Hopeful this is actively being worked.

How does Softr handle the Airtable information when I apply filters within Airtable? Previously if I filtered my data in Airtable (on the main table), it would affect what was shown in Softr. That’s why I ended up creating views that Softr was linked to, which always showed all the data and I didn’t have to worry about my changes in Airtable affecting what clients saw in Softr.

If I filter my main Airtable view, does that impact the information that Softr can access?

@flyingbren views don’t have impact and not recommended by Airtable to use outside their db view…

I would suggest using conditional filters

@BobbyBrooks are you using PAT or OAuth ?

@Ben if you use PAT it will be reflected fast within seconds…

We do use webhooks but sometimes need to scale up/down as Airtable bases get overloaded. when we start listening and acting on webhooks…

We switched to PAT at Support’s request but are still experiencing some delays, Softr Support has been in contact with me and will be reaching out to me tomorrow with more information.

I recently had the same conversation with the support and as far as I can recall correctly sync can take up to 6 hours if a table has over 300 record.

I had to sync my data with make into a softr database as a quick and dirty workaround fix (still using this workaround till today unfortunately)

We have 15,000+ records in more than one table and have had success for a long time so I’m hopeful we can get this sorted. Moving to a softr database seems like a lot of work, in the interim we built out a MiniExtension portal which is updating immediately so we can divert users to that portal if records are not found as a fall back.

We would need to know some details and check e.g. Airtable supports only 2 webhooks per base and perhaps other tools already consumed it and we can’t create a webhook to be updated on changes and so on… We used to work with Direct API but that is not scaling well with Airtable and now we do more cached version the downside is we need to rely on webhooks to keep cache up to date which is BTW the recommended approach by Airtable… We would also suggest to check if a single app is using a single integration or multiple as that has an impact too… 15K is not an issue we have users with bases ranging 100K - million and the system works… We need to see what are the specific in your case.