Airtable bases often hold the operational truth of a team: pipelines, roadmaps, inventories. Fivo reads the tables you choose and can write your reports and tasks back as records.
What it adds to your Brain
For each table you choose to read, Fivo turns every record into a page: the primary field becomes the title and the other fields become lines of text (attachments are skipped). Comments on a record are read too, with their authors and the people they mention. Airtable does not say who created a record, so you, the owner of the connection, are recorded as the author of records.
Fivo also writes. A meeting report becomes a record in the table you chose: the title goes in the primary field and the body, in Markdown, in a field named "Notes" or "Description" if the table has one. Action items detected in a meeting can be saved as records in the same way, one per task.
Example question your AI can then answer: "Which roadmap items in Airtable mention the Acme account, and what did people comment on them?"
Before you start
- An Airtable account with access to the bases you need. Writing needs a base where you can edit or create records; reading works on bases you can only read or comment on.
- Organization scope requires the organization owner. See Connect your tools.
- If you want report bodies saved, make sure the destination table has a long text field named "Notes" or "Description".
Step by step
- Open Integrations in app.fivo.ai and find Airtable.
- Click Connect. Airtable opens its authorization page. You approve permissions to read and write records, read the structure of your bases, read record comments and see your email address.
- Back in Fivo, open the integration's Configuration and choose:
- Base: the base where records will be saved. Only bases you can write to are listed.
- Table: the table of that base where reports and tasks go.
- Tables to read (optional): the tables that feed your graph, listed as "Base · Table".
- Save.
- To feed your graph, go to the Brain view, connect Airtable as a source and pick the tables to read.
What happens next
Fivo reads each table within the history window of the source, record by record, with comments where there are any. Airtable limits how fast a base can be read, so Fivo paces itself and, if Airtable asks it to wait, resumes a little later. Airtable's webhooks are not used, so changes arrive with the next scheduled read rather than instantly.
Airtable shares a whole base, never a single table, and Fivo cannot reliably list a base's collaborators. With organization scope, what Airtable brings in is visible to the organization owner and to the people recorded as authors or participants, which means you and the people who commented. With personal scope only you see it. See Permissions: what your Brain can see.
Saving reports and tasks does not depend on reading.
Disconnect
Open Integrations, select Airtable and click Disconnect. To stop reading but keep saving records, use Remove from graph in the Brain view.
Troubleshooting
- The base you want is not offered for writing. Only bases where you can edit or create records appear in the Base list. Reading is more permissive: the same base may still appear under "Tables to read".
- Records are saved without their body. The body is written only to a field named "Notes" or "Description". Add one to the table.
- Reading pauses. Airtable's rate limit binds the whole base for a short time after it is hit. Fivo waits and continues; nothing is lost.
- "The table is no longer in its base." The table was deleted or moved. Pick another table to read.
Related: Connect chat and documents.
- integration
- docs