Update Field

airtable.update_field
ActionFiles & storageconnection required

Calls the Airtable API with the connection's credentials.

Rename an Airtable column, change its description, or change its type-specific options.

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

6 fields, 3 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
base_id
Airtable base id (app…), from the base's API docs URL or airtable.list_bases.
stringYes——appAbCdEfGhIjKlMn
table_id
Table id (tbl…) — the metadata endpoints take the id, not the name.
stringYes——tblAbCdEfGhIjKlMn
field_id
Field id (fld…) of the column to change, from airtable.get_base_schema.
stringYes———
name
A new name for the column.
stringNo———
description
A new description for the column, up to 20,000 characters.
stringNo—≤ 20000 characters—
options
Replacement type-specific settings as a JSON object, such as a formula's expression or a select's 'choices'.
objectNo———
  • At least one of name, description, options 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

FieldTypeExample
id
The field id (fld…).
string—
name
The field name.
string—
type
The Airtable field type, e.g. singleSelect.
string—
description
The field description, when it has one.
string—
options
The type-specific options Airtable stored for the field.
object—
{
  "description": "",
  "id": "",
  "name": "",
  "options": {},
  "type": ""
}

Notes

  • Needs the 'schema.bases:write' scope on the personal access token.
  • A field's type can never be changed through the API — only its name, description and options.
  • 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 Field 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.