Niches · Spreadsheets & operational tables
Change existing cells or records without breaking the sheet
Two or three companies' docs show a full fit.
What counts as done
Only the targeted cells change, formatting and comments stay, the update is matched by a key so a repeat changes nothing more, and a read right after shows the new values.
How agents ask for it: mark these rows as done
, update the price column
, fix the typos in this sheet
, set the status for this customer
Does the job 3
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Airtable BB Formagrid Inc (doing business as Airtable) | PATCH on Update multiple records changes only the fields sent, by record id or by fieldsToMergeOn, so a repeat changes nothing more; fields can be addressed by id. source |
| Grist E Grist Labs Inc. | PUT /records matches rows by the require fields and updates only the fields given, with onmany and noadd options, so a repeat changes nothing more; PATCH by row id also exists. source |
| NocoDB BB NocoDB Inc (doing business as NocoDB) | PATCH /records changes only the fields sent by record id, and /records/upsert matches on a merge key so a repeat changes nothing more; fields can be addressed by id. source |
Does the job, with a limit 7
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| Baserow C Baserow B.V. | PATCH by row id or batch PATCH changes only the fields sent, addressed by field_{id}. Matching is by row id only, so an agent keyed on a business field reads before every write. source |
| Coda (Superhuman Docs) BB Superhuman Platform Inc. (parent of Coda Project LLC) | PUT on a row by id or name changes only the cells sent, and keyColumns upserts match by key. The update is queued (202), so read-after-write needs a mutationStatus poll. source |
| Google Sheets API A Google LLC | values.update and batchUpdate change only the cells in the given ranges and keep formatting, but updates address A1 ranges, not a key, so the agent reads to find the row before every write. source |
| Microsoft Excel (Microsoft Graph workbook API) D Microsoft Corporation | PATCH on a range or table row changes only those cells, but rows are addressed by index or address, not a key, and Microsoft warns that concurrent writes to one workbook cause throttling, timeouts and merge conflicts (acc-30). source |
| SeaTable B SeaTable GmbH | Update Row(s) changes only the columns sent by row_id, and Lock Rows can stop others editing; SQL UPDATE ... WHERE can match on a key column, but no upsert exists, so a key-matched insert-or-update needs a read first. source |
| Smartsheet API + MCP B Smartsheet Inc. | PUT /sheets/{id}/rows changes only the cells sent, by row id and column id. Rows are matched by id, not a key, and parallel writes to one sheet with one token return error 4004. source |
| Teable B Teable AI, Inc. | PATCH /table/{id}/record updates only the fields sent by record id with fieldKeyType=id, but there is no key-based match, so the agent reads before every keyed write. source |
What stops agents finishing
- parallel writes to one file throttled or merged wrongly (Graph, Smartsheet 4004)
- no key-based upsert, so the agent reads before every write
Around it
Before: spreadsheets.filter-records. After: spreadsheets.read-table.
Where this comes from
Weight 11 of 100 in Spreadsheets & operational tables: 4 of 35 accounts: the diff-only push CLI, NocoDB field ids, Teable duplicates on retry, Excel co-editing conflicts
The same as data: /api/v1/use-cases/spreadsheets.update-in-place.json, or the MCP tool get_use_case with id spreadsheets.update-in-place. Other jobs in this category: /api/v1/niches?category=spreadsheets.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.