Overview

A table is a grid of typed columns in your workspace, like a spreadsheet with a schema. Use one to hold reference data, collect what your workflows produce, or store the structured records your agents read and write.

Column types

Every column has a type, which decides how its values are stored and validated.

Type	Holds	Example
Text	A free-form string	`"Acme Corp"`
Number	A numeric value	`42`
Boolean	`true` or `false`	`true`
Date	A date	`2026-03-16`
JSON	An object or array	`{ "tier": "pro" }`

Types are enforced as you enter values, so a Number column only takes numbers.

Editing a table

Open the Tables section in the sidebar and click New table to create one. Add columns from the column header, type into a cell to edit it, and paste rows from a spreadsheet to bulk-load. Filter and sort from the toolbar without changing the underlying data. The editor has full keyboard support; see keyboard shortcuts.

Tables in workflows

A Table block reads and writes rows from inside a workflow: query rows for reference data, write results back, or process a batch. A workflow column goes a step further and runs a workflow against each row on its own. Everything in a table is also available over the REST API.

Using tables in workflows

Read, write, and update rows with the Table block.

Workflow columns

Run a workflow against each row of a table.

Keyboard shortcuts

Navigate and edit a table from the keyboard.

Common Questions

Tables are built for working datasets. For very large ones (100k+ rows), paginate your API reads or split the data across multiple tables.

Yes. Copy rows from any spreadsheet and paste them straight into the table; the values are validated against the column types.

No. Tables store raw data. Use workflow logic (a Function or Agent block) to compute values and write them back.

Yes. Writes are atomic at the row level, so multiple workflows can write to the same table at once.

Use the Table block: select the table, choose an operation (query, insert, update), and configure the fields.

Yes. Tables are workspace-scoped and available to all members with the right permissions.

In the table editor, Cmd/Ctrl+Z undoes recent cell edits, row insertions, and row deletions. Changes made through the API are not part of the editor's undo history.