Fields
25 types: rupee amounts, percent, Indian dates and IST times, selects, team members, attachments, links with lookups and rollups, formulas and auto-numbers by financial year.
Your own records, in the views you work in
Keep custom records in bases and tables with typed fields, linked records and saved views, and share them with the team.
Bases hold up to 30 tables of up to 100 fields and 20,000 records each. 25 field types: text, long text, number, currency (₹ by default; 1,20,000 or ₹1.2 lakh can be typed), percent, date (typed day first, shown as 12 Nov 2026), date-time in IST, checkbox, single and multi select with coloured options, team member, email, phone (+91), URL, rating, attachment (R2, up to 25 MB), two-way links, lookups, rollups (sum, count, min, max, average, joined text), formulas with {Field name} on a copy of the Sheets formula engine, auto-numbers such as PREFIX-2026-27-0001 with a financial-year reset, and created and updated time and by. Each table has views: a grid (windowed rows, column resize, groups and a summary bar), kanban by a select, member or checkbox field with drag and drop, a month calendar by a date field, a gallery with attachment covers, and a list; each view has its own filters (all or any, nested groups, operators such as 'is me' and 'this week' in IST), sorts, grouping, hidden fields and field order, and is shared or personal. A record drawer edits every field and shows comments, the change history and linked records; other people's changes arrive by polling every five seconds (no Durable Object and no live cursors). Private by default with people or team sharing; /v/<token> publishes one view read-only with its filter and visible fields. CSV import guesses column types (rupees, percent, phones, dates, selects) into a new base, a new table or an existing table with column mapping, and every view exports as CSV; seven templates (CRM-lite, inventory, content calendar, hiring tracker, vendor list, asset register, event planning). Forms intake: connecting a form to a table gives a signed webhook URL, and each form response becomes one record, only once. For the appneural.com hosts, Forms can deliver there only after a forms-catalog change that is not deployed yet; until then, responses come in by exporting a CSV from Forms and importing it here. GET /api/v1/bases and records CRUD on /api/v1/tables/<id>/records with filters, sorts and paging by field and option names, webhooks base.created, base.shared, record.created, record.updated and record.deleted, a workspace feed of tables and records, and Claude to propose tables from a description, fill a field for chosen records as a proposal and summarise records.
What Tables does for you.
25 types: rupee amounts, percent, Indian dates and IST times, selects, team members, attachments, links with lookups and rollups, formulas and auto-numbers by financial year.
Grid, kanban, calendar, gallery and list, each with its own filters, sorts, grouping and hidden fields, shared or just for you.
Private until shared; publish a view as a read-only link; CSV import and export, a records API and webhooks.
A suggested path for Tables. What you can do depends on your access in the app.
Pick one of seven templates, import a CSV, or describe the table and review what AI proposes.
Add the views people need, each with its own filters, sorts and grouping.
Type them in, import a CSV such as a Forms export, or write them through the records API.
Live host, inventory, governance, health checks, verification, dependencies and history.
Bases hold up to 30 tables of up to 100 fields and 20,000 records each. 25 field types: text, long text, number, currency (₹ by default; 1,20,000 or ₹1.2 lakh can be typed), percent, date (typed day first, shown as 12 Nov 2026), date-time in IST, checkbox, single and multi select with coloured options, team member, email, phone (+91), URL, rating, attachment (R2, up to 25 MB), two-way links, lookups, rollups (sum, count, min, max, average, joined text), formulas with {Field name} on a copy of the Sheets formula engine, auto-numbers such as PREFIX-2026-27-0001 with a financial-year reset, and created and updated time and by. Each table has views: a grid (windowed rows, column resize, groups and a summary bar), kanban by a select, member or checkbox field with drag and drop, a month calendar by a date field, a gallery with attachment covers, and a list; each view has its own filters (all or any, nested groups, operators such as 'is me' and 'this week' in IST), sorts, grouping, hidden fields and field order, and is shared or personal. A record drawer edits every field and shows comments, the change history and linked records; other people's changes arrive by polling every five seconds (no Durable Object and no live cursors). Private by default with people or team sharing; /v/<token> publishes one view read-only with its filter and visible fields. CSV import guesses column types (rupees, percent, phones, dates, selects) into a new base, a new table or an existing table with column mapping, and every view exports as CSV; seven templates (CRM-lite, inventory, content calendar, hiring tracker, vendor list, asset register, event planning). Forms intake: connecting a form to a table gives a signed webhook URL, and each form response becomes one record, only once. For the appneural.com hosts, Forms can deliver there only after a forms-catalog change that is not deployed yet; until then, responses come in by exporting a CSV from Forms and importing it here. GET /api/v1/bases and records CRUD on /api/v1/tables/<id>/records with filters, sorts and paging by field and option names, webhooks base.created, base.shared, record.created, record.updated and record.deleted, a workspace feed of tables and records, and Claude to propose tables from a description, fill a field for chosen records as a proposal and summarise records.
Free-form calculations belong to Sheets; the forms themselves belong to Forms; customer records belong to Customers and Contacts.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
tables.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.