01
Typed columns
Text, numbers, dates, choices, email, web addresses and JSON, each checked as it is entered.
Your records, in the workflow.
No separate database.
Keep the lists your team relies on next to the work that uses them. Workflows read and update the same rows people see.
See how they workSTRUCTURED, NOT RIGID
A table that keeps itself tidy.
Rules catch mistakes when data comes in, whether a person types it, a file brings it or a workflow writes it.
02
Rules that hold
Make a column required or unique, or give it a default. Every way of writing a row follows them.
03
CSV in and out
Import a file or paste from a spreadsheet, with line-by-line results. Export any filtered view.
04
Filters and saved views
Find rows with conditions like contains, starts with or is one of, then save the view for later.
05
Linked to the work
Connect a row to tickets and stored files, so the record and the conversation stay together.
06
Used by workflows
A data table step finds, adds and updates rows as part of any automation.
THE PRACTICAL DETAILSBefore you
Before you
get started.
What can a data table hold?
Text, numbers, dates, true or false, choices from a list, email addresses, web addresses and JSON. Columns can be required, unique or have a default.
Can I import a spreadsheet?
Yes. Import a CSV file or paste cells from a spreadsheet. Each line is checked against its column, and lines that do not fit are listed with the reason.
Can workflows read and change a table?
Yes. A data table step finds, adds and updates rows, so workflows can keep records current without another tool.
Is there an extra charge for tables?
No. Data tables are included on every plan and use your plan's storage.