Updating a row in Coda table from MindStudio JSON

Hi there. I’m using n8n to connect update three columns for all of the rows in a Coda table based on new data for those three columns from MindStudio. It appears that I need the internal Coda rowID, which I can bring in but can’t map to it. See below screenshots. Thanks for any guidance you may have!

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

You’re super close! The 404 is coming from Coda not finding the row you’re pointing at in Update a view row. Two reliable ways to solve it:

Option A — Use Table → Update Row with the internal Row ID (i-...)

Since you already have the internal row ID (i-VOmMwSQLEI in your screenshot), switch the Coda node to:

  • Resource: Table

  • Operation: Update Row

  • Doc: your doc

  • Table: your table (not the view)

  • Row Name or ID: map the i-... value coming from MindStudio / your prior node

  • Under Columns to update, add the 3 columns you want to change (priority, rationale, keyTheme) and map their values

This hits the table directly and accepts the internal row ID, which avoids the “row not found” you’re seeing on the view update.

Option B — Use Table → Upsert Row with a stable key column

If you don’t want to carry the internal row ID, pick a unique column you own (e.g. your rowNumber), then:

  • Resource: Table

  • Operation: Upsert Row

  • Key Column: select rowNumber

  • Set rowNumber to the incoming value

  • Add priority, rationale, keyTheme in Columns to update

This updates the matching row by key, or inserts if it doesn’t exist—no internal ID needed. (This pattern is often more robust than targeting a view.)

Update a view row expects a row name or ID visible to that view. Passing the internal i-... often doesn’t resolve through the view, which triggers Coda’s “Could not find a row with the specified ID or name” 404. Targeting the table (Option A) or using Upsert with your own key (Option B) avoids that pitfall.

Hi there. Thanks so much for your amazing response. I don’t see either the upsert or update table row resource/operation options available to me. I must be missing something. In case it was only in the current beta version, I installed that for my workspace, but I still don’t see it. Can you point me in the right direction? Oh… one other thing, will I need some sort of sleep or stall operation in my workflow because of API limits imposed by Coda? Thanks again!

Meant to include screenshot:

OK. I’ve tried a different approach. I was able to set up a column in my Coda table that has the internal ROW IDs using the formula [Split(thisRow + “”, “/”).Last()] and that column is named internalRowID. I can now clearly map the internal row IDs coming in to this new column. Here’s the way I have configured the parameters:

And you can see all of the incoming variables for 51 records. What am I doing wrong? I don’t see a place to enter the columns that are to be changed. Completely lost at the moment… :smiley:

Would be very happy to use a table (instead of view) approach, but I don’t see anything like that, that I have access to.

Thanks for any help you can provide!

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.