Fields overview

A field is a typed column in a table. Every cell’s value is validated and normalized against its field’s type when written — from the grid, the API, or an automation — so your data stays consistent.

Every field supports

• Description — optional helper text shown in the field editor.
• Required — reject empty values (on the types that support it).
• Default value — pre-filled into new records (on the types that support it).

Groups of fields

• Text — single line and long text, with optional length and pattern rules.
• Numbers — number, currency, percent, with precision and min/max.
• Choice — single- and multi-select with colored options.
• Date & time — dates, optionally with a time component.
• Contact — email, URL, and phone, each validated for format.
• Attachments — uploaded files.
• Relationships — link records to records in another table.
• Interactive — a button that triggers a webhook.
• Structured — JSON.
• Computed (read-only) — Formula, Template, and Code derive a value from other fields in the same row.

See the full Field types reference for the specifics of each.

Computed fields

Computed fields are read-only — you can’t type into them, and the API rejects writes to them. Their values are materialized (stored) into the record whenever the fields they depend on change, so they work everywhere a normal value does: filtering, sorting, grouping, API reads, and public shares all see the computed result.

• Formula and Template recompute synchronously as you edit.
• Code recomputes asynchronously in a sandbox a moment after a write.

There’s one ordering rule worth knowing: formula/template run first, then code. So a code field can read a formula’s value, but a formula reading a code field’s value will pick it up on the next write. See each page for details.