Google Sheets Node v4.6 fails with “Cannot read properties of undefined”

[timosieber]

Bug Description

I’m using the Google Sheets node (typeVersion 4.6) with the “Get Row(s)” operation in n8n v1.93.0. The exact same setup worked flawlessly with version 4.5 of the Google Sheets node, but in version 4.6 the workflow fails immediately with an internal error, even though nothing changed in the configuration.

To Reproduce

1. Create a workflow with a Manual Trigger

2. Add the Google Sheets node and set typeVersion to 4.6

3. Configure “Get Row(s)” with Document ID and Sheet Name

4. (Optional) Add a simple filter, e.g. “Weiterverfolgt = Nein”

5. Execute the workflow

6. Observe the error message:

   Cannot read properties of undefined (reading 'execute')
   

   It appears immediately, before the node emits any logs or returns items.

Expected behavior

The node should retrieve rows correctly—just as it did in version 4.5—even when a filter is applied, and should not throw an internal error.

Operating System

Railway Linux (containerized via Docker)

n8n Version

1.93.0

Node.js Version

Database

SQLite (default)

Execution mode

main (default)

[Joffcom]

Hey @timosieber,

We have created an internal ticket to look into this which we will be tracking as "GHC-2243"

[Joffcom]

Thanks for reporting this issue! We’ve attempted to reproduce the problem, but unfortunately, we weren’t able to replicate it. It’s possible there was some environmental or other variable that prevented us from seeing the same behavior.

Can you also try updating as I was using 1.94 so it you are on 1.93 it could be that this is fixed already.

If you’re still encountering this issue, please provide any additional details or steps to reproduce it, and we’d be happy to investigate further. Thanks for your understanding!