Build with Gemini
Build business apps with Gemini. Keep the rules in the database.
Use Gemini to reason about your data model and write an interface, or build an agent that calls gtable's REST API. The model generates the plan; the database enforces access.
Start with the business, then shape the app
A useful brief names the people, the records they work with and what each person is allowed to do.
- Design the relationships
- Ask Gemini for a schema with stable links between clients, projects and tasks, plus clear ownership fields for the permission rules.
- Describe the contract
- Use the API document generated for your identity. It names only the tables and fields that credential can read.
- Keep secrets server-side
- A custom agent calls the API from a trusted backend. Do not place API keys in generated interface code or a browser bundle.
Give Gemini a way to work as you
Use a Gemini-based tool that can call REST with your scoped gtable credential, or an MCP-capable host with OAuth support. This page does not assume the consumer Gemini app has a native gtable connector.
- Builder access
- The Studio's machine surface is for the app definition: tables, fields, groups and permissions. Connect using a builder identity when designing an app.
- User access
- A suite connection is for the apps you may use. It carries your identity and can be narrower than your account, never wider.
- Review changes
- The in-app assistant asks before applying its proposed writes. External clients must follow their own approval workflow; an API credential still obeys your permissions.
A model's ability to generate code is different from a client's ability to connect. The Gemini route here is an API or compatible-host workflow, not a promised native connector.
A brief worth giving your agent
“Design a client-delivery app with Clients, Projects and Tasks. Link tasks to projects and projects to clients. Consultants work on their assigned projects. Clients see only their own projects. Add an overview of overdue tasks.”
Treat this as a starting brief, not a command that bypasses setup. Review the proposed schema and permission rules before using real data.
Your assistant can change. Your access rules stay.
- One model
- The grid, generated interfaces, REST and MCP all ask the same permission compiler. Switching clients does not create a new route around it.
- What is available
- gtable is not open yet. These pages explain workflows for the product being built, not an invitation to sign up or a promise of a provider-specific integration.
Read the connection guide and the developer documentation for the exact API surface.