01
Create with Teable AI
Describe the records, roles and actions you need. Bring a spreadsheet or choose a data source, then use App Builder to create and refine the screens for your team.
Start with a briefFOR THE PEOPLE WHO BUILD THE SYSTEM
An internal tool builder for your team’s work
Keep data, sign-in and team workflows together. Build your internal app with Teable AI, Claude Code or Codex.
Design the workflow and try both sides
Choose an example, inspect its connected tables, then handle a request as a teammate. Carry the resulting blueprint into your app brief.
Interactive example · sample data
Connected tables
People
Name · Email · Team
Equipment
Asset ID · Type · Availability
Requests
Requester → People · Item → Equipment · Status
↳ Connect records with linked fields and stable IDs
Responsibilities
- Requester
- Submit a request and follow your own items.
- Operations team
- Review the queue, assign work and close requests.
Request lifecycle
- Submitted
- In review
- In progress
- Done
Your system blueprint
Build this internal tool in Teable. Use the following plan as a starting point. Equipment requests Connected tables People: Name · Email · Team Equipment: Asset ID · Type · Availability Requests: Requester → People · Item → Equipment · Status Connect records with linked fields and stable IDs Responsibilities Requester: Submit a request and follow your own items. Operations team: Review the queue, assign work and close requests. Request lifecycle: Submitted → In review → In progress → Done Test the published app with separate requester and operator accounts before inviting the team.
Turn the plan into your own internal tool
Describe your process, attach a spreadsheet or add a data source. Start free in Teable.
- Build an equipment request app with linked People, Equipment and Requests tables, a personal request page and an operations queue.
- Turn our purchasing spreadsheet into an internal app with request forms, reviewer decisions and a delivery status.
- Build a support intake system with request ownership, status updates and a team workload view.
Use this plan in your brief
System brief
Trusted by teams at
What is an internal tool builder?
An internal tool builder turns your team’s data and recurring work into an app: submit a request, review it, assign it and track the result. Teable combines related tables with editable app screens. The builder maintains the model and access rules; colleagues update records and handle their tasks.
Build internal tools your way
Start without hand-writing code, keep working with your agent, or develop the app in a repository. Each path builds on the same Teable data.
02
Use Claude Code or Codex
Add the Teable Skill or configure MCP in a compatible agent. Work on your tables and system structure from the coding workflow you already use.
Set up your agent03
Develop and review the code
Download and import app code when you need direct edits. Cloud Business and above adds two-way GitHub sync for repository-based development and code review.
See the code workflowHow to build internal tools in Teable
01
Map one process end to end
Name the requester, reviewer and operator. Define the required fields, decision and finished state before generating screens.
02
Connect data and create the app
Use a small spreadsheet sample or supported source. Define related tables, then build the interface with Teable AI or your coding agent.
03
Test roles and exceptions
Try separate accounts. Check record access, missing fields, rejected requests and the path from submission to completion.
04
Publish and hand it over
Invite the intended team, name a maintainer and document everyday updates. Retest the affected workflow when data structures or access rules change.
01
Build your internal app on linked data
Keep people, requests and resources in related tables. A request points to its owner and the item it concerns, instead of copying names across sheets. Build the interface around those relationships so a new screen uses the same records.
- Define the source of truth
- Import the existing spreadsheet, identify stable record IDs and decide which table owns each field.
- Give each screen a job
- Separate intake, review and operations views. Choose what information each step needs before adding more controls.
Start with the work your team already does
Use these briefs as a starting point. Replace the fields, decision rules and owners with your actual process.
Equipment requests
An employee requests a device; operations checks availability and records the handover.
Build an equipment request app with linked People, Equipment and Requests tables. Employees submit requests and see their own items. Operations reviews the queue, assigns an available asset and records the handover date. Include a return status and a view of outstanding loans. Test record access with separate employee and operations accounts.
Purchase approvals
Department leads review purchases while the purchasing team follows approved orders through delivery.
Create a purchasing app with Departments, Vendors and Purchase Requests tables. Collect an item description, total, department and needed-by date. Route each request to its department reviewer, retain the decision and show approved items in a purchasing queue. Track ordered and received dates. Provide an overview of pending decisions for the process owner.
Internal service desk
Teams submit issues once, then follow ownership and progress from the same record.
Build an internal service desk with linked Teams, Services and Tickets tables. Let colleagues choose a service, describe the issue and follow their ticket status. Give the service team an assignment queue and a view of unassigned work. Record the resolution before closure. Add a handover page explaining who maintains each service and its routing rules.
02
Turn the prototype into a role-based team app
A good internal tool works for the person who did not build it. Add app sign-in, decide who can submit and review, and make the next action visible. Configure table permissions and app access for their respective jobs.
- Test with real roles
- Try separate accounts and check both record visibility and permitted actions. Hiding a button alone does not protect data.
- Leave a usable operating guide
- Document who owns the system, how to resolve a stuck request and where teammates can change everyday data.
03
Connect existing data before adding another screen
Use the source picker to add supported connections or read a webpage for context. Keep credentials in the app’s credential settings. Builders using Claude Code or Codex can use Teable’s Skill and MCP to work with their workspace.
- Keep integrations explicit
- Choose the connection and the records the app needs. Test an import on sample data before replacing a team’s live process.
- Plan changes after launch
- Review app code, check affected workflows and retest access after changing a schema or role. App code rollback does not restore database changes.
Build internal tools with your coding agent
Add Teable’s Skill to your coding workflow or configure its MCP endpoint. Let the agent work with Teable data and system structure while your team uses the resulting app and tables.
Read the setup guideInstall the Teable Skill
npx skills add teableio/agent-skillsTeable MCP endpoint
https://mcp.teable.ai/mcpConnect an authorized Teable account when setting up your agent.
Choose where you want to spend maintenance effort
| Your starting point | Spreadsheet + inbox | Self-managed code stack | Teable |
|---|---|---|---|
| Shared data | Reconcile copies and message threads | Design and operate the data layer | Related tables shared by apps and the team |
| Access | File sharing and manual routing | Implement and test authentication and rules | Configure app sign-in and table permissions; test role access |
| Changes | Adjust sheets and explain the new process | Update code, infrastructure and integrations | Edit records and views; review app and schema changes |
| Best fit | A small, occasional process | Custom runtime or infrastructure requirements | Business workflows with structured data and ongoing collaboration |
Builders turning tables into working systems
Read how Teable users bring data, apps and everyday workflows together.
Leo
AI Systems Builder · AI SCWORK
🧨 Teable does not just compete with Airtable. It exposes what Airtable is missing. Modern teams do not need nicer spreadsheets. They need operational systems that can run themselves. Teable turns tables into workflows, AI actions, and internal apps.
Anas Riad
AI Consultant & AI Engineer · Adway
Teable 3.0 feels like a grown-up spreadsheet. It keeps the familiar grid and adds automations, AI actions, and internal app building in one platform. I finally got the control model I used to assemble manually.
Aman Chadha
AI Leader · Google DeepMind
I used Teable for a team with leads spread across sheets, CRM exports, and automations. We now import, follow up, and track dashboards in one flow. One system replaced half a dozen disconnected tools.
Questions before you build
Can I start building internal tools for free?
Yes. Teable’s Free plan includes App Builder. Start with a small workflow and a sample dataset. Check the pricing page for current AI allowances, capacity and collaboration limits. When you need more capacity or plan-specific features, choose the appropriate plan.
Is an internal app builder different from an internal tool builder?
Both terms describe building apps for work inside a company. Here you can plan linked data, roles and a repeatable workflow, then use Teable App Builder to create the app. Your app and team work with the same records.
Can I keep using Claude Code or Codex?
Yes. Use Teable’s Skill or MCP with a compatible agent. App Builder also supports code download and import. Two-way GitHub sync is available on Cloud Business plans and above, so you can review and develop app code in a repository.
Can I begin with a spreadsheet or existing source?
Attach a spreadsheet or choose a supported connection in the input area. Add the source, the fields you need and the intended action. Webpage reading can supply context for the brief; the connected tables should hold the records your workflow uses.
How do colleagues sign in and get the right access?
Configure the app’s login options and intended audience, then set the relevant data permissions. Decide what each role can view and change. Test the published app with separate accounts before inviting the wider team.
Can non-developers maintain the data?
Yes. Teammates can update records in Teable tables and use the app’s forms and actions. Give each person suitable permissions and document the process. Structural changes to the app or database should still have a responsible owner.
Can customers or suppliers use the system too?
You can build a dedicated portal and configure app access for the intended audience. Keep internal operations and external-facing views clearly defined, and test each audience’s access. Use the client portal and vendor portal guides to plan those workflows.
What happens when the system needs to change?
Update the affected tables, app screens and rules together, then retest the workflow. App version history can help manage code changes; database records and schema changes need their own backup and change process. Keep the maintainer and handover guide current.
