Airtable

Bases and the operational trackers your team keeps by hand. Read-only.

Connects with	OAuth, or a personal access token
Reads	4 operations
Writes	None
Irreversible	None
Personal data	Whatever the shared bases hold.
Data stays in	AWS Sydney (ap-southeast-2)

What it reads

• The bases the connection can reach.
• Each base’s tables, with every field’s type and options and the available views.
• Records, listed from a table or fetched one at a time.

What it does not read

Comments, and bases that were not shared with the connection.

What it writes

Nothing. There are no write operations in this connector.

How you connect it

Connect with OAuth. From the Integrations page, choose Connect on Airtable, tick the operations StoriBot may use, and approve at Airtable signed in as yourself. Airtable asks you which bases to share.

If you prefer, paste a personal access token instead. Create it in Airtable’s developer hub with the schema.bases:read and data.records:read scopes on the bases to expose. It starts with pat.

What StoriBot will ask for

Airtable’s consent screen lists schema.bases:read and data.records:read, scoped to the bases you choose. No write scope is requested.

Every operation

These are the names the Integrations page shows beside each tick box, in the order it lists them. Generated from the connector registry; do not edit by hand.

All 4 operations

Operation	Kind	What it does
list_bases	Read	List the bases the credential can reach, with their ids.
list_tables	Read	Describe a base: every table with its fields, each field’s type and options, and the available views.
list_records	Read	List records from one table.
get_record	Read	Retrieve one record by id.