UPDATE ROW : Unable to retrieve Row ID from n8n

Your Setup:

Please describe your issue as precise as possible. If helpful, you can also provide:

Hello,

I’m working on an n8n workflow connected to SeaTable to automate email sending.
I use the Get Many Rows action and I can successfully read all my table columns, but I’m unable to get the internal Row ID in the returned data.

Without this ID, I cannot use the Update Row action dynamically — at the moment I have to select a Row ID in “Fixed” mode, which means it always updates the same row.
My questions:
	•	How can I include the internal Row ID of each row in the “Get Many Rows” output in n8n?
	•	Is there any specific setting in SeaTable or n8n to ensure this data is returned?
Thanks in advance for your help!

Hi @ChrisD2044 and welcome to the SeaTable forum!

As far as I remember, there’s a Simplify option checked by default for this node. If you uncheck it, you’ll get the row ids with the _id key. Another solution is to create a specific formula-type column with the simple formula rowID() to get the actual id of each row directly inside your table.

Bests,
Benjamin

1 Like

Thanks @bha !

actually the simplify option must be selected and then disabled, which generate the _id in the output jason, thanks a lot !

Then it goes to the send mail node, but the latter does not replicate the id_ parameter in its output so the Update row node cannot take it as an input.

Temporary solution: place the update row node at the output of the IF node with assumption that the mail will be effectively sent, but not really acceptable

As for the rowid() formula that works too, I can see it at the output of the IF node, but the send mail node does not replicate it to the update row node either. Would there be anyway to do this?

would mean one cannot update the row once a mail has been sent regarding this particular row

thanks a lot

Hi @ChrisD2044,

Maybe I misunderstand what you say, but this sounds more like an n8n problem to me, and you can actually set as input a value from an older node that the immediately previous one.
To be sure you get only the right _id, you can eventually loop over items, but I’m not sure that you actually need this :thinking:

Bests,
Benjamin

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