List Bases
airtable.list_bases
ActionFiles & storageconnection required
Calls the Airtable API with the connection's credentials.
List every Airtable base the connection's token can reach, one page at a time.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- Airtable
- Secret shape
- the Airtable access token
- Resolved by
- config.connection_id, else node.connection_id
Configuration
1 field, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
offset Airtable's continuation token from a previous call's 'offset'. Leave empty for the first page. | string | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
bases[].id The base id (app…). | string | — |
bases[].name The base name. | string | — |
bases[].permissionLevel What the token may do in this base: none, read, comment, edit, create or interfaceOnly. | string | — |
count How many bases this page returned. | number | — |
offset The token for the next page; empty on the last page. | string | — |
has_more True while another page is waiting behind 'offset'. | boolean | — |
{
"bases": [
{
"id": "",
"name": "",
"permissionLevel": ""
}
],
"count": 0,
"has_more": false,
"offset": ""
}Notes
- Needs the 'schema.bases:read' scope on the personal access token.
- Airtable caps every batch write at 10 records per request. The batch nodes chunk for you and report how many calls they made in 'batches'; the calls are sequential and not a transaction, so a failure part-way leaves the earlier chunks committed and says how many got through.
- typecast is what lets a plain string be written into a single-select, date or number column. It is on by default, matching airtable.create_record.
- Reads page on an opaque 'offset' token, not a page number: feed the offset a call returns back into the next call while 'has_more' is true.
- The base/table/field nodes use Airtable's metadata API, which needs the 'schema.bases:read' (or ':write') scope on the personal access token. A token minted only for 'data.records:*' gets a 403 from them.
See List Bases run in a workflow.
In a technical demo we add the Airtable connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.