Update Row: Coda action · Tiny Command

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Doc ID doc_id	string	Required	Doc ID. Example: AbCDeFGH
Table ID table_id	string	Required	Table ID. Example: grid-abc123
Row ID row_id	string	Required	Row ID. Example: i-row123
Cell Values (JSON) cells	string	Required	Cell Values (JSON). e.g. "[{"column": "Status", "value": "Done"}]"

Sample request

{
  "doc_id": "e.g. AbCDeFGH",
  "table_id": "e.g. grid-abc123",
  "row_id": "e.g. i-row123",
  "cells": "[{\"column\": \"Status\", \"value\": \"Done\"}]"
}

Returns

{
  "id": "i-row123",
  "requestId": "abc-123"
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Update Row.

What does the Update Row action do in Coda?

Partial update on cell values — only the passed columns change. Writes to formula columns are no-ops. For "external system changed → reflect in Coda" sync patterns.

What inputs does Update Row require?

Required: Doc ID, Table ID, Row ID, Cell Values (JSON). Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Coda returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Update Row support batch operations?

Yes. Run Update Row inside a Loop node to process arrays. Tiny Command handles Coda's rate limits automatically so you don't have to throttle manually.

More actions