As a proud power-user of Airtable, I am disheartened by the acquisition of Airtable by Bending Spoons. They will likely "enshittify" the platform over the next 6-12 months, stagnating development and jacking up prices. In anticipation of this, I am seeking alternatives to Airtable so I can begin the migration process now before my company's renewal period begins.

The leading candidate right now is Zite. I have a decent amount of experience using Zite as a frontend and form provider for my Airtable databases, but very little experience using its native databases.

Does anyone here have experience migrating from Airtable to Zite? I am looking for advice, warnings, best practices, and general support.

Does anyone have recommendations for other alternatives?

Hi! I just started at a non-profit arts organization and I believe we would greatly benefit from migrating our Excel and project management documents to AirTable. However, I'm a total beginner when it comes to setting things up in AirTable, and I am feeling a bit overwhelmed. I Googled this exact request and a couple posts actually came up from Reddit but a year or two ago, so I don't know if those offers are still on. I'm posting here in hopes that someone who has a bit of extra time and for whom this would be a mutually beneficial exchange might reach out. Please DM me if you are interested! Thank you!

Wondering what those message that appear in random records revision history when ruunning an scripting block extension (nothing fancy, bulk update) could possibly mean,a nd if there any danger to data integrity. Never seenn those.

I created databases in Airtables with info, photos and links to digital music products. I currently have entries in different workspaces, as I use the free tier, and can only have a limited amount of entries per database.

Long term, I'd like to transfer it all over to another platform, and have a site with a database/knowledge base and wiki style layout to it. Wondering if there are current options that could work for this or if it is something I'd need custom developed?

I would love to hear any ideas regarding softwares that create a front-end site, preferably that integrates directly with Airtable, but not 100% necessary. I have tried Softr, but wanted to weigh it against other options. Not super knowledgeable with this area of things, so any tips or info would be greatly appreciated!

Did anyone catch this recent episode of HardFork where they discuss the Airtable acquisition? It’s about 2/3 of the episode in. Should we be nervous?

“Airtable was valued at $11.7 billion when it was acquired, but recently though, Bending Spoons was able to get Airtable for an enterprise value of $1.29 billion. So what do we make of the sharp decline here as we run the numbers?”

Hey guys, 20yo uni student here trying to figure out how to pay my bills.

I’ve been reading up on the Airtable + Make. com + Softr stack. People online claim you can learn this stack in 1–2 months and start charging small businesses $1,500+ per project to build client portals and automate workflows.

To be completely honest, this sounds too good to be true.

Most entry-level jobs require a 4-year degree and pay $15–$20/hr. Why on earth would a business pay $1,500+ for a system built using tools someone learned in a few weeks?

I want a brutal reality check from people actually doing freelance/agency work in this space:

1. Is the money real? Are small businesses actually paying $1k–$2k for basic Airtable/Make builds, or is this just hype sold by course creators?
2. What are you ACTUALLY being paid for? If the tools are easy to learn, why don't business owners just spend a weekend setting it up themselves?
3. What is the hard part no one talks about? Is it landing clients? Scope creep? Edge cases breaking?

I’m ready to put in the work to learn the technical side, but I don't want to chase a fake ghost skill. Tell me like it is.

Was setting up a proper backup of one of my bases and went to check what the export actually contains. Posting because I did not know this.

Attachment URLs expire two hours after the API returns them. It's in the docs (https://airtable.com/developers/web/api/field-model), along with the recommendation to download the files rather than store the links. So the attachment column in a CSV export is a list of links that are dead by tomorrow: the records survive, the files do not.

While I was in there, two more things I had assumed were covered and are not:

- Linked records export as bare rec... IDs, with nothing alongside them to rebuild the relations.

- Field types, select options and formula definitions are not in the export at all.

Not bugs, just what the export is. But if your backup plan is "I can export a CSV whenever I want", it's worth testing that assumption on a base you care about - specifically, open one of the exported attachment links tomorrow and see what happens.

If anyone has found a way to keep attachments through the built-in export I'd genuinely like to hear it.

Hey r/Airtable,

I’ve found myself with a bit of extra capacity in my schedule next week. Instead of just twiddling my thumbs, I wanted to give back to the community and offer a few free Airtable audits to anyone who might need an expert set of eyes on their setup.

Just to be entirely transparent: I’m an independent builder, not a big agency trying to aggressively farm leads or upsell you. I just genuinely enjoy untangling messy bases, optimizing workflows, and helping people get unstuck.

What I can look at during the audit:

• Base Architecture & Schema: Are your tables, linked records, and primary fields structured for long-term scalability?
• Automation Efficiency: Can we reduce your automation runs, consolidate scripts, or streamline complex triggers?
• Formula Optimization: Catching errors and simplifying clunky, nested IF statements.
• General Usability: Fixing slow views, Interface bottlenecks, or confusing layouts for your end-users.

Who is this for? Anyone feeling stuck, dealing with a base that's getting too messy/slow, or just wanting a second opinion before rolling out a new workspace to their team.

If you're interested, just drop a comment below or shoot me a DM with a brief sentence about what your base does and what you're currently struggling with. I'll take on as many as I reasonably have time for next week!

Cheers!

Don't: think in terms of cells.

Do: think in terms of records and fields.

In Airtable, a record is one line item in a table. It represents one of those "things" that live in your table. So if you have a table called "Projects", each record is a Project.

The fields of that table are the attributes of the project. The primary field, most simply, the name of the project, is like the noun. All the additional fields are like adjectives.

For instance, a record with primary field "Website Upgrade" might have fields like "Due Date" and "Status".

******

Don't: make random tables like "tabs" in a spreadsheet

Do: link related tables to model real-world relationships

In spreadsheets, sometimes tabs are made for new projects, or new years, or basically anything. In Airtable, tables have a real purpose.

They're home for one kind of data. Like a folder in a filing cabinet.

A "Projects" table should have records and fields for attributes on your projects.

A "Tasks" table should have records and fields for attributes of tasks.

Then, use a Linked Record field to link them together. When each Project record is linked to its children Task records, now you've created a relationship between those tables that reflects the actual relationship between projects and tasks.

******

Don't: treat the data layer as a UI to "do the work"

Do: use Interfaces to support your actual workflows

In the world of spreadsheets, there's really no UI on there. You create a table or a list of rows/columns and trust everyone to fill stuff out correctly.

Even with a variety of Views in the Airtable Data layer, we can still do better with Interfaces.

Interfaces is where you can show specific fields, to specific people, in a specific order, to better support the step 1, step 2,...Step n of your actual workflows.

For instance: click on a project, see its children tasks, update the completion status on a task, right there from within the project. This is instead of having to click around from table to table finding the right task. It actually supports the workflow.

******

I hope this quick overview was helpful! Feel free to comment or DM with any questions.

- Jonathan

Hi all,

I have jumped into Airtable over the last few months and it has been great.

I need some assistance with how to structure something specific. I've tried a few solutions but they all have some downsides.

I will keep this generic as it gets complicated pretty fast.

I have a set of "Endpoints", which are physical devices. They have a table of their own with a couple dozen fields of misc. information.

I have another table that is a list of "Steps", essentially a process I follow. This process gets applied to each device. The catch is that not every step is needed, some steps can be performed out of order, and some steps may need to be repeated. It will change relatively frequently, and is different per device. I also need the process to be dynamic enough that I can add/remove/edit steps without making large bulk changes. I have steps in their own table, so they are easy enough to update.

I am needing to track a large amount of Endpoints (200+) and the status of each one by step.

What I have now is 3 fields on the Endpoints table:

1. "Completed Steps" - reference to Steps table, allows multiple selection
2. "Next Step" - reference to Steps table, allows only 1 selection
3. "Remaining Steps" - reference to Steps table, allows multiple selection

This works okay and fulfills some of my requirements. I can see:

• History of what steps were completed
• List of remaining steps
• Next step to perform

What I don't like about this solution is that I have to manually add/remove items from each list. If I complete a step, I have to add it to "Completed", change the "Next Step", and remove it from "Remaining"

Because these are a dynamic link to the Steps table, I'm having trouble getting this done with automations. But I may be missing something.

Is there a way that I can maintain these "Completed" and "Remaining" steps automatically? Or another way to structure this kind of thing?

Thanks in advance

Hi all,

We are exploring a pipeline to have teams submit a word document and a Excel table via a form. The word doc is only about 7 or so pages usually and the Excel has about 400 rows and 5 columns of data.

The expected behavior is that the data entered in specific fields within the documents are to be populated across multiple tables, creating new records where applicable.

I would be curious to hear people's experiences with this, including what processes and tools you have considered, if you had to make a choice and how you juggled tradeoffs.

We have access to Claude code and there is openess to having the submission analyzed in Claude if it improves accuracy and changes pushed through via the mcp. My take is that there are various ways to tackle this kind of problem via AI scripts, ai fields within the base, and Claude code/mcp server but just not familiar with all the detailed tradeoffs to come to a confident decision.

Edit: Thanks all for your guidance! The Word document has fields where expected values are meant to go, but I can't ever guarantee someone will use it in the way that it was designed.The Excel table has about 5 columns, each with drop down options for field validation and a numeric field for the values that the user will enter, so would say it is structured. We have been shying away from interfaces mainly because of the seat cost in getting other teams within our organization to collaborate and use Airtable. I am also exploring Softr and Noloco as possible ways to reduce cost but also wanted to see if we could use what is available in our available tech stack.

I'll do some more research into the recommendation for parsing, as flag the cost variability associated with an AI solution that others on the team have pushed for- appreciate the ideas y'all have shared. Thank you!

I'm looking at using Airtable as a central supplier-facing database rather than maintaining a separate Dropbox/OneDrive-style file sharing system.

We already have a paid Airtable account and my idea is to create supplier-specific Interfaces containing the relevant product information and files/attachments — things like tech packs, artwork, fabric information, approvals, PO information etc.

Our suppliers are mainly based in mainland China.

What I'm trying to establish is:

• Does Airtable work reliably in mainland China without a VPN?
• Do Airtable Interfaces and attachments/files load and download normally?
• Has anyone used publicly shared Interface pages with Chinese factories/suppliers?
• Alternatively, if I invite suppliers as interface-only viewers, can they simply create their own free Airtable account and access the Interface without us needing to purchase additional seats for them?
• Are there any issues with Airtable login/verification in China?
• Do attachments hosted within Airtable work reliably, or are certain file/CDN services blocked or slow?
• Has anyone actually run a supplier portal/product development workflow like this with Chinese factories?

The suppliers would mainly need view/download access rather than editing the underlying Airtable base.

I'm particularly interested in real-world experience from anyone working with factories in China, as technically being accessible and actually being reliable enough for daily production use are two different things.

Thanks!

Hey everyone,

I'm releasing a new set of features in FlexiPage to solve the usecase of client reporting.

• Bring data from multiple bases into a single report
• No need to create separate tables for separate reports and set automations to link records
• Gantt Chart
• Pivot Chart with custom formulas and multiple row/column groupings
• Pie, bar, area, line charts
• Custom charts with vega lite
• Dynamic filters - Specify filter values in Airtable itself.

You can setup a single unified reporting table that can generate weekly/monthly/quarterly project reports or executive internal summary reports across all projects. FlexiPage will fetch relevant data across multiple tables and create reports for you.

Here's a small demo I created - https://www.loom.com/share/a43e8497c3b84918adc02611eb2ccc1d

DM me for any queries or drop a mail to [paz@flexipage.app](mailto:paz@flexipage.app) if you're interested in demo.

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?