update_row
Update specific fields of an existing row. Only the fields provided in data are updated; others are preserved. Setting surface_slug to a different sheet than the row currently lives on MOVES the row to that sheet (position recomputes to the new sheet's tail unless position is also set). Same surface as current → no-op move.
Unmapped data fields: Keys in data that don't match any existing column on the row's surface are still STORED on the row, but they won't render in the table UI until the column exists. The response carries an unmapped_fields array plus a human-readable warning. Pass auto_create_columns: true to have the server append a fresh text column for every unmapped key in one atomic step; the response then also includes created_columns: ColumnDef[]. Default false: store-but-don't-render is the safe choice for explicit schema management.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | Partial row data with fields to update (e.g. {"status": "sealed"}). Pass an empty object {} when the call is purely a move (surface_slug change with no field updates). | |
| slug | Yes | The workspace slug. Accepts either the bare slug ('my-workspace') or the org-prefixed form ('my-org/my-workspace') as shown in the dashboard URL; both resolve to the same workspace. | |
| rowId | Yes | The row ID to update | |
| position | No | Optional. Override the row's position. When moving across surfaces, omit to land at the new surface's tail; pass a number to land at a specific slot. | |
| surface_slug | No | Optional. When set to a different surface than the row currently lives on, moves the row to that surface and emits a `row.moved_surface` event. Same-surface is a no-op. 400 if the slug is a doc surface, archived, or not in this workspace. | |
| auto_create_columns | No | When true, the server auto-creates a text column for every key in `data` that doesn't already exist on the surface, then applies the update in the same call. Returns `created_columns` in the response. Default false: unmapped keys are still merged into row.data but won't render in the UI until you `add_column` them yourself. |