Turn your business data into AI workflows and custom apps. Connect any system, migrate any data, and build anything that fits your business 100%.
This is the 3rd launch from Teable. View more
Teable 3.0
Launched this week
Turn your business data into AI workflows and custom apps. Connect any system, migrate any data, and build anything that fits your business 100%.
Free Options
Launch Team / Built With
Being able to migrate linked records and attachments instead of only importing flat spreadsheets is a really valuable detail in my view. How much manual cleanup is typically needed after moving a more complex Airtable setup into Teable?
Teable
@nico_mandera Just ask GPT-5.6 sol to do it, 0 manual job! check then you can start building a new fully automated AI workflow in Teable !
Teable
@nico_mandera it’s more of a quick check than a cleanup job 😄 Linked records and attachments come along for the ride!
Teable
@nico_mandera Great question! Nico. No manual work is needed, unless you’d like to give everything a quick check before getting started.
Athena by Shoplazza
Congrats on shipping Teable 3.0! 🎉 "Connect any system, migrate any data" is a bold promise — curious how deep the AI goes on the migration side: does it auto-detect schema/field types from messy source data, or do you still need to map fields manually before it builds the workflow?
Teable
@ryancheng Thank you! And yes—the AI goes beyond moving rows. It can understand messy source data, infer schemas and field types, and help map relationships before building the workflow. You can still review and adjust everything, but you’re no longer starting from a blank mapping screen.
Teable
@ryancheng From an ops perspective, this means less setup work and fewer mistakes. The AI handles most of the mapping first, and you just review and adjust anything that needs attention before moving the data.
Teable
@ryancheng Great question! Teable AI can identify schemas and field types even when the source data is messy, then map them automatically. You can adjust anything if needed.
ReadPo
This looks useful for franchise operations. Each location could submit data through an app while the central team runs approvals, reporting, and exception handling from one source of truth.
Teable
@blueeon Perfect Teable use case! Each location gets a simple app tailored to its daily work, while headquarters manages approvals, reporting, and exceptions from one trusted source of truth.
Teable
@blueeon You nailed it. Giving each location a focused way to work while keeping the central operation connected is exactly the kind of setup Teable supports well.
the "build anything that fits your business 100%" part is the ambitious bit - when the AI spins up a custom app from your tables, does it set access/permission rules on its own or is that still a manual pass per app?
Teable
@sabber_ahamed Permissions are part of the system the AI builds within—not an afterthought bolted onto the generated app. Agents operate inside defined access boundaries, and every action is logged and traceable.
You still retain final control and can review or refine access rules for each app.
Teable
@sabber_ahamed Sabber, Teable AI can handle the access setup as part of building the app, and you can review or adjust it for each app.
Congratulations on the launch!
natural language application building has huge potential. can multiple team members collaborate with the same AI agent simultaneously? how does collaboration work in shared workspaces?
Teable
@avery_thompson2 Absolutely. Teable is designed for shared workspaces, not isolated one-person AI sessions. Team members collaborate around the same live data, apps, and workflows, while agents can have distinct responsibilities and permission scopes. Every action is logged, so the team can see what happened, who initiated it, and what the agent changed. The goal is shared AI context without sacrificing control or accountability.
Teable
@avery_thompson2 Thank you! Shared workspaces are central to Teable. Team members work with Teable AI around the same live data, apps, and workflows, with permissions and a clear history of every change.
What am I missing? If I have data in a spreadsheet, using the spreadsheet as a db, why would I move the data into Teable? Maybe I am too tired but I don't understand the value prop and the problem this solves. Maybe someone can explain? Thank you!
Teable
@rusutraiancristian
That’s a completely fair question. If your spreadsheet is personal, relatively small, and mainly used for calculations, you may not need to move it.
The problem appears when the spreadsheet starts running the business: multiple people edit it, records need relationships, access must be controlled, changes must be audited, and reminders, approvals, reports, emails, or custom interfaces have to be built around it. At that point, teams usually glue together more spreadsheets, scripts, automation services, and internal tools—and eventually nobody fully trusts or understands the system.
Teable keeps the familiar table experience but puts real PostgreSQL underneath it. Then it adds relational data, permissions, auditability, automations, custom apps, and AI agents in the same environment.
So the value isn’t “another place to store spreadsheet rows.” It’s turning business data into a trustworthy system that can actively run the workflow around it—without losing the flexibility that made the spreadsheet useful in the first place.
Teable
@rusutraiancristian Rusu, I get where you’re coming from. If your spreadsheet already does everything you need, there’s no reason to move it. Teable becomes useful when that same data needs to support a growing team, controlled access, automations, AI workflows, and custom apps.
@jocky @bieber_chen thank you to both of you.
used airtable for years with a pretty deep web of formulas and automations tied to slack/zapier. the pitch of 'migrate any data' sounds great until you hit the automations layer specifically - does teable actually rebuild those triggers/actions during import or just bring over the raw tables and leave you to rewire the logic by hand?
Teable
@omri_ben_shoham1 That’s a fair challenge. We don’t pretend every deeply customized Airtable + Slack + Zapier system can be imported with perfect behavioral parity in one click. Moving tables is easy; reconstructing years of automation assumptions is the hard part.
Our goal is more ambitious than creating a frozen copy. Teable preserves the relational foundation, then lets you rebuild—and often improve—those triggers and actions as freely customizable AI workflows. Instead of leaving the logic scattered across Airtable, Zapier, scripts, and Slack integrations, you can bring the data, automation, apps, and agents into one operating environment.
We like to call it a 200% migration: preserve what matters, then build something more capable than the system you left.
Teable
@omri_ben_shoham1 Once your data and relationships are in Teable, tell Teable AI how the automation should behave, and it can turn that logic into a workflow you can keep refining.