Airtable ends up holding the things that fit nowhere else — content calendars, vendor lists, hiring pipelines, launch trackers. Each base is tidy on its own. Across a workspace they are twenty separate search boxes, and the long-text fields where the actual reasoning lives are the hardest part to search at all. The Airtable connector is part of askFinz Knowledge, which is still rolling out; here is what it will do, and what it will not.
Ask across bases without building a view
Today, answering "which vendors did we shortlist and why" means opening the right base, remembering the right view, and reading. Connected, you ask the question once and the answer draws on whichever base holds it, naming the record so you can open it.
Read the long-text fields, not just the labels
Notes, briefs and comment fields carry the reasoning that a status column cannot. Those get matched by meaning, so a search for "the supplier we dropped over lead times" can find a record that never uses the word "lead time".
Keep status and dates as filters, not prose
What is read, and what is never written
What crosses, and what stays in Airtable
Read
field values and long-text content from the bases and tables you select.
Written back
nonenothing. No records created, edited or deleted; no comments posted.
Stored
a searchable copy of the text you selected, plus a link back to the record.
Never read
bases you did not tick, and columns holding keys or passwords.
What you will be granting
Read-only access to the specific bases you choose, using the same permissions your own Airtable account already has — no more reach than you have today.
Setting it up
Planned — not available yetWhat connecting it will look like once the connector arrives.
- 01
Authorise Airtable from Knowledge and pick the workspace.
- 02
Tick the bases and tables to include. Anything unticked is never requested.
- 03
Choose how often to re-check for changes.
Limits, honestly
- One-way and read-only. Airtable stays the place you edit.
- Changes appear at the next refresh, not the instant you type them.
- Attachments, revision history and automation logs are out of scope.
- Very wide tables may have low-signal columns skipped to keep answers readable.