Heading in data

[sunka]

Hello, I have a problem with the headers of a google sheet.
n8n retrieves the heading to make it a data and adds it as a data. I think I set the node correctly but it’s still the same.

Can someone give me help ? thank you

n8n self hosted
last version
runing via docker

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

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

[ihortom]

@sunka , it appears you are using much older version of n8n. Could you let us know what the version is? There is a significant difference between old and new versions in terms of configuration of Google Spreadsheet node.

I believe the problem you face is due to wrong configuration where you have specified incorrect range of data, more specifically “Data Start Row”/“Key Row”. It would help if you could provide the node configuration and how the data is presented in the spreadsheet.

For example, here’s the 2 outcomes for querying the same data:

Correct range

Invalid range

[sunka]

@ihortom

@sunka , it appears you are using much older version of n8n. Could you let us know what the version is? There is a significant difference between old and new versions in terms of configuration of Google Spreadsheet node.

I believe the problem you face is due to wrong configuration where you have specified incorrect range of data, more specifically “Data Start Row”/“Key Row”. It would help if you could provide the node configuration and how the data is presented in the spreadsheet.

For example, here’s the 2 outcomes for querying the same data:

Hi i use the latest version :

I specifiied the good range. That’s why i don’t understand.

You’re sure that it’s not you with an old version ?

[ihortom]

@sunka

You’re sure that it’s not you with an old version ?

Yes, I used the old version as I assumed you are using the old version too. I still believe you might be using the old version of the node despite having the new version of the app. The reason for that is your screenshot does not show row_number column which is present in the newer version of Google Spreadsheet node as in the screenshot below.

Did you happen to have n8n upgraded while using the old version of the node (copied over from some old workflow)? I cannot reproduce such an issue in the latest spreadsheet node, only in the old one.

You still haven’t presented the actual node with its configuration and the way the data is laid out in the spreadsheet that you query.

[sunka]

But now it’s working. I don’t why. I try without “Data Location on Sheet” and it’s work.

Thank you for your help

Last question : is it possible to have nodes outdated with an updated n8n version ?

[bartv]

@sunka

Last question : is it possible to have nodes outdated with an updated n8n version ?

Yes; your workflows will always keep using the version of the node that you created it with. Auto-updating node functionality could break existing workflows.

We’re having a conversation to display an ‘update available’ indicator in the UI, but for now here’s a template that will check for outdated nodes in all your workflows:

Check if workflows contain build-in nodes that are not of the latest version...

[sunka]

@bartv

Yes; your workflows will always keep using the version of the node that you created it with. Auto-updating node functionality could break existing workflows.

We’re having a conversation to display an ‘update available’ indicator in the UI, but for now here’s a template that will check for outdated nodes in all your workflows:

Oh super, thank you very much