Teable (TuanDK)Install

Summary

Updates multiple existing records in a Teable table by sending a JSON array of {id, fields} objects via PATCH, batched 1,000 at a time. Returns each updated record as its own output item.

Inputs

• Space (required) — Teable space selected from a dropdown; used only to cascade the Base list.
• Base (required) — Base within the space; used only to cascade the Table list.
• Table (required) — Table whose records are updated. Must contain only letters, digits, underscores or hyphens (validated).
• Records (JSON) (required) — Array of objects, each with "id" (recXXX) and "fields" (field key → new value). Accepts a JSON string or an already-parsed array/expression result. Invalid JSON throws an error.
• Additional Options > Field Key Type — Whether keys in "fields" are field names (default) or field IDs (fldXXX). Sent as fieldKeyType only when set.

Output shape

One output item per updated record, taken from the records array in Teable's PATCH response.

The request is sent with typecast enabled, so Teable coerces values to the field types. Records beyond 1,000 are split into sequential requests. The node does not check that each entry has id/fields; Teable validates them. The operation runs once per input item, so each input item's recordsJson is processed and results are concatenated. With Continue On Fail, an error becomes an item with an error message. Transient 429/5xx errors are retried up to 3 times without delay.

Examples

Example 1: Mark several records as Done

Select Space/Base/Table; Records (JSON) = [{"id":"rec1","fields":{"Status":"Done"}},{"id":"rec2","fields":{"Status":"Done"}}]

Example 2: Bulk update from upstream data using field IDs

Records (JSON) set by expression building [{id, fields:{fldXXX: value}}] from earlier nodes; Field Key Type = Field ID

Links

• n8n community nodes installation guide