Update Table
airtable.update_table
ActionFiles & storageconnection required
Calls the Airtable API with the connection's credentials.
Rename an Airtable table or change its description.
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
4 fields, 2 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 |
|---|---|---|---|---|---|
base_id Airtable base id (app…), from the base's API docs URL or airtable.list_bases. | string | Yes | — | — | appAbCdEfGhIjKlMn |
table_id Table id (tbl…) — the metadata endpoints take the id, not the name. | string | Yes | — | — | tblAbCdEfGhIjKlMn |
name A new name for the table. | string | No | — | — | — |
description A new description for the table, up to 20,000 characters. | string | No | — | ≤ 20000 characters | — |
- At least one of name, description must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"base_id": "appAbCdEfGhIjKlMn",
"table_id": "tblAbCdEfGhIjKlMn"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
id The table id (tbl…). | string | — |
name The table name. | string | — |
primaryFieldId The id of the table's primary field. | string | — |
description The table description, when it has one. | string | — |
fields The table's fields, each with id, name, type and options. | array | — |
views The table's views, each with id, name and type. | array | — |
{
"description": "",
"fields": [],
"id": "",
"name": "",
"primaryFieldId": "",
"views": []
}Notes
- Needs the 'schema.bases:write' scope on the personal access token.
- Only the name and description change here; columns are added and edited with airtable.create_field and airtable.update_field.
- 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 Update Table 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.