Update record

The unique identifier of the Airtable base containing the record to be updated.

Fields to update. Keys are field names (case-sensitive) or IDs (fldXXXX recommended). Only specified fields are modified. Empty strings convert to null. Field names must match Airtable schema exactly (e.g., 'Call Status' not 'call status'). Use AIRTABLE_GET_BASE_SCHEMA for exact names/IDs. Date-only fields require 'YYYY-MM-DD' format. Date-time fields require ISO 8601: 'YYYY-MM-DDTHH:MM:SS.sssZ'. Human-readable dates rejected even with typecast=true. SELECT FIELDS: With typecast=false (default), only existing select options accepted; new values fail with INVALID_MULTIPLE_CHOICE_OPTIONS. Set typecast=true to auto-create new options or verify existing options via AIRTABLE_GET_BASE_SCHEMA first.

The unique identifier (ID) of the record to be updated within the specified table. MUST be in Airtable's record ID format: exactly 17 characters starting with 'rec' followed by 14 alphanumeric characters (e.g., 'recABC123def456G'). Simple numeric values or row numbers are NOT valid record IDs. You can obtain valid record IDs from the AIRTABLE_LIST_RECORDS action or the Airtable web interface.

Enables automatic data conversion and select option creation. CRITICAL FOR SELECT FIELDS: When false (default), Airtable rejects updates to single-select or multi-select fields if the value is not already an existing option, failing with 'Insufficient permissions to create new select option' error. When true: (1) automatically creates new select options if they don't exist, and (2) converts strings to appropriate types for other fields (e.g., '123' to number 123). RECOMMENDED: Set to true when updating select fields with potentially new values, or use AIRTABLE_GET_BASE_SCHEMA to verify option existence first. Set to false only when you want strict validation against existing options.

The unique identifier (ID) or the name of the table within the base that contains the record to be updated. Also accepts 'tableId' as an alias.

If `True`, API response keys record fields by field ID instead of name. Using field IDs is recommended for integrations resilient to field name changes.