Coda n8n integrationAutomate Coda with n8n.

Controls are the sliders, selectors and buttons sitting on a Coda page. This operation reads one of them and returns its current value, which lets a workflow branch on a choice a human made in the doc.

• Doc Name or ID: the doc that holds the control, picked from the dropdown or passed as an expression when the doc changes per item.
• Control ID: the identifier of the control itself, a plain text field rather than a list.

Lists every control in a doc in one call, with the identifier of each one. It is the fastest way to find out what a doc exposes without clicking through its pages.

• Doc Name or ID: the only required input, since controls are scoped to the doc rather than to a table.
• Return All: on, n8n walks the API pages until every control is back; off, Limit caps how many come through.

A Coda formula is a named calculation living in a doc. Asking for it returns the value Coda computed, already up to date, so a workflow reports a number instead of rebuilding it.

• Formula ID: the identifier of the calculation to read, entered as text.
• Doc Name or ID: the doc where that formula lives, chosen in the list or supplied with an expression.

Returns the formulas a doc publishes, with their identifiers and values. Handy when the doc belongs to someone else and its internals are not obvious from the outside.

• Doc Name or ID: scope of the call, since formulas are listed per doc.
• Return All and Limit: leave Return All off with Limit set low while exploring, turn it on when the workflow needs the complete set.

Writes an incoming item into a Coda table as a new row. Fields from the previous node map onto columns, so a form submission or an inbound email becomes a tracked line without anyone retyping it.

• Table Name or ID: the destination table, selected from the list that loads once the doc is set.
• Key Columns: optional column identifiers used as upsert keys, comma separated; matching rows get updated instead of duplicated.
• Disable Parsing: on, Coda stores values exactly as sent rather than interpreting them.

Removes one or several rows from a table. The deletion applies to the underlying table, so the row disappears from every view built on top of it.

• Row ID: the rows to delete, typically carried over from an earlier read as {{ $json.id }}.
• Table Name or ID: the table the rows belong to, required alongside the doc.

Describes the structure of a table: every column with its identifier and name. Column identifiers survive renames, which is exactly why a workflow should store them.

• Table Name or ID: the table to inspect, from the dropdown or an expression.
• Return All: off, Limit decides how many columns come back, enough for a quick look at a wide table; on, every column comes back.

Pulls the contents of a table into the workflow, one n8n item per row. This is the read operation most Coda automations start from.

• Query: filters rows server side as column:value, with the value written as JSON, so text needs its own quotes.
• Return All: turned on, n8n chains the API pages to bring back the whole table; turned off, Limit stops it early.
• ValueFormat: Simple, Simple With Arrays or Rich, depending on whether you want plain cell values or the structured version.
• Visible Only: restricts the result to the rows and columns visible on the table.

Fetches the definition of a single column: what it is called, how it is typed, what identifier it answers to. It reads metadata, not the values stored in the cells.

• Column ID: the column to describe, given as text.
• Table Name or ID: the table it belongs to, required with the doc.

Reads a single row and returns its cells. Use it when a workflow already knows which record it cares about and pulling the whole table would be wasteful.

• Row ID: the identifier or the name of the row; names are fragile because anyone can edit them, and a name used twice returns an arbitrary match.
• Use Column Names: returns column names instead of identifiers, readable but prone to breaking after a rename.
• RAW Data: hands back the API response untouched, useful while debugging a mapping.

Presses a button column on a given row, exactly as a person clicking it in the doc would. Whatever the button does inside Coda then happens without a human.

• Column Name or ID: the button column to press, chosen from the list the node loads for that table.
• Row ID: which row gets the click, by identifier rather than by name whenever possible.

Deletes a row through a view instead of the table. Both dropdowns load real values, so the row can be selected without digging for its identifier first.

• View Name or ID: the view that shows the row, picked from the list.
• Row Name or ID: the row to remove, also offered as a list here rather than a free text field.

Returns the description of one view: its name, the table behind it and its identifier. A small call that mostly serves to confirm a workflow points at the right place.

• View ID: entered as text on this operation, unlike the view operations that offer a dropdown.
• Doc Name or ID: the parent doc, required for every operation on the node.

Lists the columns a view exposes. A view often hides part of its table, so this list can be shorter than the columns of the underlying table.

• View Name or ID: the view to inspect, selected in the list loaded from the doc.
• Return All and Limit: the same pair as everywhere on the node, all columns or a capped number.

Enumerates the views of a doc with their identifiers. Since several view operations expect an identifier, this call is often the one that provides it.

• Doc Name or ID: the doc to scan, with no table to specify at this level.
• Return All: on for a complete inventory, off with Limit when a sample is enough.

Reads the rows displayed by a view, filters included. When a view already isolates the records you care about, this saves filtering the whole table in n8n.

• Query: narrows the result further, written as column:value with a quoted column name when you use one.
• Sort By: Created At or Natural; left empty, rows arrive in creation order, oldest first.
• Return All: on, every row of the view comes back page after page; off, Limit caps the batch.

Triggers a button column on a row seen through a view. The mechanics match the table version, but every input here is a dropdown, which makes it quicker to configure by hand.

• Column Name or ID: the button to press, listed for the selected view.
• Row Name or ID: the target row, also offered as a list.

Changes the content of a row reached through a view. The write goes to the underlying table, so the new values show up everywhere that row appears.

• Key Name: required text field identifying what gets written on the row.
• Row Name or ID: the row to modify, taken from the list the view exposes.
• Disable Parsing: keeps Coda from interpreting the values, which protects strings that look like dates or numbers.