Product · Auto mode
A table that answers new rows on its own.
Build the table once. After that, every row added to it — a file dropped onto it, an email sent to its address, a document synced from a shared folder — is answered as soon as its documents have been read, without anyone opening the table or pressing Run.
Free credits on sign-up. No card, no subscription.
| Row | Documents | Supplier Insured | Cover Expires | Coverage and Limits | Employers Liability Evidenced |
|---|---|---|---|---|---|
| Harlow Scaffolding certificate.pdf | Harlow Scaffolding Ltd p.1 | 31 Mar 2027 p.1 | Public liability £5m, Employers’ liability £10m p.1 | Yes p.1 | |
| Northgate Electrical certificate.pdfSchedule of cover.pdf | Northgate Electrical Ltd Certificate, p.1 | 30 Jun 2027 Certificate, p.1 | Public liability £2m Schedule of cover, p.2 | No Certificate, p.1 | |
| Brightline HVAC certificate.pdf | Spend cap | Spend cap | Spend cap | Spend cap |
Three ways a row arrives.
Auto mode answers rows, and a row belongs to a table. Uploading to the workspace’s files without adding them to a table starts nothing.
| How it arrives | What becomes a row |
|---|---|
| Dropped onto the table | Each file becomes a row, or a bundle you drop becomes one. |
| Sent to the table’s email address | Each email becomes a row, its attachments bundled together. |
| Synced by a connector | Each subfolder becomes a bundle and a row; loose files are read too. |
Email addresses and connectors are available on the Silver tier and above — integrations covers both.
On from the start, off when you say.
Tables made in the app, and tables made from a template, start in auto mode. Tables created through the API start manual.
Switching a table between the two needs Manage on its workspace. Turning auto mode off keeps every answer already in the table; it only stops new rows answering themselves.
Only rows that have never run.
A row is answered once, when every one of its documents has been read. A row with a document that failed to read waits for you rather than running on what is left.
Rows already answered are left alone. Editing a column’s question marks its answers stale rather than rerunning them, and cells corrected by hand are never overwritten.
Spending while nobody is signed in.
Auto mode turns spending credits from something a person does into a standing arrangement, so it stops where you would want it to. At a zero balance, or at your organisation’s monthly spend cap, a new row is marked Out of credits or Spend cap instead of running, and nothing is charged.
Buying credits lets the rows that stopped for credits run. Rows held by the cap wait for the next month, or for an admin to raise it. A row that stopped partway stays for someone to finish by hand.
Every organisation has a monthly spend cap from the start, so it is worth checking what yours is set to before a table starts answering on its own.
What it will not do.
- It fills the table; it does not watch it. It will read an expiry date off a certificate and cite the page, and nobody will be told when that date comes.
- It does not rerun what is already there. Existing rows keep their answers until someone runs them again.
- It does not pick up files uploaded elsewhere. A document added to the workspace but not to the table is not a row, so it is not answered.
Auto mode is one part of it. Integrations bring rows in without an upload, bundles are what an email or a subfolder becomes, and tables are where the answers land.
Start with the pile you already have.
Signing up comes with free credits. No card, no subscription.