Records and lists
A list defines the fields that a team uses to store and display records. A record is one live entry, such as a prospect with a name, status, and last contact date. An app can show records through a grid or board.
Define a list
Section titled “Define a list”Columns and ownership
Section titled “Columns and ownership”A Studio list resource has a stable key, teamId, revision, and definition.columns. Each column declares a unique key, label, type, and whether it is required. Studio supports text, number, boolean, date, select, image, and json columns. Apps and publications refer to the column key. Renaming the visible label can leave those bindings intact.
{ "key": "list.meeting-desk.summaries", "teamId": "meeting-desk", "revision": 1, "archived": false, "kind": "list", "definition": { "name": "Meeting summaries", "description": "", "language": "en", "columns": [ { "key": "summary", "label": "Summary", "type": "text", "required": true } ] }}Populate and verify records
Section titled “Populate and verify records”Publication projection
Section titled “Publication projection”A publish_list step declares the publisher key and maps individual fields. Bind it to the destination list with the owner’s allow-list and applicable consent. Meeting desk maps summary from /input/summary. A private source attachment or attendee list stays in its original scope unless explicitly mapped and authorized. Use a provider or runtime receipt to confirm the record write.
Definition and record revisions
Section titled “Definition and record revisions”Validate dependent views, pipelines, and publications before changing a column type or removing a column. When updating a record, recheck its current state and use the expected version supported by the operation. Data inside the list remains workspace state when its definition is published.
See pipelines, apps, and record publication.