Google Sheets new column not recognized by Search Rows module

Beginner Questions
1

:bullseye: What is your goal?

I want to read data from a Google Sheets spreadsheet using the Search Rows module, including a column I recently added.

:thinking: What is the problem?

The Search Rows module does not recognize a new column I added to my spreadsheet. The module only shows columns that existed when I first connected the spreadsheet. Any structural update I make to the sheet (new columns, renamed headers) is not reflected in Make. The last visible column is always the original one — the new column never appears for mapping.

:test_tube: What have you tried so far?

Changed the Column Range to A:Z
Deleted and recreated the Google Sheets module from scratch
Reconnected the Google account
Moved the new column to different positions in the sheet
Used a simple header name without special characters
Ran the scenario with “Run Once”

I feel like I’m being very stupid and the answer is obvious. Nothing has worked so far. It seems like Make caches the original spreadsheet structure and never refreshes it.

:camera_with_flash: Screenshots: scenario setup, module configuration, errors

Capturar 3.PNG
Capturar 3.PNG1366×728 83.5 KB
Capturar 2.PNG
Capturar 2.PNG1366×768 149 KB
Capturar.PNG
Capturar.PNG1366×768 165 KB

3

Hey there,

yeah google sheets module cache information when they are setup first. But deleting the module and creating a new one is the surefire way to bypass this. I know it sounds stupid, but maybe you have two spreadsheets with similar names and have the wrong one open? Or you are looking at a different sheet in the spreadsheet?

4

Hello @Volare_Marketing,

Please check if you don’t have an additional copy of your file where you added column “O”, as Stoyan suggested. This is the most likely cause- especially considering that Google allows storing multiple files with the same name in one folder.

For the future, you can right-click on the module and choose Run this module only. This should refresh cached data.

As a workaround, you can set Table contains headers to No.
With this approach, you map columns directly by their IDs (letters).

Have a nice day,
Michal