I have replicated the Google Sheets trigger node configuration that shows @KevinK and the bug is found when the sheet containing the data has been renamed.
If the sheet contains the default name assigned to it by Google Sheets, as shown below, the trigger executes correctly.
If the sheet is renamed with another text string, the Google Sheets trigger does not allow to activate the workflow showing the error that @KevinK comments.
I have reproduced the workflow in two instances of n8n running on Cloudron in versions 0.233.0 and 0.232.0 respectively and the behavior is identical in both.
If it is a rename that makes sense as the sheet the node is looking for wouldn’t exist so in theory it would need to be deactivated and activated again.
@martinhache that is strange and unexpected I would expect it to work assuming the ID doesn’t change on the rename which would be a surprise. I will do some digging on this Monday morning to see what I can find.
Hi,
I am experiencing the same problem with the Google Sheets Trigger. It started after I renamed the sheet. Even when I tried using the sheet id (0) instead of its name in the node, it still did not solve the issue.