I’m seeking your help with a specific data integration issue in my n8n workflow (version 1.68.0) with Google Sheets.
My workflow starts with a form that collects a keyword, triggers the duplication of a Google Sheets template, and automatically renames it. The system then performs SERP scraping via an API, with data processing through a JavaScript Code node.
The core of my issue lies in the Google Sheets data integration. I first tried using the “Update Row” operation directly. While the data integrates correctly, since cell A2 already contains a value, the system automatically skips a line. As a result, my keyword list starts at row 3 instead of row 2.
Following received advice, I implemented a Loop node to process items individually and switched to using the “Append” operation. However, this approach creates a new problem: either the data isn’t properly taken into account, or it starts at the first line but overwrites itself instead of writing line by line.
To help you better visualize my issue, I’m attaching:
A preview of the items I want to integrate into my Google Sheet
The current configuration of my Google Sheets node
An overview of my workflow
Any help would be greatly appreciated to resolve this integration issue and ensure correct line-by-line data insertion.
Ensure to copy your n8n workflow and paste it in the code block, that is in between the pairs of triple backticks, which also could be achieved by clicking </> (preformatted text) in the editor and pasting in your workflow.
```
<your workflow>
```
That implies to any JSON output you would like to share with us.
Make sure that you have removed any sensitive information from your workflow and include dummy or pinned data with it!
You mentioned that you used “append” but the screenshots show “update”.
I also do not think that using Loop is a good idea for this job.
To succeed, you likely need to compose the whole row, not just one column. Then you can append row by row without issues.
Having said that, you have repeated column names, namely “Volume” which will curtainly confuse n8n in the proposed solution. You would have to give them some distinct identifiers.
