List Rows: 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 or Name table_id	string	Required	Table ID or Name. Example: grid-abc123
Search Query query	string	Optional	Full-text search across row values
Limit limit	string	Optional	Limit. e.g. "25"

Sample request

{
  "doc_id": "e.g. AbCDeFGH",
  "table_id": "e.g. grid-abc123",
  "query": "e.g. John",
  "limit": "25"
}

Returns

{
  "items": [
    {
      "id": "i-row123",
      "name": "Row 1",
      "values": {
        "Name": "John",
        "Status": "Active"
      }
    }
  ]
}

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

FAQ

Questions about List Rows.

What does the List Rows action do in Coda?

Returns paginated rows with optional query filter (column-id:"value" equality only — for richer filtering, query loosely and filter downstream). Max page 1000.

What inputs does List Rows require?

Required: Doc ID, Table ID or Name. 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 List Rows support batch operations?

Yes. Run List Rows 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