A data table is a small spreadsheet that lives in your workspace: a rate card, a list of delivery zones, a weight-band price list, a stock list. Your forms read from it, so a visitor gets a real price or answer the moment they fill in the form, and you change the numbers in one place instead of editing every form.
Data tables live in the dashboard under Forms → Data tables.
What a table looks like
Columns across the top, one record per row. For example, a pallet rate card:
| max_kg | price |
|---|---|
| 100 | 40 |
| 500 | 90 |
| 1000 | 150 |
Each table has two names:
- Name - what you call it in the dashboard, such as "Pallet rates 2026".
- Name in formulas - the short handle forms use to find it, such as
pallet_rates. Lowercase letters, digits, and underscores, starting with a letter, up to 40 characters. It must be unique in your workspace.
Create a table from a CSV file
- Go to Forms → Data tables → New data table.
- Give it a name and a name for formulas.
- Choose CSV file and upload your file.
- Save.
What the file needs:
- The first row holds the column names. Every column needs a name and names cannot repeat.
- Comma or semicolon separated. Semicolon files from European spreadsheets work as they are, and "12,50" is read as 12.5.
- Plain numbers become numbers, so formulas can do arithmetic with them. Values with a leading zero, like the postcode
01234, stay text so the zero is kept. - Empty rows are skipped.
To change the numbers later, open the table and upload a new file. It replaces the old contents in one step.
Limits
| Limit | Value |
|---|---|
| Rows per table | 5,000 |
| Columns per table | 20 |
| CSV file size | 1 MB |
| Tables linked to an API | 10 per workspace |
Three ways to fill a table
- Upload a CSV file - best for a list you update now and then. See above.
- Refresh from an API - Formspring fetches your JSON endpoint every hour, every day, or when you ask. See Refresh from an API.
- Push from your own system - your transport management system, ERP, or shop sends the fresh table to Formspring whenever something changes. See Push data with the API.
Whichever way a table is filled, forms always read the stored copy. A slow or unavailable source can never slow a form down.
Use it in a form
Add a Computed field to a form and write a formula that uses lookup or band. See Look up prices in formulas.
Deleting a table
Deleting a table is queued and finishes in the background. Forms that still use it show a blank result for those formulas, so update the forms first.