Skip to content

Product · Integrations

Documents that arrive without an upload.

Most documents already have a place they land — a shared folder, a SharePoint site, an inbox. Point a table at that place and what arrives there becomes rows, answered by the table’s own questions, with nobody signed in.

Connectors and mailhooks are available on the Silver tier and above.

Supplier contracts
Three supplier contracts that arrived without an upload — two from a shared folder and one by email — each answer citing the page it was read from.
RowDocumentsGoverning lawTerm endsNotice periodLiability cap
Harbour Logistics MSA.pdfAmendment 1.pdfEngland & Wales31 Mar 202890 days£2,000,000
Calder Supply agreement.pdfScotland30 Sep 202760 days100% of fees
Reseller terms.pdfPricing schedule.pdfIreland31 Dec 202630 days£250,000
Rows 1 and 2 synced from a shared folder — row 1 was a subfolder, so its documents are one rowRow 3 arrived by email, its two attachments bundled into one row

Two ways in.

The two ways documents arrive without an upload: what becomes a row, when, and what each never does.
ChannelWhat becomes a row
Google Drive or SharePointEach subfolder becomes a bundle, and each bundle a row. Loose files in the folder are read too.
EmailEach email becomes one row, its attachments bundled together.

Three things to know before you forward anything.

  • Nothing comes back from a mailhook. No confirmation, no reply and no bounce, whether it read the email or not — so a working address and a mistyped one look the same from the sender’s side. The activity list in the workspace’s settings is where you see what happened.
  • About 18 MB of attachments per email. That is the ceiling for one message, and it is lower than the upload limit on the tiers that have mailhooks. An email over it makes no row, no error and no record.
  • Below Silver, both stop. A connector stops syncing and nothing is deleted. Mail to a mailhook is refused, and its sender is not told.

Your folder, read with your account.

A connector reads through an account you control — a Google service account you share the folder with as a viewer, or a Microsoft app granted read access to one SharePoint site. An owner or admin registers the account once; a workspace manager then picks the folder and the tables it should feed.

Documents are copied in, and nothing is ever written back. It is not a backup: a file edited in the folder is reported rather than re-read, and one deleted there is reported rather than deleted here.

Setting up a connector

An address, and a list that decides.

A table can have its own email address. Forward a message to it and the email becomes a row, its attachments bundled so they answer as one subject. The subject line and body are not kept.

An address passes in plain sight through every mail server on the way, so it is not what keeps the table safe — the allowlist is. Only mail from an address or domain on it is read, checked against the authenticated sender rather than the From line anyone can type. Seeing the address and the list both need Manage.

Mailhooks

Unattended means spending while nobody is signed in.

Both channels run under the ordinary credit rules, and an auto-mode table answers what arrives without anyone watching. That is the point of them — and it is why your organisation’s monthly spend cap is worth checking before the first document lands.

How credits and spend caps work

Going the other way.

The channels above bring documents in. These take answers out.

Integrations are one part of it. Tables are where the answers land, extraction is how each one is read, and citations are how you check one.

Start with the pile you already have.

Signing up comes with free credits. No card, no subscription.