Insert 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 or Name table_id	string	Required	Table ID or Name. Example: grid-abc123
Row Data (JSON) cells	string	Required	Array of cell objects: [{"column": "Name", "value": "John"}]

Sample request

{
  "doc_id": "e.g. AbCDeFGH",
  "table_id": "e.g. grid-abc123",
  "cells": "[{\"column\": \"Name\", \"value\": \"John\"}, {\"column\": \"Status\", \"value\": \"Active\"}]"
}

Returns

{
  "requestId": "abc-123",
  "addedRowIds": [
    "i-row123"
  ]
}

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

FAQ

Questions about Insert Row.

What does the Insert Row action do in Coda?

Inserts a new row with cell values addressed by column ID or name. Writes to formula columns are silently ignored — Coda recomputes formulas after insert. For the standard "external event → log to Coda" workflow.

What inputs does Insert Row require?

Required: Doc ID, Table ID or Name, Row Data (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 Insert Row support batch operations?

Yes. Run Insert 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