I then use the “Create or Update” function of Google Sheets with the below parameters, which seems to work because no error and I have the below output:
@aymkdn I just came to the Community Forum earlier with the same problem & (I think) I found a solution:
It could be a problem with the Googlesheet Node version under the current N8N version. The solution ( according to @fxholl is mentioned here : Update Google Sheets node: Could not find column for key) Basically use the old Googlesheets Node instead of the new one - worked for me
From the screenshot @treyr has provided I believe It’s also the old GS Node (?)
I have the latest version BUT I checked and the node is old.
I just added a new workflow with the new node and boy is it different !
Not sure how this new node works for the same functionality
The interface for the new Google Sheet Node sure is fancy (I personally love the look & feel of it all) The only problem is they omitted some of the old node functionalities which were superb (e.g in this case adding Key vales) I’ve reverted to using the old one as well as I await…
Thank goodness N8N updates don’t affect Node versioning inside workflows (Versioning - n8n Documentation) - otherwise we’d be in deep doo-doo!
I agree the upsert by key is a critical function for middleware like n8n which doesnt have its own persistent data storage between workflow instances.
So by design, you have to rely on keeping the state someplace else and Google Sheets are popular and also easy to use and a natural choice.
Please add this functionality back - it is CRITICAL.
It does indeed. Took me a minute to figure it out as well
Quick one - is there a “changelog” page of some sorts where one can see vairous Node Versionings? (to know which typeversion to revert to/update as it were?)